Error 845 running backup of one database

I have one database that I keep getting an error 845: Time out ocurred while
waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
569352192, Index ID 0..
This only started happening last week. The database has not changed (other
than normal data entry) in over a year. Does anyone have any ideas of what
should be checked?
Thanks in advanceDid you see the specific recommendations in Books Online for this?
Error 845
Severity Level 17
Message Text
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, d
atabase ID %d.
Explanation
When under a heavy stress load or high I/O conditions, your system may produ
ce this message.
Action
This message can usually be ignored; however, if you receive repeated messag
es where the wait time
increases, it may indicate an internal server problem. Contact your system a
dministrator. The system
administrator should check the waittype, waittime, lastwaittype, and the wai
tresource columns of
sysprocesses to see what activities each SPIDs is performing.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Connie" <cfelt@.ga.wa.gov> wrote in message news:OcwIz0TWEHA.1144@.TK2MSFTNGP10.phx.gbl...[vb
col=seagreen]
> I have one database that I keep getting an error 845: Time out ocurred whi
le
> waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
> 569352192, Index ID 0..
> This only started happening last week. The database has not changed (othe
r
> than normal data entry) in over a year. Does anyone have any ideas of wha
t
> should be checked?
> Thanks in advance
>[/vbcol]

Error 845 running backup of one database

I have one database that I keep getting an error 845: Time out ocurred while
waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
569352192, Index ID 0..
This only started happening last week. The database has not changed (other
than normal data entry) in over a year. Does anyone have any ideas of what
should be checked?
Thanks in advance
Did you see the specific recommendations in Books Online for this?
Error 845
Severity Level 17
Message Text
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
Explanation
When under a heavy stress load or high I/O conditions, your system may produce this message.
Action
This message can usually be ignored; however, if you receive repeated messages where the wait time
increases, it may indicate an internal server problem. Contact your system administrator. The system
administrator should check the waittype, waittime, lastwaittype, and the waitresource columns of
sysprocesses to see what activities each SPIDs is performing.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Connie" <cfelt@.ga.wa.gov> wrote in message news:OcwIz0TWEHA.1144@.TK2MSFTNGP10.phx.gbl...
> I have one database that I keep getting an error 845: Time out ocurred while
> waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
> 569352192, Index ID 0..
> This only started happening last week. The database has not changed (other
> than normal data entry) in over a year. Does anyone have any ideas of what
> should be checked?
> Thanks in advance
>
sql

Error 845 running backup of one database

I have one database that I keep getting an error 845: Time out ocurred while
waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
569352192, Index ID 0..
This only started happening last week. The database has not changed (other
than normal data entry) in over a year. Does anyone have any ideas of what
should be checked?
Thanks in advanceDid you see the specific recommendations in Books Online for this?
Error 845
Severity Level 17
Message Text
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
Explanation
When under a heavy stress load or high I/O conditions, your system may produce this message.
Action
This message can usually be ignored; however, if you receive repeated messages where the wait time
increases, it may indicate an internal server problem. Contact your system administrator. The system
administrator should check the waittype, waittime, lastwaittype, and the waitresource columns of
sysprocesses to see what activities each SPIDs is performing.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Connie" <cfelt@.ga.wa.gov> wrote in message news:OcwIz0TWEHA.1144@.TK2MSFTNGP10.phx.gbl...
> I have one database that I keep getting an error 845: Time out ocurred while
> waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
> 569352192, Index ID 0..
> This only started happening last week. The database has not changed (other
> than normal data entry) in over a year. Does anyone have any ideas of what
> should be checked?
> Thanks in advance
>

error '800a03eb' Type mismatch

Maintaining database website,its running ASP pages on windows 2003 server with SQL server 2000. I have upgraded SP2 for SQL server to SP4 in maintance process.

The problem accur with some ASP pages are

server_errors [server_Errors] GetErrorMessage [serverSERVER version 1.0.0] error '800a03eb' Type mismatch

/server/asp/cmfls/errorconfirmation.asp, line

There may be permission /security issues related with database.help me to troubleshoot my problem.

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

Error 7399: OLE DB provider Microsoft.Jet.OLEDB.4.0 reported an error.

I tried to make one with following options in enterprise manager:

Server type: Other data source
Provider name: test
Product name: Access 2000
Data source: c:\db\test.mdb
Provider string: Microsoft.Jet.OLEDB.4.0

When I try to access the linked server tables I receive following error:
Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.

When I try to make a view (select * from linkedserver1...table) I receive following error:
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Disk or network error.]

Can anyone help me? the only thing I want to do is link an access table to SQL Server (NOT sql server table in access but access table in sql server!)Have you definately got the paths setup right?

'c:\db\test.mdb' needs to be on the SQL Server machine itself and has the system got the correct permissions to access the mdb file.

If you check this and this is all OK then is it not a possibility to import your table into SQL Server?|||make sure that u are connected to you Domain Server.
and that u make a System DSN (best solution in DSN) correctly to your SQL Server.

hope this will help u
bye

Error 644 Severity level 21

Hi,
I got the following error message for one of our databases:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 3/25/2005
Time: 9:18:53 AM
User: XXXXXXXX\Administrator
Computer: XXXXXX
Description:
Error: 644, Severity: 21, State: 3
Could not find the index entry for RID '16c42dc515100' in index page
(1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
I looked up the error in Books Online and it told me to run DBCC CHECKDB to
see the extent of the damage. It gave me the following result:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for the
keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:155:91) with values (parent_obj = 1237579447 and id =
365243844) points to the data row identified by ().
DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
DBCC results for 'sysobjects'.
There are 2315 rows in 49 pages for object 'sysobjects'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysobjects' (object ID 1).
These don't seem to match. Should they?
The next thing that Books Online says to do is to run DBCC CHECKDB with the
REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
course of action given that the error reported by checkdb doesn't seem to be
the one from the event log?
One of the other dba's here said that there may be a better way to rebuild
the index than to run the repair_rebuild on the entire database. I just
wanted to double check and get some other opinions/feedback before I
continued. Any help would really be appreciated. Thank you
-John
Hi
You have corruption.
Do a full backup of the database, then run the DBCC. There is probably more
than one problem so the DBCC finds the other one first.
At the same time, look for your backups because if the corruption is bad
enough, you need to restore to you last good backup.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Rosenlof" <greyseal96@.hotmail.com> wrote in message
news:O#0LBPYMFHA.3296@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I got the following error message for one of our databases:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 3/25/2005
> Time: 9:18:53 AM
> User: XXXXXXXX\Administrator
> Computer: XXXXXX
> Description:
> Error: 644, Severity: 21, State: 3
> Could not find the index entry for RID '16c42dc515100' in index page
> (1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> I looked up the error in Books Online and it told me to run DBCC CHECKDB
to
> see the extent of the damage. It gave me the following result:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
> 'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for
the
> keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:155:91) with values (parent_obj = 1237579447 and id =
> 365243844) points to the data row identified by ().
> DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> DBCC results for 'sysobjects'.
> There are 2315 rows in 49 pages for object 'sysobjects'.
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> 'sysobjects' (object ID 1).
> These don't seem to match. Should they?
> The next thing that Books Online says to do is to run DBCC CHECKDB with
the
> REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
> course of action given that the error reported by checkdb doesn't seem to
be
> the one from the event log?
> One of the other dba's here said that there may be a better way to rebuild
> the index than to run the repair_rebuild on the entire database. I just
> wanted to double check and get some other opinions/feedback before I
> continued. Any help would really be appreciated. Thank you
> -John
>

Error 644 Severity level 21

Hi,
I got the following error message for one of our databases:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 3/25/2005
Time: 9:18:53 AM
User: XXXXXXXX\Administrator
Computer: XXXXXX
Description:
Error: 644, Severity: 21, State: 3
Could not find the index entry for RID '16c42dc515100' in index page
(1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
I looked up the error in Books Online and it told me to run DBCC CHECKDB to
see the extent of the damage. It gave me the following result:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for the
keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:155:91) with values (parent_obj = 1237579447 and id =
365243844) points to the data row identified by ().
DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
DBCC results for 'sysobjects'.
There are 2315 rows in 49 pages for object 'sysobjects'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysobjects' (object ID 1).
These don't seem to match. Should they?
The next thing that Books Online says to do is to run DBCC CHECKDB with the
REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
course of action given that the error reported by checkdb doesn't seem to be
the one from the event log?
One of the other dba's here said that there may be a better way to rebuild
the index than to run the repair_rebuild on the entire database. I just
wanted to double check and get some other opinions/feedback before I
continued. Any help would really be appreciated. Thank you
-JohnHi
You have corruption.
Do a full backup of the database, then run the DBCC. There is probably more
than one problem so the DBCC finds the other one first.
At the same time, look for your backups because if the corruption is bad
enough, you need to restore to you last good backup.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Rosenlof" <greyseal96@.hotmail.com> wrote in message
news:O#0LBPYMFHA.3296@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I got the following error message for one of our databases:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 3/25/2005
> Time: 9:18:53 AM
> User: XXXXXXXX\Administrator
> Computer: XXXXXX
> Description:
> Error: 644, Severity: 21, State: 3
> Could not find the index entry for RID '16c42dc515100' in index page
> (1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> I looked up the error in Books Online and it told me to run DBCC CHECKDB
to
> see the extent of the damage. It gave me the following result:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
> 'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for
the
> keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:155:91) with values (parent_obj = 1237579447 and id =
> 365243844) points to the data row identified by ().
> DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> DBCC results for 'sysobjects'.
> There are 2315 rows in 49 pages for object 'sysobjects'.
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> 'sysobjects' (object ID 1).
> These don't seem to match. Should they?
> The next thing that Books Online says to do is to run DBCC CHECKDB with
the
> REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
> course of action given that the error reported by checkdb doesn't seem to
be
> the one from the event log?
> One of the other dba's here said that there may be a better way to rebuild
> the index than to run the repair_rebuild on the entire database. I just
> wanted to double check and get some other opinions/feedback before I
> continued. Any help would really be appreciated. Thank you
> -John
>

Error 644 Severity level 21

Hi,
I got the following error message for one of our databases:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 3/25/2005
Time: 9:18:53 AM
User: XXXXXXXX\Administrator
Computer: XXXXXX
Description:
Error: 644, Severity: 21, State: 3
Could not find the index entry for RID '16c42dc515100' in index page
(1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
I looked up the error in Books Online and it told me to run DBCC CHECKDB to
see the extent of the damage. It gave me the following result:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for the
keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:155:91) with values (parent_obj = 1237579447 and id = 365243844) points to the data row identified by ().
DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
DBCC results for 'sysobjects'.
There are 2315 rows in 49 pages for object 'sysobjects'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysobjects' (object ID 1).
These don't seem to match. Should they?
The next thing that Books Online says to do is to run DBCC CHECKDB with the
REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
course of action given that the error reported by checkdb doesn't seem to be
the one from the event log?
One of the other dba's here said that there may be a better way to rebuild
the index than to run the repair_rebuild on the entire database. I just
wanted to double check and get some other opinions/feedback before I
continued. Any help would really be appreciated. Thank you
-JohnHi
You have corruption.
Do a full backup of the database, then run the DBCC. There is probably more
than one problem so the DBCC finds the other one first.
At the same time, look for your backups because if the corruption is bad
enough, you need to restore to you last good backup.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Rosenlof" <greyseal96@.hotmail.com> wrote in message
news:O#0LBPYMFHA.3296@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I got the following error message for one of our databases:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 3/25/2005
> Time: 9:18:53 AM
> User: XXXXXXXX\Administrator
> Computer: XXXXXX
> Description:
> Error: 644, Severity: 21, State: 3
> Could not find the index entry for RID '16c42dc515100' in index page
> (1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> I looked up the error in Books Online and it told me to run DBCC CHECKDB
to
> see the extent of the damage. It gave me the following result:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
> 'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for
the
> keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:155:91) with values (parent_obj = 1237579447 and id => 365243844) points to the data row identified by ().
> DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> DBCC results for 'sysobjects'.
> There are 2315 rows in 49 pages for object 'sysobjects'.
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> 'sysobjects' (object ID 1).
> These don't seem to match. Should they?
> The next thing that Books Online says to do is to run DBCC CHECKDB with
the
> REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
> course of action given that the error reported by checkdb doesn't seem to
be
> the one from the event log?
> One of the other dba's here said that there may be a better way to rebuild
> the index than to run the repair_rebuild on the entire database. I just
> wanted to double check and get some other opinions/feedback before I
> continued. Any help would really be appreciated. Thank you
> -John
>

Error 627:Cannot use SAVE TRANSACTION within a distributed transac

Information:
SQL Server 2000 Enterprise Edition
Server Pack 3a
Server Edition is Windows 2000 Advanced Server
Replication Type is Transactional
I am trying to drop a publication. I am getting the error:
Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
This error also is generated when trying to drop the individual subscription.
Can anyone provide insight as to what could be causing this error?
Thank you in advance.
Robert M.Check the "remote proc trans" value from sp_configure. If it's 1, you need
to change it to 0.
"Robert M." <RobertM@.discussions.microsoft.com> wrote in message
news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> Information:
> SQL Server 2000 Enterprise Edition
> Server Pack 3a
> Server Edition is Windows 2000 Advanced Server
> Replication Type is Transactional
> I am trying to drop a publication. I am getting the error:
> Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> This error also is generated when trying to drop the individual
subscription.
> Can anyone provide insight as to what could be causing this error?
> Thank you in advance.
> Robert M.
>|||I am assuming that the 'remote proc trans' setting needs to be set to zero on
the publisher (i have separate servers for distributor/publisher/subscriber).
Thanks...Robert M.
"Richard Ding" wrote:
> Check the "remote proc trans" value from sp_configure. If it's 1, you need
> to change it to 0.
>
> "Robert M." <RobertM@.discussions.microsoft.com> wrote in message
> news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> > Information:
> > SQL Server 2000 Enterprise Edition
> > Server Pack 3a
> > Server Edition is Windows 2000 Advanced Server
> > Replication Type is Transactional
> >
> > I am trying to drop a publication. I am getting the error:
> > Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> >
> > This error also is generated when trying to drop the individual
> subscription.
> >
> > Can anyone provide insight as to what could be causing this error?
> >
> > Thank you in advance.
> >
> > Robert M.
> >
> >
>
>|||Actually, I believe it should be set to 0 on the subscriber. No need to
touch the values on publisher or distributor.
"Robert M." <RobertM@.discussions.microsoft.com> wrote in message
news:4A56EC3F-0537-441C-990E-0C7D43BD972C@.microsoft.com...
> I am assuming that the 'remote proc trans' setting needs to be set to zero
on
> the publisher (i have separate servers for
distributor/publisher/subscriber).
> Thanks...Robert M.
> "Richard Ding" wrote:
> > Check the "remote proc trans" value from sp_configure. If it's 1, you
need
> > to change it to 0.
> >
> >
> > "Robert M." <RobertM@.discussions.microsoft.com> wrote in message
> > news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> > > Information:
> > > SQL Server 2000 Enterprise Edition
> > > Server Pack 3a
> > > Server Edition is Windows 2000 Advanced Server
> > > Replication Type is Transactional
> > >
> > > I am trying to drop a publication. I am getting the error:
> > > Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> > >
> > > This error also is generated when trying to drop the individual
> > subscription.
> > >
> > > Can anyone provide insight as to what could be causing this error?
> > >
> > > Thank you in advance.
> > >
> > > Robert M.
> > >
> > >
> >
> >
> >

Error 56

This morning, within the space of just a few minutes, we got a WHOLE lot of
these errors:
Event Type: Warning
Event Source: mraid35x
Event Category: None
Event ID: 56
Date: 1/27/2005
Time: 7:06:27 AM
User: N/A
Computer: SQL
Description:
The driver failed to allocate memory.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 10 00 01 00 66 00 .....f.
0008: 00 00 00 00 38 00 04 80 ...8..?
0010: 10 00 00 00 9a 00 00 c0 ...?..À
0018: 00 00 00 00 00 00 00 00 ......
0020: 00 00 00 00 00 00 00 00 ......
0028: 53 63 50 44 e0 01 00 00 ScPDà...
0030: 6c 69 74 75 b4 06 00 00 litu´...
I can't find any information regarding this error. We're running SQL on a
Windows 2003 server.
Thank you for your attention
mHello
Well, the first thing we are going to want to do is run chkdsk /f /r on the
server
to hopefully clear up the NTFS and FTDISK errors on the drive.
This will require a server reboot and could take over an hour to complete.
Next, we need you to delete and recreate your pagefile.sys. To do this,
1) When the Chkdsk.exe utility has completed, set the paging file size to 0.
a. Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b. In the Initial Size (MB): box, type "0" (without the quotation marks).
c. In the Maximum Size (MB): box, type "0" (without the quotation marks).
d. Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
2) After the computer has restarted, reset the Pagefile.sys file to the
correct
size.
a. Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b. In the Initial Size (MB): box, type a value equal to the amount of
random
access memory (in megabytes) in your computer plus 11.
c. In the Maximum Size (MB): box, type a value equal to or less than the
amount of
disk space available (in megabytes) on the specified partition minus 1.
d. Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
Hopefully this will correct the NTFS, FTDISK, and errors with your Promise
Controller.
If not, we will need to continue investigating further and review your next
memory.dmp file.
Let me know when you have completed the above actions.
Best Regards,
Regev Avivi (Mcse)
http://www.regevnet.com
<-- Please reply to the NewsGroup only -->

Error 56

This morning, within the space of just a few minutes, we got a WHOLE lot of
these errors:
Event Type: Warning
Event Source: mraid35x
Event Category: None
Event ID: 56
Date: 1/27/2005
Time: 7:06:27 AM
User: N/A
Computer: SQL
Description:
The driver failed to allocate memory.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 10 00 01 00 66 00 .....f.
0008: 00 00 00 00 38 00 04 80 ...8..
0010: 10 00 00 00 9a 00 00 c0 .....
0018: 00 00 00 00 00 00 00 00 ......
0020: 00 00 00 00 00 00 00 00 ......
0028: 53 63 50 44 e0 01 00 00 ScPD...
0030: 6c 69 74 75 b4 06 00 00 litu...
I can't find any information regarding this error. We're running SQL on a
Windows 2003 server.
Thank you for your attention
mHello
Well, the first thing we are going to want to do is run chkdsk /f /r on the
server
to hopefully clear up the NTFS and FTDISK errors on the drive.
This will require a server reboot and could take over an hour to complete.
Next, we need you to delete and recreate your pagefile.sys. To do this,
1) When the Chkdsk.exe utility has completed, set the paging file size to 0.
a. Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b. In the Initial Size (MB): box, type "0" (without the quotation marks).
c. In the Maximum Size (MB): box, type "0" (without the quotation marks).
d. Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
2) After the computer has restarted, reset the Pagefile.sys file to the
correct
size.
a. Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b. In the Initial Size (MB): box, type a value equal to the amount of
random
access memory (in megabytes) in your computer plus 11.
c. In the Maximum Size (MB): box, type a value equal to or less than the
amount of
disk space available (in megabytes) on the specified partition minus 1.
d. Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
Hopefully this will correct the NTFS, FTDISK, and errors with your Promise
Controller.
If not, we will need to continue investigating further and review your next
memory.dmp file.
Let me know when you have completed the above actions.
Best Regards,
Regev Avivi (Mcse)
http://www.regevnet.com
<-- Please reply to the NewsGroup only -->

Error 56

This morning, within the space of just a few minutes, we got a WHOLE lot of
these errors:
Event Type: Warning
Event Source: mraid35x
Event Category: None
Event ID: 56
Date: 1/27/2005
Time: 7:06:27 AM
User: N/A
Computer: SQL
Description:
The driver failed to allocate memory.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 10 00 01 00 66 00 .....f.
0008: 00 00 00 00 38 00 04 80 ...8..
0010: 10 00 00 00 9a 00 00 c0 .....
0018: 00 00 00 00 00 00 00 00 ......
0020: 00 00 00 00 00 00 00 00 ......
0028: 53 63 50 44 e0 01 00 00 ScPD...
0030: 6c 69 74 75 b4 06 00 00 litu...
I can't find any information regarding this error. We're running SQL on a
Windows 2003 server.
Thank you for your attention
m
Hello
Well, the first thing we are going to want to do is run chkdsk /f /r on the
server
to hopefully clear up the NTFS and FTDISK errors on the drive.
This will require a server reboot and could take over an hour to complete.
Next, we need you to delete and recreate your pagefile.sys. To do this,
1) When the Chkdsk.exe utility has completed, set the paging file size to 0.
a.Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b.In the Initial Size (MB): box, type "0" (without the quotation marks).
c.In the Maximum Size (MB): box, type "0" (without the quotation marks).
d.Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
2) After the computer has restarted, reset the Pagefile.sys file to the
correct
size.
a.Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b.In the Initial Size (MB): box, type a value equal to the amount of
random
access memory (in megabytes) in your computer plus 11.
c.In the Maximum Size (MB): box, type a value equal to or less than the
amount of
disk space available (in megabytes) on the specified partition minus 1.
d.Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
Hopefully this will correct the NTFS, FTDISK, and errors with your Promise
Controller.
If not, we will need to continue investigating further and review your next
memory.dmp file.
Let me know when you have completed the above actions.
Best Regards,
Regev Avivi (Mcse)
http://www.regevnet.com
<-- Please reply to the NewsGroup only -->

Error 409: The assignment operator operation could not take a text data type as an argumen

How can I make it work when I need to pull out a field which is text type using a stored procedure? Please help!!!Thanks
I am getting the following error
Error 409: The assignment operator operation could not take a text data type as an argument
===========my sp=================================
CREATE PROCEDURE [dbo].[sp_SelectABC]
(@.a varchar(50) output,
@.b text output
)
AS
set nocount on
select @.a=name, @.b= description from ABC

GONo, you can't do that.

You're going to have to replace it with

select name, description from ABC

error 30311: Value of type 'System.DBNull' cannot be converted to 'Date'

I'm creating an ISP for extractig data from a text file and put it in a database.

One of the fields in my textfile contains the value '0' or a date. If it's '0' it should be converted to the Null Value. The column in which it has to be saved is of type smalldatetime.

This is the code of my script where I want to check the value of the field in my textfile and convert it to a date or to Null.

Public Overrides Sub Input0_ProcessInputRow(ByVal Row As Input0Buffer)

If Row.cdDateIn = "" Or Row.cdDateIn= "0" Then

Row.cdDateInCorr = CDate(DBNull.Value)

ElseIf Row.cdDateIn_IsNull Then

Row.cdDateInCorr = CDate(DBNull.Value)

Else

Row.cdDateInCorr = CDate(Row.cdDateIn)

End If

End Sub

The error that I get is:

Validation error. Extract FinCD: Conversion of cdDateIn [753]: Eroor 30311: Value of type 'System.DBNull' cannot ben converted to 'Date'.

How do I resolve this problem ?

Why not use a derived column? Expression follows: (Typing from memory)

cdDateIn == "" || cdDateIn == "0" || ISNULL(cdDateIn) ? NULL(DT_DBTIMESTAMP) : (DT_DBTIMESTAMP)cdDateIn

|||You can just set Row.cdDateInCorr_IsNull = true.
|||

JayH wrote:

You can just set Row.cdDateInCorr_IsNull = true.

Correct, though if this is all you're doing in the script component, I would stay away from that and use a derived column. There's no reason for the overhead of the script in this case.

|||

I've used the code JayH suggested and this works.

Phil, your code is a bit like chinese to me. This ISP I'm working on is my first project in .NET. But I will check this derived column thing.

Thanks four your help.

|||

Phil Brammer wrote:

JayH wrote:

You can just set Row.cdDateInCorr_IsNull = true.

Correct, though if this is all you're doing in the script component, I would stay away from that and use a derived column. There's no reason for the overhead of the script in this case.

Are you sure about this - the IsNull property is for evaluation and not for assigning true or false to it - I believe that it will reset itself when you leave the script task - or am I wrong?
|||

Simon Givoni wrote:

Phil Brammer wrote:

JayH wrote:

You can just set Row.cdDateInCorr_IsNull = true.

Correct, though if this is all you're doing in the script component, I would stay away from that and use a derived column. There's no reason for the overhead of the script in this case.

Are you sure about this - the IsNull property is for evaluation and not for assigning true or false to it - I believe that it will reset itself when you leave the script task - or am I wrong?

Yes, I'm sure. You can set the property to True and the null will stick. You cannot set it to False, but it will automatically become False if you set a value to the column. SP2 will raise an exception if you set it to False.

|||Ah yes you are right - here are the full explanation:

The IsNull property of columns in the Script Component now raises a warning when it is used incorrectly.
The code generated by the Script component contains a <columnname> and a <columnname>_IsNull property for each input and output column. The intention of the <columnname>_IsNull property is to allow the user to specify a Null value for the column by setting the value of the property to True. To specify a non-null value, the user should assign a value to the <columnname> property. In earlier versions, if you set <columnname>_IsNull to False, the property was silently reset to True. In SP2, the Script component raises a warning message about the incorrect usage.

Source: http://msdn2.microsoft.com/en-us/library/bb283536.aspx#BKMK_IntegrationServices

Error 208

Hi,
every morning about 06.03 AM in DB PROBA there is the follow error:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/1/2006
Time: 6:03:22 AM
User: N/A
Description:
name database: PROVA
Error: 208, Severity: 16, State: 0
Invalid object name '#tmp'.
Someone can help me to understand the reason of the error...
Thanks a lotLuca (artematico@.yahoo.it) writes:
> every morning about 06.03 AM in DB PROBA there is the follow error:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/1/2006
> Time: 6:03:22 AM
> User: N/A
> Description:
> name database: PROVA
> Error: 208, Severity: 16, State: 0
> Invalid object name '#tmp'.
> Someone can help me to understand the reason of the error...
I would check for scheduled jobs running at this time.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||I assume that this is a scheduled job
The job is looking for a temporary table #tmp, this object does not
exists, it either got dropped, is out of scope or got never created
Open up QA and run this
select * from #tmp
you will see this error message
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name '#tmp'.
Take a look at the code and try to figure out if it's the object is
misspelled by mistake #tmp instead of #temp
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Luca wrote:
> Hi,
> every morning about 06.03 AM in DB PROBA there is the follow error:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/1/2006
> Time: 6:03:22 AM
> User: N/A
> Description:
> name database: PROVA
> Error: 208, Severity: 16, State: 0
> Invalid object name '#tmp'.
> Someone can help me to understand the reason of the error...
> Thanks a lot|||SQL Menace ha scritto:

> I assume that this is a scheduled job
> The job is looking for a temporary table #tmp, this object does not
> exists, it either got dropped, is out of scope or got never created
> Open up QA and run this
> select * from #tmp
> you will see this error message
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name '#tmp'.
> Take a look at the code and try to figure out if it's the object is
> misspelled by mistake #tmp instead of #temp
I run this
select * from '#tmp
but there is the same error:
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name '#temp'.
> Denis the SQL Menace
> http://sqlservercode.blogspot.com/
>
> Luca wrote:|||Yes you will get that error since the temp table does not exist for
your connection
Whatever code runs at that time, open it up and look where #tmp is
referenced
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Luca wrote:
> SQL Menace ha scritto:
>
> I run this
> select * from '#tmp
> but there is the same error:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name '#temp'.
>|||SQL Menace ha scritto:

> Yes you will get that error since the temp table does not exist for
> your connection
> Whatever code runs at that time, open it up and look where #tmp is
> referenced
The code runs at 06.00 AM, how can I look where #tmp is referenced?
>
> Denis the SQL Menace
> http://sqlservercode.blogspot.com/
>
> Luca wrote:|||Enterprise Manager-->management-->SQL server Agent-->Jobs
You will see a bunch of icons in blue (succes) or Red (failed)
One of the red ones is the one that uses #tmp (you can also scroll to
the right and look at the next run date column, that will have the date
and time there)
The double click on the job, click on the steps tab and double click
step1 (it will be blue)
If the code looks like this EXECUTE master.dbo.xp_sqlmaint N'-PlanID
2C6BA936-F50A-42F9-AFA5-B88BC0251AF3 -Rpt "d:\MSSQL\LOG\DB Maintenance
Plan10.txt" -DelTxtRpt 1WEEKS -WriteHistory -RebldIdx 10
-RmUnusedSpace 50 10 ' then it is s maintainance plan and maybe you ran
out of space on your hard disk and the object could not be created
Delete stuff you don't need or move some tables to another
filegroup/hard drive (if you have multiple drives)
Or put tempdb on it's own hardrive and the LOG files also on their own
hard drive
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Luca wrote:
> SQL Menace ha scritto:
>
> The code runs at 06.00 AM, how can I look where #tmp is referenced?
>|||SQL Menace ha scritto:

> Enterprise Manager-->management-->SQL server Agent-->Jobs
> You will see a bunch of icons in blue (succes) or Red (failed)
> One of the red ones is the one that uses #tmp (you can also scroll to
> the right and look at the next run date column, that will have the date
> and time there)
There isn't any red icons, they are all blu
> The double click on the job, click on the steps tab and double click
> step1 (it will be blue)
> If the code looks like this EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 2C6BA936-F50A-42F9-AFA5-B88BC0251AF3 -Rpt "d:\MSSQL\LOG\DB Maintenance
> Plan10.txt" -DelTxtRpt 1WEEKS -WriteHistory -RebldIdx 10
> -RmUnusedSpace 50 10 ' then it is s maintainance plan and maybe you ran
> out of space on your hard disk and the object could not be created
> Delete stuff you don't need or move some tables to another
> filegroup/hard drive (if you have multiple drives)
> Or put tempdb on it's own hardrive and the LOG files also on their own
> hard drive
>
> Denis the SQL Menace
> http://sqlservercode.blogspot.com/
> Luca wrote:|||Luca (artematico@.yahoo.it) writes:
> There isn't any red icons, they are all blu
You may have to inspect the job history. The job could be set up so
that it continues with the next step even on error. Or it runs a second
time, and this time it's successful.
In any case, as long everything else appears to be working normally on
your sever, it may not be worth the effort to track this down.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx