Showing posts with label event. Show all posts
Showing posts with label event. Show all posts

Thursday, March 22, 2012

Error in the Event Viewer - Database log truncated: Database: DBNAME

Hi,

I am with a problem in my SQL Server 2000 SP1 Database, called Siade.
A job runned with success but in the Event Viewer I saw an error with
this message:
" The description for Event ID ( 17055 ) in Source ( MSSQL$SIADE )
cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 18278,
Database log truncated: Database: Siade."

So I would like to know how the job was succesfully, and there was an
error in Event Viewer?
Is this possible?
Ah! The job has these 3 steps:
Step 1- exec dbcc_all_dbreindex
Step 2- backup log Siade with truncate_only
Step 3- DBCC SHRINKDATABASE (Siade,0)
Please, reply me! This error is appearing everytime the job is executed and I want to know if I can ignore it...
Thanks,

NadiaRE: The job has these 3 steps:
Step 1- exec dbcc_all_dbreindex
Step 2- backup log Siade with truncate_only
Step 3- DBCC SHRINKDATABASE (Siade,0)


Comments:

Q1 DBCC SHRINKDATABASE (Siade,0) will attempt to shrink the DB Siade to 0% free space! Is the Siade DB any kind of normal production DB (with new data inserted, updated, etc.)?
{If so, 0% free space as a target is likely not the most efficient choice possible. In low DB freespace enviroments any, and possibly many kinds of inserts, may require more extents to be allocated to the DB before a given insert may complete. Triggering a resource intensive DB growth event in this manner may be expected to not only delay the triggering insert itself, but also to generally degrade the server's user responsiveness (until the growth event is completed).

Comment1 Reindexing consumes a Db's free log space (if 0% free space exists in a given DB at the time of reindexing , potentially many many more extents may need to be allocated to grow the DB Log (before the reindexing may complete).

Comment2 In general, Backups are prevented from occuring if certain kinds of schema locks are present (such as those that are applied when growing a DB with 0% free working space to allow reindexing to complete).

Sunday, March 11, 2012

error in my event viewer "application log"

Hi all, I'm using winxp pro and just installed MSDE2000 /w
sp3, now I see a error message in my event
viewer "application log":
19012 :
SuperSocket Info: Bind failed on TCP port 1433.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Can anyone give me a hand?
GMow
hi GMov,
"gmow@.shaw.ca" <anonymous@.discussions.microsoft.com> ha scritto nel
messaggio news:5a3101c42d5a$25dd6770$a501280a@.phx.gbl...
> Hi all, I'm using winxp pro and just installed MSDE2000 /w
> sp3, now I see a error message in my event
> viewer "application log":
> 19012 :
> SuperSocket Info: Bind failed on TCP port 1433.
>
your TCP 1433 port is probably in use by other applications..
please refer to
http://support.microsoft.com/default...b;EN-US;293107 for further
info and hints to solve the problem..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,thx for the info, let me try and see!
>--Original Message--
>hi GMov,
>"gmow@.shaw.ca" <anonymous@.discussions.microsoft.com> ha
scritto nel[vbcol=seagreen]
>messaggio news:5a3101c42d5a$25dd6770$a501280a@.phx.gbl...
MSDE2000 /w
>your TCP 1433 port is probably in use by other
applications..
>please refer to
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;293107 for further
>info and hints to solve the problem..
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>.
>

Friday, March 9, 2012

Error in Mcafee MSDE

Hi Everyone,
i have a problem in Mcafee MSDE , it doesent run & give me the error in the
Event Log
"This SQL Server has been optimized for 8 concurrent queries. This limit has
been exceeded by 1 queries and performance may be adversely affected."
event id 17055
Any Idea About This error'
Thx in Adv.Thats the effect of the query governor which slows allows only 8 simultanly
queries per server based on the restrictions of the msde.
"MSDE includes a
Governor Workloads that kicks in when 8 of more concurrent workloads
activities (batches that include the operations as described in
http://msdn.microsoft.com/library/?url=/library/en-us/architec/8_ar_sa2_0ciq.asp
?frame=true)
are executed and slows all of them down, but more workloads are supported
and only slowed down...
"
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Mariame" <mariame_waguih@.hotmail.com> schrieb im Newsbeitrag
news:u$vix1nZFHA.3132@.TK2MSFTNGP09.phx.gbl...
> Hi Everyone,
> i have a problem in Mcafee MSDE , it doesent run & give me the error in
> the Event Log
> "This SQL Server has been optimized for 8 concurrent queries. This limit
> has been exceeded by 1 queries and performance may be adversely affected."
> event id 17055
> Any Idea About This error'
> Thx in Adv.
>

Sunday, February 26, 2012

Error in Event Viewer

I am having trouble backing up my SQL DBs using Retrospect software to a NAS
box. I am thinking this error might have something to do with it. What does
it mean? Thanks for any help!
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan1'' (0xAE93FC57F4BBB24EAC6F90AD165B993F) - Status: Failed -
Invoked on: 2004-11-19 02:00:01 - Message: The job failed. Unable to
determine if the owner (PULIZ04\Administrator) of job DB Backup Job for DB
Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could not
obtain information about Windows NT group/user 'PULIZ04\Administrator'.
[SQLSTATE 42000] (Error 8198)).
The maintenance plan has been made with a user who probably doesn't exist
anymore.
You might try to edit the maintenance plan and use a user name and password
with full admin rights at
the database. Simply right click the maintenance plan and choose edit
properties. Within the properties it's possible to edit the user.
Regards,
Johan
"scottdog129" <scottdog129@.discussions.microsoft.com> schreef in bericht
news:6E7E1780-9C65-49F6-AFE1-088266C1920C@.microsoft.com...
> I am having trouble backing up my SQL DBs using Retrospect software to a
NAS
> box. I am thinking this error might have something to do with it. What
does
> it mean? Thanks for any help!
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan1'' (0xAE93FC57F4BBB24EAC6F90AD165B993F) - Status:
Failed -
> Invoked on: 2004-11-19 02:00:01 - Message: The job failed. Unable to
> determine if the owner (PULIZ04\Administrator) of job DB Backup Job for DB
> Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could
not
> obtain information about Windows NT group/user 'PULIZ04\Administrator'.
> [SQLSTATE 42000] (Error 8198)).
|||Yes, that is the resason for your backup failure. That happens now and then
and there are different causes and fixes. The best way is to avoid such a
problem by changing your job owner to a SQL login such as sa.
Gary
"scottdog129" <scottdog129@.discussions.microsoft.com> wrote in message
news:6E7E1780-9C65-49F6-AFE1-088266C1920C@.microsoft.com...
> I am having trouble backing up my SQL DBs using Retrospect software to a
NAS
> box. I am thinking this error might have something to do with it. What
does
> it mean? Thanks for any help!
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan1'' (0xAE93FC57F4BBB24EAC6F90AD165B993F) - Status:
Failed -
> Invoked on: 2004-11-19 02:00:01 - Message: The job failed. Unable to
> determine if the owner (PULIZ04\Administrator) of job DB Backup Job for DB
> Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could
not
> obtain information about Windows NT group/user 'PULIZ04\Administrator'.
> [SQLSTATE 42000] (Error 8198)).

Error in event viewer

I saw in the event viewer an error telling me that there are more than 8
connections and that the system performance could get worse.
It isn't a trouble with the number of licenses because there are more than
users.
What's happening?
Thank you very muchYou are running personal edition or MSDE and that is indeed performance
throttled after 5-8 users concurrently executing queries. As you see these
warnings, you see an indication that you will possibly benefit
performance-wise by installing a "proper" SQL Server, like Standard Edition
or Enterprise Edition.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Alberto" <alberto@.nospam.com> wrote in message
news:ewptdhkvDHA.3216@.TK2MSFTNGP11.phx.gbl...
> I saw in the event viewer an error telling me that there are more than 8
> connections and that the system performance could get worse.
> It isn't a trouble with the number of licenses because there are more than
> users.
> What's happening?
> Thank you very much
>

Error in Event Viewer

I am having trouble backing up my SQL DBs using Retrospect software to a NAS
box. I am thinking this error might have something to do with it. What doe
s
it mean? Thanks for any help!
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan1'' (0xAE93FC57F4BBB24EAC6F90AD165B993F) - Status: Failed -
Invoked on: 2004-11-19 02:00:01 - Message: The job failed. Unable to
determine if the owner (PULIZ04\Administrator) of job DB Backup Job for DB
Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could not
obtain information about Windows NT group/user 'PULIZ04\Administrator'.
[SQLSTATE 42000] (Error 8198)).The maintenance plan has been made with a user who probably doesn't exist
anymore.
You might try to edit the maintenance plan and use a user name and password
with full admin rights at
the database. Simply right click the maintenance plan and choose edit
properties. Within the properties it's possible to edit the user.
Regards,
Johan
"scottdog129" <scottdog129@.discussions.microsoft.com> schreef in bericht
news:6E7E1780-9C65-49F6-AFE1-088266C1920C@.microsoft.com...
> I am having trouble backing up my SQL DBs using Retrospect software to a
NAS
> box. I am thinking this error might have something to do with it. What
does
> it mean? Thanks for any help!
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan1'' (0xAE93FC57F4BBB24EAC6F90AD165B993F) - Status:
Failed -
> Invoked on: 2004-11-19 02:00:01 - Message: The job failed. Unable to
> determine if the owner (PULIZ04\Administrator) of job DB Backup Job for DB
> Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could
not
> obtain information about Windows NT group/user 'PULIZ04\Administrator'.
> [SQLSTATE 42000] (Error 8198)).|||Yes, that is the resason for your backup failure. That happens now and then
and there are different causes and fixes. The best way is to avoid such a
problem by changing your job owner to a SQL login such as sa.
Gary
"scottdog129" <scottdog129@.discussions.microsoft.com> wrote in message
news:6E7E1780-9C65-49F6-AFE1-088266C1920C@.microsoft.com...
> I am having trouble backing up my SQL DBs using Retrospect software to a
NAS
> box. I am thinking this error might have something to do with it. What
does
> it mean? Thanks for any help!
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan1'' (0xAE93FC57F4BBB24EAC6F90AD165B993F) - Status:
Failed -
> Invoked on: 2004-11-19 02:00:01 - Message: The job failed. Unable to
> determine if the owner (PULIZ04\Administrator) of job DB Backup Job for DB
> Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could
not
> obtain information about Windows NT group/user 'PULIZ04\Administrator'.
> [SQLSTATE 42000] (Error 8198)).

Error In Event Viewer

Hi I am getting the following error:

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 4/14/2004
Time: 09:32:05 AM
User: SYSTEM
Computer: BSEW2k01
Description:
Error: 50000, Severity: 5, State: 1
Error Calling StatusToStreet In DCS0 Code 7202

Please help.

ThanksThe error doesn't seems to be a system generated as its a user-defined from the application, check the vendor for that application.|||And I would venture to say that

StatusToStreet

Is the sproc and

DCS0

Is the database

Error in Event Viewer

I am having trouble backing up my SQL DBs using Retrospect software to a NAS
box. I am thinking this error might have something to do with it. What does
it mean? Thanks for any help!
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan1'' (0xAE93FC57F4BBB24EAC6F90AD165B993F) - Status: Failed -
Invoked on: 2004-11-19 02:00:01 - Message: The job failed. Unable to
determine if the owner (PULIZ04\Administrator) of job DB Backup Job for DB
Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could not
obtain information about Windows NT group/user 'PULIZ04\Administrator'.
[SQLSTATE 42000] (Error 8198)).The maintenance plan has been made with a user who probably doesn't exist
anymore.
You might try to edit the maintenance plan and use a user name and password
with full admin rights at
the database. Simply right click the maintenance plan and choose edit
properties. Within the properties it's possible to edit the user.
Regards,
Johan
"scottdog129" <scottdog129@.discussions.microsoft.com> schreef in bericht
news:6E7E1780-9C65-49F6-AFE1-088266C1920C@.microsoft.com...
> I am having trouble backing up my SQL DBs using Retrospect software to a
NAS
> box. I am thinking this error might have something to do with it. What
does
> it mean? Thanks for any help!
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan1'' (0xAE93FC57F4BBB24EAC6F90AD165B993F) - Status:
Failed -
> Invoked on: 2004-11-19 02:00:01 - Message: The job failed. Unable to
> determine if the owner (PULIZ04\Administrator) of job DB Backup Job for DB
> Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could
not
> obtain information about Windows NT group/user 'PULIZ04\Administrator'.
> [SQLSTATE 42000] (Error 8198)).|||Yes, that is the resason for your backup failure. That happens now and then
and there are different causes and fixes. The best way is to avoid such a
problem by changing your job owner to a SQL login such as sa.
Gary
"scottdog129" <scottdog129@.discussions.microsoft.com> wrote in message
news:6E7E1780-9C65-49F6-AFE1-088266C1920C@.microsoft.com...
> I am having trouble backing up my SQL DBs using Retrospect software to a
NAS
> box. I am thinking this error might have something to do with it. What
does
> it mean? Thanks for any help!
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan1'' (0xAE93FC57F4BBB24EAC6F90AD165B993F) - Status:
Failed -
> Invoked on: 2004-11-19 02:00:01 - Message: The job failed. Unable to
> determine if the owner (PULIZ04\Administrator) of job DB Backup Job for DB
> Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could
not
> obtain information about Windows NT group/user 'PULIZ04\Administrator'.
> [SQLSTATE 42000] (Error 8198)).

error in event log

running windows 2003 server, Sql 2000 sp3 and WSS 2.0. I have been getting
the following error. Any ideas on hot to fix it? Also sometimes I cant
connect to the DB using sql mamanger but if I restart the db I can connect.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/9/2004
Time: 3:10:58 PM
User: NA\SqlServerAccount
Computer: CINSQLWSS1
Description:
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 8b 45 00 00 14 00 00 00 ?E.....
0008: 0b 00 00 00 43 00 49 00 ...C.I.
0010: 4e 00 53 00 51 00 4c 00 N.S.Q.L.
0018: 57 00 53 00 53 00 31 00 W.S.S.1.
0020: 00 00 1a 00 00 00 53 00 .....S.
0028: 54 00 53 00 5f 00 63 00 T.S._.c.
0030: 69 00 6e 00 73 00 71 00 i.n.s.q.
0038: 6c 00 77 00 73 00 73 00 l.w.s.s.
0040: 31 00 5f 00 31 00 35 00 1._.1.5.
0048: 30 00 37 00 32 00 35 00 0.7.2.5.
0050: 31 00 38 00 39 00 33 00 1.8.9.3.
0058: 00 00 ..17803 indicates that you are having memory pressure. Depending on what the
SQL error logs say, the pressure could be in the main area (Buffer pool) or
the MemToLeave area.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

error in event log

running windows 2003 server, Sql 2000 sp3 and WSS 2.0. I have been getting
the following error. Any ideas on hot to fix it? Also sometimes I cant
connect to the DB using sql mamanger but if I restart the db I can connect.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/9/2004
Time: 3:10:58 PM
User: NA\SqlServerAccount
Computer: CINSQLWSS1
Description:
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 8b 45 00 00 14 00 00 00 E.....
0008: 0b 00 00 00 43 00 49 00 ...C.I.
0010: 4e 00 53 00 51 00 4c 00 N.S.Q.L.
0018: 57 00 53 00 53 00 31 00 W.S.S.1.
0020: 00 00 1a 00 00 00 53 00 .....S.
0028: 54 00 53 00 5f 00 63 00 T.S._.c.
0030: 69 00 6e 00 73 00 71 00 i.n.s.q.
0038: 6c 00 77 00 73 00 73 00 l.w.s.s.
0040: 31 00 5f 00 31 00 35 00 1._.1.5.
0048: 30 00 37 00 32 00 35 00 0.7.2.5.
0050: 31 00 38 00 39 00 33 00 1.8.9.3.
0058: 00 00 ..
17803 indicates that you are having memory pressure. Depending on what the
SQL error logs say, the pressure could be in the main area (Buffer pool) or
the MemToLeave area.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

error in event log

running windows 2003 server, Sql 2000 sp3 and WSS 2.0. I have been getting
the following error. Any ideas on hot to fix it? Also sometimes I cant
connect to the DB using sql mamanger but if I restart the db I can connect.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/9/2004
Time: 3:10:58 PM
User: NA\SqlServerAccount
Computer: CINSQLWSS1
Description:
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 8b 45 00 00 14 00 00 00 E.....
0008: 0b 00 00 00 43 00 49 00 ...C.I.
0010: 4e 00 53 00 51 00 4c 00 N.S.Q.L.
0018: 57 00 53 00 53 00 31 00 W.S.S.1.
0020: 00 00 1a 00 00 00 53 00 .....S.
0028: 54 00 53 00 5f 00 63 00 T.S._.c.
0030: 69 00 6e 00 73 00 71 00 i.n.s.q.
0038: 6c 00 77 00 73 00 73 00 l.w.s.s.
0040: 31 00 5f 00 31 00 35 00 1._.1.5.
0048: 30 00 37 00 32 00 35 00 0.7.2.5.
0050: 31 00 38 00 39 00 33 00 1.8.9.3.
0058: 00 00 ..17803 indicates that you are having memory pressure. Depending on what the
SQL error logs say, the pressure could be in the main area (Buffer pool) or
the MemToLeave area.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Sunday, February 19, 2012

Error In Application Logs

hii...
I am using SQL 2000 With sp3a on win200server.
i am getting following error in application log.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 10/31/2003
Time: 3:52:54 PM
User: N/A
Computer: BNET8
Description:
Error: 17832, Severity: 20, State: 8
Connection opened but invalid login packet(s) sent. Connection closed. Data:
0000: a8 45 00 00 14 00 00 00 =A8E.....
0008: 06 00 00 00 42 00 4e 00 ...B.N.
0010: 45 00 54 00 38 00 00 00 E.T.8...
0018: 00 00 00 00 ...
Please explain? what is this and solution.
Thanks in advanceHi ,
The error (17832) do not indicate a problem with SQL Server, but rather a
network failure, or client application problem.
17832 can happen if a client starts to connect, but never successfully
completes the attempt.
Normally this error is caused by the network failing between the time a
connection attempt is initiated, and when it completes.
You can just ignore this error incase the occurance of this error is
limited. Incase if the occurance is higher please check with your network
services.
Thanks
Hari
MCDBA
"sandi" <anonymous@.discussions.microsoft.com> wrote in message
news:057a01c3a026$9171c6a0$a301280a@.phx.gbl...
hii...
I am using SQL 2000 With sp3a on win200server.
i am getting following error in application log.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 10/31/2003
Time: 3:52:54 PM
User: N/A
Computer: BNET8
Description:
Error: 17832, Severity: 20, State: 8
Connection opened but invalid login packet(s) sent.
Connection closed.
Data:
0000: a8 45 00 00 14 00 00 00 ¨E.....
0008: 06 00 00 00 42 00 4e 00 ...B.N.
0010: 45 00 54 00 38 00 00 00 E.T.8...
0018: 00 00 00 00 ...
Please explain? what is this and solution.
Thanks in advance|||Dear Hari,
Thanks for your help.
sandi
>--Original Message--
>Hi ,
>The error (17832) do not indicate a problem with SQL Server, but rather a
>network failure, or client application problem.
>17832 can happen if a client starts to connect, but never successfully
>completes the attempt.
>Normally this error is caused by the network failing between the time a
>connection attempt is initiated, and when it completes.
>You can just ignore this error incase the occurance of this error is
>limited. Incase if the occurance is higher please check with your network
>services.
>Thanks
>Hari
>MCDBA
>"sandi" <anonymous@.discussions.microsoft.com> wrote in message
>news:057a01c3a026$9171c6a0$a301280a@.phx.gbl...
>hii...
>I am using SQL 2000 With sp3a on win200server.
>i am getting following error in application log.
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17052
>Date: 10/31/2003
>Time: 3:52:54 PM
>User: N/A
>Computer: BNET8
>Description:
>Error: 17832, Severity: 20, State: 8
>Connection opened but invalid login packet(s) sent.
>Connection closed.
>Data:
>0000: a8 45 00 00 14 00 00 00 =A8E.....
>0008: 06 00 00 00 42 00 4e 00 ...B.N.
>0010: 45 00 54 00 38 00 00 00 E.T.8...
>0018: 00 00 00 00 ...
>Please explain? what is this and solution.
>Thanks in advance
>
>.
>

Error importing excel file

When ever importing a excel file or flat file, I get an Unhandled exception error and the event log reads a .Netframework error ID 1000.

Checking the database I was importing into, I find that the table was created with the columns, but no data within the columns.

The import wizards report 509 row copyed before crashing with the Handle error, where a dialog box appears allowing debug or close.

Can anyone help?

I include the logged errors.

Event Log

.NET Runtime 2.0 Error
Event ID: 1000

Faulting application dtswizard.exe, version 9.0.1399.0, stamp 434f5e2a, faulting module dtspipeline.dll, version 2005.90.1399.0, stamp 434f5dbc, debug? 0, fault address 0x0004ba38.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 64 00 74 00 73 00 .d.t.s.
0030: 77 00 69 00 7a 00 61 00 w.i.z.a.
0038: 72 00 64 00 2e 00 65 00 r.d...e.
0040: 78 00 65 00 20 00 39 00 x.e. .9.
0048: 2e 00 30 00 2e 00 31 00 ..0...1.
0050: 33 00 39 00 39 00 2e 00 3.9.9...
0058: 30 00 20 00 34 00 33 00 0. .4.3.
0060: 34 00 66 00 35 00 65 00 4.f.5.e.
0068: 32 00 61 00 20 00 69 00 2.a. .i.
0070: 6e 00 20 00 64 00 74 00 n. .d.t.
0078: 73 00 70 00 69 00 70 00 s.p.i.p.
0080: 65 00 6c 00 69 00 6e 00 e.l.i.n.
0088: 65 00 2e 00 64 00 6c 00 e...d.l.
0090: 6c 00 20 00 32 00 30 00 l. .2.0.
0098: 30 00 35 00 2e 00 39 00 0.5...9.
00a0: 30 00 2e 00 31 00 33 00 0...1.3.
00a8: 39 00 39 00 2e 00 30 00 9.9...0.
00b0: 20 00 34 00 33 00 34 00 .4.3.4.
00b8: 66 00 35 00 64 00 62 00 f.5.d.b.
00c0: 63 00 20 00 66 00 44 00 c. .f.D.
00c8: 65 00 62 00 75 00 67 00 e.b.u.g.
00d0: 20 00 30 00 20 00 61 00 .0. .a.
00d8: 74 00 20 00 6f 00 66 00 t. .o.f.
00e0: 66 00 73 00 65 00 74 00 f.s.e.t.
00e8: 20 00 30 00 30 00 30 00 .0.0.0.
00f0: 34 00 62 00 61 00 33 00 4.b.a.3.
00f8: 38 00 0d 00 0a 00 8.....

Debug Log

Unhandled exception at 0x2357ba38 in DTSWizard.exe: 0xC000001D: Illegal Instruction.

Would you be able to help us nail down this problem by identifying what data is exactly causing this crash?

You can do this by reducing the data set in your spreadsheet (i.e. take 10 rows around the row #509 and see if the problem reproes, than try to find the exact row, then the exact column if possible) and figuring out what is the data and data type of the cell that could not be handled.

In the case you can give us the entire spreadsheet or the minimal piece that still reproes the problem; we could start our investigation from there.

Thanks.

|||

Hi

I have cut down the excel file, still no luck. I have even created a new excel file with two columns and two rows and I still get the error. I have noticed the test file I created "test.xls" is imported with a $ "test$" .

test.xls

Temp Contract 1 231 2 234

This should be simple to import.

John

|||

Well, this is quite simple data and it should not cause any problem. It worked for me quite easy.

Could it be possible that you have some problems with your installation/binaries? What edition of SQL Server do you have installed? Have you installed some previous versions on the same machine?

|||

Bob,

Here are the version information:

Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.3790.1830
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

There was no prevoius installations of SQL, However after installing SQL2005 I installed the MSDN disk that came with it, I believe there was an error, I uninstalled and re-install MSDN without any errors "Installation Successful".

John

Friday, February 17, 2012

Error ID 19011

Platform: Windows 2000 Server SP3
Hi,
I noticed the following error event in the Application Log
of our database server (SQL 2000 Server SP3) for the first
time three days ago:
Error ID: 19011
Source: MSSQLServer
SuperSocket info: ConnectionListen(Shared-Memory (LPC)) :
Error 5.
This error appeared right after I shut down and restarted
the database, using the SQL Server Service Manager. I
always do this to backup the database, but never get the
error message.
I would appreciate if anyone could help.
ThanksAmir\
This is comment of Bill Cheng [MSFT]
According to my check, "SpnRegister" is to register in Active Directory.
8344 indicates insufficient access rights to perform the operation.
According to my experience, if the account starting SQL Server service does
not have enough permissions, it may also this message: SuperSocket Info:
Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) : Error 10013 (An
attempt was made to access a socket in a way forbidden by its access
permissions.).
Could you check the account that starts SQL Server service? Make sure it
has enough permissions. Try to add it to LOCAL ADMINISTRATORS group to
check.
For more information on DsWriteAccountSpn ,visit the following Microsoft
website:
http://msdn.microsoft.com/library/d...-us/netdir/ad/d
swriteaccountspn.asp
"Amir M." <anonymous@.discussions.microsoft.com> wrote in message
news:df0901c40b68$d7e17d80$a501280a@.phx.gbl...
> Platform: Windows 2000 Server SP3
> Hi,
> I noticed the following error event in the Application Log
> of our database server (SQL 2000 Server SP3) for the first
> time three days ago:
> Error ID: 19011
> Source: MSSQLServer
> SuperSocket info: ConnectionListen(Shared-Memory (LPC)) :
> Error 5.
> This error appeared right after I shut down and restarted
> the database, using the SQL Server Service Manager. I
> always do this to backup the database, but never get the
> error message.
> I would appreciate if anyone could help.
> Thanks
>|||Thanks for the reply.
If it's a permission issue, then why the error message
didn't used to appear before?
Do you know how to find out the name of the SQL account?
Is it an account that was created by someone or is it
built in? Is it a domain account?
Thanks

>--Original Message--
>Amir\
>This is comment of Bill Cheng [MSFT]
>According to my check, "SpnRegister" is to register in
Active Directory.
>8344 indicates insufficient access rights to perform the
operation.
>According to my experience, if the account starting SQL
Server service does
>not have enough permissions, it may also this message:
SuperSocket Info:
>Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) :
Error 10013 (An
>attempt was made to access a socket in a way forbidden by
its access
>permissions.).
>Could you check the account that starts SQL Server
service? Make sure it
>has enough permissions. Try to add it to LOCAL
ADMINISTRATORS group to
>check.
>For more information on DsWriteAccountSpn ,visit the
following Microsoft
>website:
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/netdir/ad/d
>swriteaccountspn.asp
>
>
>
>"Amir M." <anonymous@.discussions.microsoft.com> wrote in
message
>news:df0901c40b68$d7e17d80$a501280a@.phx.gbl...
Log
first
(LPC)) :
restarted
>
>.
>

Wednesday, February 15, 2012

Error Handling with Execute Package Task

I have a main package that calls several other packages using Execute Package Tasks. I also have OnPreExecute, OnPostExecute, and OnError event handlers at the package level to audit the beginning and completion of each package. I want to prevent each task from bubbling up to the package event handlers as well as prevent each task from bubbling up to the main package event handlers. I've tried setting the Propagate variable for each of the event handlers to False and setting the DisableEventHandlers property of each task to True but neither solution seems to work. Is there a way to do this that I'm missing?

You have to set [System::Propogate]=false in the eenthandler of the task for which you don't want events to propogate.

Your post doesn't specify on which eventhandlers you are setting this.

-Jamie

|||

I found another thread that describes the problem I'm seeing. Here is the previous thread and, in following the thread, I'm not sure if the conclusion was that this behavior was as designed or that this is really a bug. Here is a link to the previous discussion:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=57523&SiteID=1

The problem in a nutshell is the following: There are two packages, a parent package which calls a child package using the Execute Package Task. Both packages have OnPostExecute event handlers defined at the package level to log progress with different ExecutionInstanceGUID. Even when the System::Propagate property is set to False for the child package OnPropagate event handler, the parent OnPostExecute event handler is still raised.

I guess the work around is to create an empty event handler for the Execute Package Task in the parent package and set the System::Propagate property for that empty event handler to False to prevent the main package OnPostExecute event from being raised. Since I have several Execute Package Tasks in the real solution, a better approach would be to wrap all the Execute Package Tasks in a Sequence container and create the do nothing event handler with the Propagate property set to false at the Sequence container rather than at each of the Execute Package tasks event handlers.

Does this make sense? Or is there possibly a better solution that I'm missing? Have to confess, I'm getting a bit overwhelmed by the number of possible appoaches one can use to log and audit package execution.

|||

Martin,

I cannot replicate your problem. If I set System::Propogate=FALSE on an eventhandler scoped to the child package then any events raised by the package container of the child package do not propogate to the parent package.

Note that this does NOT stop events raised by containers in the child package from propogating to the parent package. If you want to stop this from happening then set System::Propogate=FALSE on all of those containers as well.

I've also re-read your first post where you say "I want to prevent each task from bubbling up to the package event handlers ". If you only want to capture events fired by the package then you can compare System::PackageID to System::SourceID. If they are different then the event has not been raised by the package.

-Jamie

|||

Jamie,

I guess I was looking at the architecture wrong. I thought the child package was the container for all other containers in the child package and therefore, by setting Propagate to false for all child package event handlers, no events would be raised by any containers in the child package to the parent package. That doesn't seem to be the case. By creating empty event handlers for the Execute Package Task in the parent package and setting Propagate to false for the empty event handlers, events raised by child package containers are not propagated to the parent package event handlers.

We are logging to two tables. Package events in one table and tasks in another table and have created a package template to handle the plumbing. This is great stuff.

|||

Martin Mason wrote:

Jamie,

I guess I was looking at the architecture wrong. I thought the child package was the container for all other containers in the child package and therefore, by setting Propagate to false for all child package event handlers, no events would be raised by any containers in the child package to the parent package. That doesn't seem to be the case.

Yeah, System::Propogate can often be misunderstood - mainly due to the complexity of the container hierarchy. System::Propogate only stops events fired by the container that it is scoped to from propogating. It does not stop events fired by descendant containers from propogating.

Martin Mason wrote:

By creating empty event handlers for the Execute Package Task in the parent package and setting Propagate to false for the empty event handlers, events raised by child package containers are not propagated to the parent package event handlers.

I'm surprised that that is the case though. The package container and the TaskHost container on the Execute Package Task are no different from any other container and should behave the same way.

Martin Mason wrote:

We are logging to two tables. Package events in one table and tasks in another table and have created a package template to handle the plumbing. This is great stuff.

I agree. I'm a big fan of using eventhandlers for custom logging and have advocated it strongly here: http://blogs.conchango.com/jamiethomson/archive/2005/06/11/1593.aspx

-Jamie

|||

Is there an easy way to identify which "System::Propogate" variable goes with what container object? The variable names and scope are all the same? How can you tell which variable goes with which container event. When I define an OnPreExecute event for multiple containers/tasks I can't tell which "System::Propogate" variable goes with what object?

Maybe I am missing something obvious but I do not see the connection?

Thanks!

|||

Each eventhandler has a [System::Propogate] variable scoped to it. Variables called [System::Propogate] are ONLY scoped to eventhandlers, nothing else. Therefore, when you use one there can be no ambiguity about which one you are using, it is the one scoped to the eventhandler you are currently editing.

And remember that an eventhandler is, in turn, scoped to a container in the control-flow.

Does that answer the question?

-Jamie

|||

Um Kind of.

I guess I should have noted that I was referring to the variables list, located under SSIS on the toolbar? Not just when I am editing the event. I understand that when I am editing the event ssis will only show me variables that are in scope to the event/container/task but I was referring to the "ALL" Variable list, where you can view all System and user variables and set their values etc. or add new variables or to view there properties in the properties pane?

Do I make sense?

Thanks!

Error Handling with Execute Package Task

I have a main package that calls several other packages using Execute Package Tasks. I also have OnPreExecute, OnPostExecute, and OnError event handlers at the package level to audit the beginning and completion of each package. I want to prevent each task from bubbling up to the package event handlers as well as prevent each task from bubbling up to the main package event handlers. I've tried setting the Propagate variable for each of the event handlers to False and setting the DisableEventHandlers property of each task to True but neither solution seems to work. Is there a way to do this that I'm missing?

You have to set [System::Propogate]=false in the eenthandler of the task for which you don't want events to propogate.

Your post doesn't specify on which eventhandlers you are setting this.

-Jamie

|||

I found another thread that describes the problem I'm seeing. Here is the previous thread and, in following the thread, I'm not sure if the conclusion was that this behavior was as designed or that this is really a bug. Here is a link to the previous discussion:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=57523&SiteID=1

The problem in a nutshell is the following: There are two packages, a parent package which calls a child package using the Execute Package Task. Both packages have OnPostExecute event handlers defined at the package level to log progress with different ExecutionInstanceGUID. Even when the System::Propagate property is set to False for the child package OnPropagate event handler, the parent OnPostExecute event handler is still raised.

I guess the work around is to create an empty event handler for the Execute Package Task in the parent package and set the System::Propagate property for that empty event handler to False to prevent the main package OnPostExecute event from being raised. Since I have several Execute Package Tasks in the real solution, a better approach would be to wrap all the Execute Package Tasks in a Sequence container and create the do nothing event handler with the Propagate property set to false at the Sequence container rather than at each of the Execute Package tasks event handlers.

Does this make sense? Or is there possibly a better solution that I'm missing? Have to confess, I'm getting a bit overwhelmed by the number of possible appoaches one can use to log and audit package execution.

|||

Martin,

I cannot replicate your problem. If I set System::Propogate=FALSE on an eventhandler scoped to the child package then any events raised by the package container of the child package do not propogate to the parent package.

Note that this does NOT stop events raised by containers in the child package from propogating to the parent package. If you want to stop this from happening then set System::Propogate=FALSE on all of those containers as well.

I've also re-read your first post where you say "I want to prevent each task from bubbling up to the package event handlers ". If you only want to capture events fired by the package then you can compare System::PackageID to System::SourceID. If they are different then the event has not been raised by the package.

-Jamie

|||

Jamie,

I guess I was looking at the architecture wrong. I thought the child package was the container for all other containers in the child package and therefore, by setting Propagate to false for all child package event handlers, no events would be raised by any containers in the child package to the parent package. That doesn't seem to be the case. By creating empty event handlers for the Execute Package Task in the parent package and setting Propagate to false for the empty event handlers, events raised by child package containers are not propagated to the parent package event handlers.

We are logging to two tables. Package events in one table and tasks in another table and have created a package template to handle the plumbing. This is great stuff.

|||

Martin Mason wrote:

Jamie,

I guess I was looking at the architecture wrong. I thought the child package was the container for all other containers in the child package and therefore, by setting Propagate to false for all child package event handlers, no events would be raised by any containers in the child package to the parent package. That doesn't seem to be the case.

Yeah, System::Propogate can often be misunderstood - mainly due to the complexity of the container hierarchy. System::Propogate only stops events fired by the container that it is scoped to from propogating. It does not stop events fired by descendant containers from propogating.

Martin Mason wrote:

By creating empty event handlers for the Execute Package Task in the parent package and setting Propagate to false for the empty event handlers, events raised by child package containers are not propagated to the parent package event handlers.

I'm surprised that that is the case though. The package container and the TaskHost container on the Execute Package Task are no different from any other container and should behave the same way.

Martin Mason wrote:

We are logging to two tables. Package events in one table and tasks in another table and have created a package template to handle the plumbing. This is great stuff.

I agree. I'm a big fan of using eventhandlers for custom logging and have advocated it strongly here: http://blogs.conchango.com/jamiethomson/archive/2005/06/11/1593.aspx

-Jamie

|||

Is there an easy way to identify which "System::Propogate" variable goes with what container object? The variable names and scope are all the same? How can you tell which variable goes with which container event. When I define an OnPreExecute event for multiple containers/tasks I can't tell which "System::Propogate" variable goes with what object?

Maybe I am missing something obvious but I do not see the connection?

Thanks!

|||

Each eventhandler has a [System::Propogate] variable scoped to it. Variables called [System::Propogate] are ONLY scoped to eventhandlers, nothing else. Therefore, when you use one there can be no ambiguity about which one you are using, it is the one scoped to the eventhandler you are currently editing.

And remember that an eventhandler is, in turn, scoped to a container in the control-flow.

Does that answer the question?

-Jamie

|||

Um Kind of.

I guess I should have noted that I was referring to the variables list, located under SSIS on the toolbar? Not just when I am editing the event. I understand that when I am editing the event ssis will only show me variables that are in scope to the event/container/task but I was referring to the "ALL" Variable list, where you can view all System and user variables and set their values etc. or add new variables or to view there properties in the properties pane?

Do I make sense?

Thanks!