Showing posts with label odbc. Show all posts
Showing posts with label odbc. Show all posts

Thursday, March 29, 2012

Error 945: Cannot Be Opened Because...

I'm getting this error message all of a sudden:
MS SQL-DMO (ODBC SQL State: 42000)
Error 945: Database "Database Name" cannot be opened
because some of the files could not be activated.
Can anybody help me here?
My phone number is (714)513-3038...my name is Dorsey
Richardson..
e-mail: oldmoney@.geologistics.com
Thanks in advance..
Dorsey
Dorsey,
There is a BOL topic on error 945. On the net you can find it at:
http://tinyurl.com/4wvmv
This has 4 cases that might be the cause and actions for each.
Russell Fields
"Dorsey Richardson" <anonymous@.discussions.microsoft.com> wrote in message
news:027b01c48ba8$4c2c3a30$a401280a@.phx.gbl...
> I'm getting this error message all of a sudden:
> MS SQL-DMO (ODBC SQL State: 42000)
> Error 945: Database "Database Name" cannot be opened
> because some of the files could not be activated.
> Can anybody help me here?
> My phone number is (714)513-3038...my name is Dorsey
> Richardson..
> e-mail: oldmoney@.geologistics.com
> Thanks in advance..
> Dorsey
|||Dorsey,
Russell gave you a link and four possibly actions. None of the four gave the actual error. Did you find one the solved your problem? I have the same error message as you do.
Michael Meyers

Quote:

Originally posted by Dorsey Richardson
I'm getting this error message all of a sudden:
MS SQL-DMO (ODBC SQL State: 42000)
Error 945: Database "Database Name" cannot be opened
because some of the files could not be activated.
Can anybody help me here?
My phone number is (714)513-3038...my name is Dorsey
Richardson..
e-mail: oldmoney@.geologistics.com
Thanks in advance..
Dorsey

Error 945: Cannot Be Opened Because...

I'm getting this error message all of a sudden:
MS SQL-DMO (ODBC SQL State: 42000)
Error 945: Database "Database Name" cannot be opened
because some of the files could not be activated.
Can anybody help me here?
My phone number is (714)513-3038...my name is Dorsey
Richardson..
e-mail: oldmoney@.geologistics.com
Thanks in advance..
DorseyDorsey,
There is a BOL topic on error 945. On the net you can find it at:
http://tinyurl.com/4wvmv
This has 4 cases that might be the cause and actions for each.
Russell Fields
"Dorsey Richardson" <anonymous@.discussions.microsoft.com> wrote in message
news:027b01c48ba8$4c2c3a30$a401280a@.phx.gbl...
> I'm getting this error message all of a sudden:
> MS SQL-DMO (ODBC SQL State: 42000)
> Error 945: Database "Database Name" cannot be opened
> because some of the files could not be activated.
> Can anybody help me here?
> My phone number is (714)513-3038...my name is Dorsey
> Richardson..
> e-mail: oldmoney@.geologistics.com
> Thanks in advance..
> Dorsey

Error 945: Cannot Be Opened Because...

I'm getting this error message all of a sudden:
MS SQL-DMO (ODBC SQL State: 42000)
Error 945: Database "Database Name" cannot be opened
because some of the files could not be activated.
Can anybody help me here?
My phone number is (714)513-3038...my name is Dorsey
Richardson..
e-mail: oldmoney@.geologistics.com
Thanks in advance..
DorseyDorsey,
There is a BOL topic on error 945. On the net you can find it at:
http://tinyurl.com/4wvmv
This has 4 cases that might be the cause and actions for each.
Russell Fields
"Dorsey Richardson" <anonymous@.discussions.microsoft.com> wrote in message
news:027b01c48ba8$4c2c3a30$a401280a@.phx.gbl...
> I'm getting this error message all of a sudden:
> MS SQL-DMO (ODBC SQL State: 42000)
> Error 945: Database "Database Name" cannot be opened
> because some of the files could not be activated.
> Can anybody help me here?
> My phone number is (714)513-3038...my name is Dorsey
> Richardson..
> e-mail: oldmoney@.geologistics.com
> Thanks in advance..
> Dorsey

Thursday, March 22, 2012

Error 8114 Date data

I am trying to pull over data in for a specified date from an ODBC connected
AS/400 table, and I get the following error.
Server: Msg 8114, Level 16, State 8, Line 1
Error converting data type DBTYPE_DBTIMESTAMP to datetime.
Here's an example of what the field looks like in the AS/400 table:
1999-08-24 00:00:00.000
I thought that I could just as "where date = '2005-07-01 00:00:00.00'" but
it doesn't work.
Any thoughts'
Thanks in advance.This could be the limitation of the provider you use. Try a different or
newer provider.
Adrian
"aschossler" <aschossler@.discussions.microsoft.com> wrote in message
news:6C6CD9AF-F37E-459E-9A42-64CE221D2E94@.microsoft.com...
>I am trying to pull over data in for a specified date from an ODBC
>connected
> AS/400 table, and I get the following error.
> Server: Msg 8114, Level 16, State 8, Line 1
> Error converting data type DBTYPE_DBTIMESTAMP to datetime.
> Here's an example of what the field looks like in the AS/400 table:
> 1999-08-24 00:00:00.000
> I thought that I could just as "where date = '2005-07-01 00:00:00.00'"
> but
> it doesn't work.
> Any thoughts'
> Thanks in advance.sql

Error 8114 Date data

I am trying to pull over data in for a specified date from an ODBC connected
AS/400 table, and I get the following error.
Server: Msg 8114, Level 16, State 8, Line 1
Error converting data type DBTYPE_DBTIMESTAMP to datetime.
Here's an example of what the field looks like in the AS/400 table:
1999-08-24 00:00:00.000
I thought that I could just as "where date = '2005-07-01 00:00:00.00'" but
it doesn't work.
Any thoughts?
Thanks in advance.
This could be the limitation of the provider you use. Try a different or
newer provider.
Adrian
"aschossler" <aschossler@.discussions.microsoft.com> wrote in message
news:6C6CD9AF-F37E-459E-9A42-64CE221D2E94@.microsoft.com...
>I am trying to pull over data in for a specified date from an ODBC
>connected
> AS/400 table, and I get the following error.
> Server: Msg 8114, Level 16, State 8, Line 1
> Error converting data type DBTYPE_DBTIMESTAMP to datetime.
> Here's an example of what the field looks like in the AS/400 table:
> 1999-08-24 00:00:00.000
> I thought that I could just as "where date = '2005-07-01 00:00:00.00'"
> but
> it doesn't work.
> Any thoughts?
> Thanks in advance.

Error 8114 Date data

I am trying to pull over data in for a specified date from an ODBC connected
AS/400 table, and I get the following error.
Server: Msg 8114, Level 16, State 8, Line 1
Error converting data type DBTYPE_DBTIMESTAMP to datetime.
Here's an example of what the field looks like in the AS/400 table:
1999-08-24 00:00:00.000
I thought that I could just as "where date = '2005-07-01 00:00:00.00'" but
it doesn't work.
Any thoughts'
Thanks in advance.This could be the limitation of the provider you use. Try a different or
newer provider.
Adrian
"aschossler" <aschossler@.discussions.microsoft.com> wrote in message
news:6C6CD9AF-F37E-459E-9A42-64CE221D2E94@.microsoft.com...
>I am trying to pull over data in for a specified date from an ODBC
>connected
> AS/400 table, and I get the following error.
> Server: Msg 8114, Level 16, State 8, Line 1
> Error converting data type DBTYPE_DBTIMESTAMP to datetime.
> Here's an example of what the field looks like in the AS/400 table:
> 1999-08-24 00:00:00.000
> I thought that I could just as "where date = '2005-07-01 00:00:00.00'"
> but
> it doesn't work.
> Any thoughts'
> Thanks in advance.

Wednesday, March 21, 2012

error '80004005' while accessing the ASP pages

hi,
I am having while accessing the asp pages in our the problem is
"Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][Named Pipes]Access denied.
/pressreleases/pressroom.asp, line 90 "
If i restart the system then i am able to connect the database and working
well.. but afterdays again i am getting same error.. so please help me in
this. Thanks in advance
rajavelWhy are you using named pipes? See http://www.aspfaq.com/2126 for optimal
connection strings...
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Rajavelu Dhakshinamurthy" <rajavelu_d@.dev.visualsoft-tech.com> wrote in
message news:#xySVGH7DHA.2404@.TK2MSFTNGP12.phx.gbl...
> hi,
> I am having while accessing the asp pages in our the problem is
> "Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Access denied.
> /pressreleases/pressroom.asp, line 90 "
>
> If i restart the system then i am able to connect the database and working
> well.. but afterdays again i am getting same error.. so please help me in
> this. Thanks in advance
> rajavel
>
>|||Either you have your database open while you are executing an asp page which
either reads or writes from a datagase or,
You don't have the permission to read/write your database
Click on My Computer icon on your desktop, keep clicking until you find the
folder where your database is. Right click on the database and select
properties and make sure the correct permissions are selected.
regards,
harsh.
"Rajavelu Dhakshinamurthy" <rajavelu_d@.dev.visualsoft-tech.com> wrote in
message news:#xySVGH7DHA.2404@.TK2MSFTNGP12.phx.gbl...
> hi,
> I am having while accessing the asp pages in our the problem is
> "Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Access denied.
> /pressreleases/pressroom.asp, line 90 "
>
> If i restart the system then i am able to connect the database and working
> well.. but afterdays again i am getting same error.. so please help me in
> this. Thanks in advance
> rajavel
>
>|||In article <uukjTUH7DHA.2760@.TK2MSFTNGP09.phx.gbl>, "harsh" <harshalmistry@.hotmail.com> wrote:
>Either you have your database open while you are executing an asp page which
>either reads or writes from a datagase or,
>You don't have the permission to read/write your database
>Click on My Computer icon on your desktop, keep clicking until you find the
>folder where your database is. Right click on the database and select
>properties and make sure the correct permissions are selected.
>regards,
>harsh.
Huh?
I'm afraid you didn't catch the fact that this is a SQL Server DB.
SQL Server doesn't work like that.
What exactly is the SQL statement that is bombing out doing?
Have you tried running profiler when this occurs?|||Check this general guide how to troubleshoot the 80004005 error as well:
http://support.microsoft.com/default.aspx?scid=kb;en-us;306518.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Rajavelu Dhakshinamurthy" <rajavelu_d@.dev.visualsoft-tech.com> wrote in
message news:#xySVGH7DHA.2404@.TK2MSFTNGP12.phx.gbl...
> hi,
> I am having while accessing the asp pages in our the problem is
> "Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Access denied.
> /pressreleases/pressroom.asp, line 90 "
>
> If i restart the system then i am able to connect the database and working
> well.. but afterdays again i am getting same error.. so please help me in
> this. Thanks in advance
> rajavel
>
>

error '80004005' while accessing the ASP pages

hi,
I am having while accessing the asp pages in our the problem is
"Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][Named Pipes]Access denied.
/pressreleases/pressroom.asp, line 90 "
If i restart the system then i am able to connect the database and working
well.. but afterdays again i am getting same error.. so please help me in
this. Thanks in advance
rajavelWhy are you using named pipes? See http://www.aspfaq.com/2126 for optimal
connection strings...
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Rajavelu Dhakshinamurthy" <rajavelu_d@.dev.visualsoft-tech.com> wrote in
message news:#xySVGH7DHA.2404@.TK2MSFTNGP12.phx.gbl...
> hi,
> I am having while accessing the asp pages in our the problem is
> "Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Access denied.
> /pressreleases/pressroom.asp, line 90 "
>
> If i restart the system then i am able to connect the database and working
> well.. but afterdays again i am getting same error.. so please help me in
> this. Thanks in advance
> rajavel
>
>|||Either you have your database open while you are executing an asp page which
either reads or writes from a datagase or,
You don't have the permission to read/write your database
Click on My Computer icon on your desktop, keep clicking until you find the
folder where your database is. Right click on the database and select
properties and make sure the correct permissions are selected.
regards,
harsh.
"Rajavelu Dhakshinamurthy" <rajavelu_d@.dev.visualsoft-tech.com> wrote in
message news:#xySVGH7DHA.2404@.TK2MSFTNGP12.phx.gbl...
> hi,
> I am having while accessing the asp pages in our the problem is
> "Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Access denied.
> /pressreleases/pressroom.asp, line 90 "
>
> If i restart the system then i am able to connect the database and working
> well.. but afterdays again i am getting same error.. so please help me in
> this. Thanks in advance
> rajavel
>
>|||In article <uukjTUH7DHA.2760@.TK2MSFTNGP09.phx.gbl>, "harsh" <harshalmistry@.hotmail.com>
wrote:
>Either you have your database open while you are executing an asp page whic
h
>either reads or writes from a datagase or,
>You don't have the permission to read/write your database
>Click on My Computer icon on your desktop, keep clicking until you find the
>folder where your database is. Right click on the database and select
>properties and make sure the correct permissions are selected.
>regards,
>harsh.
Huh?
I'm afraid you didn't catch the fact that this is a SQL Server DB.
SQL Server doesn't work like that.
What exactly is the SQL statement that is bombing out doing?
Have you tried running profiler when this occurs?|||Check this general guide how to troubleshoot the 80004005 error as well:
http://support.microsoft.com/defaul...b;en-us;306518.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Rajavelu Dhakshinamurthy" <rajavelu_d@.dev.visualsoft-tech.com> wrote in
message news:#xySVGH7DHA.2404@.TK2MSFTNGP12.phx.gbl...
> hi,
> I am having while accessing the asp pages in our the problem is
> "Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Access denied.
> /pressreleases/pressroom.asp, line 90 "
>
> If i restart the system then i am able to connect the database and working
> well.. but afterdays again i am getting same error.. so please help me in
> this. Thanks in advance
> rajavel
>
>

Error 7405 with a linked server and stored procedure

I'm trying to create a stored procecudure using the openquery command to an linked ODBC server.

Everytime I try to save the procedure I get "error 7405: Heterogenous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection."

I've checked everywhere and set these options on, yet it still doesn't work.

Any ideas?

It's a simple procedure and when I type the sql into query analyzer it works.

HELP?

Here is the procedure.
===============================
CREATE PROCEDURE [dbo].[stpDKLink] AS

select * from openquery(dk, 'select * from pub.invoice')

GO
===============================Yes, SQLServer error message is a bit misleading in this case. Try this out:

SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO

CREATE PROCEDURE [dbo].[stpDKLink] AS
select * from openquery(dk, 'select * from pub.invoice')
GO

SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GOsql

Friday, March 9, 2012

Error 5041. MODIFY FILE failed. File '%.*ls' does not exist.

I am trying to set the file growth of a database file to
10% and I get the message:
Microsoft SQL-MDO (ODBC SQL-STATE 42000)
Error 5041. MODIFY FILE failed. File '%.*ls' does not
exist.
All I know is that this system error message is of
severity 16.
DO you have any ideas?
See my other reply. Please don't re-post...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kostas Kourtides" <KostasKourtides@.yahoo.com> wrote in message
news:275101c45d0a$f7b4bd90$3501280a@.phx.gbl...
> I am trying to set the file growth of a database file to
> 10% and I get the message:
> Microsoft SQL-MDO (ODBC SQL-STATE 42000)
> Error 5041. MODIFY FILE failed. File '%.*ls' does not
> exist.
> All I know is that this system error message is of
> severity 16.
> DO you have any ideas?

Error 5041. MODIFY FILE failed. File '%.*ls' does not exist.

I am trying to set the file growth of a database file to
10% and I get the message:
Microsoft SQL-MDO (ODBC SQL-STATE 42000)
Error 5041. MODIFY FILE failed. File '%.*ls' does not
exist.
All I know is that this system error message is of
severity 16.
DO you have any ideas?See my other reply. Please don't re-post...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kostas Kourtides" <KostasKourtides@.yahoo.com> wrote in message
news:275101c45d0a$f7b4bd90$3501280a@.phx.gbl...
> I am trying to set the file growth of a database file to
> 10% and I get the message:
> Microsoft SQL-MDO (ODBC SQL-STATE 42000)
> Error 5041. MODIFY FILE failed. File '%.*ls' does not
> exist.
> All I know is that this system error message is of
> severity 16.
> DO you have any ideas?

Error 5041. MODIFY FILE failed. File '%.*ls' does not exist.

I am trying to set the file growth of a database file to
10% and I get the message:
Microsoft SQL-MDO (ODBC SQL-STATE 42000)
Error 5041. MODIFY FILE failed. File '%.*ls' does not
exist.
All I know is that this system error message is of
severity 16.
DO you have any ideas?See my other reply. Please don't re-post...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kostas Kourtides" <KostasKourtides@.yahoo.com> wrote in message
news:275101c45d0a$f7b4bd90$3501280a@.phx.gbl...
> I am trying to set the file growth of a database file to
> 10% and I get the message:
> Microsoft SQL-MDO (ODBC SQL-STATE 42000)
> Error 5041. MODIFY FILE failed. File '%.*ls' does not
> exist.
> All I know is that this system error message is of
> severity 16.
> DO you have any ideas?

Wednesday, March 7, 2012

Error 3624 Location: fakerowset.cpp:251

Hello,
I have the following error when I want to access the design
mode in Entreprise Manager of some tables :
Microsoft SQL-DMO (ODBC SQLState: HY000)
Error: 3624
Expression: accCategory == ACC_CATEGORY_NORMAL || accCatgegory ==
ACC_CATEGORY_BIT
SOPID: 52
Process ID : 2876
I'm running SQL server 2000 with SP3a.
Thanks for your help
You seem to be running into some sort of ASSERT is what I think. Please run
checkdb on your database, and check on the SQL error logs for any stack
dumps. Please paste the input buffer and short stack dump in this thread
and we can analyse.
Also if corruption is the cause, you also want to get your hw vendors
thoroughly involved and have them check your disk, controllers, etc.
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 3624 Location: fakerowset.cpp:251

Hello,
I have the following error when I want to access the design
mode in Entreprise Manager of some tables :
Microsoft SQL-DMO (ODBC SQLState: HY000)
Error: 3624
Expression: accCategory == ACC_CATEGORY_NORMAL || accCatgegory == ACC_CATEGORY_BIT
SOPID: 52
Process ID : 2876
I'm running SQL server 2000 with SP3a.
Thanks for your helpYou seem to be running into some sort of ASSERT is what I think. Please run
checkdb on your database, and check on the SQL error logs for any stack
dumps. Please paste the input buffer and short stack dump in this thread
and we can analyse.
Also if corruption is the cause, you also want to get your hw vendors
thoroughly involved and have them check your disk, controllers, etc.
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 3624 - SQL-DMO(ODBC SQLState:HY000)

My ProjectServer database suddenly became (suspect), the log file increased
like balloon 49.9GB, I don't know exactly what was the size before. The mdf
file is about 640MB. To get the situation worst, the backup wasn't good,
tried to copy the file to a different folder, so a detached the DB to copy
both of them.
Later I tried to attach the DB back and it gave me this error message.
(SQL2000 SP3)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:321
Expression: m_len !=0
SPID: 54
Process ID: 1832"
================================
(After applying SP4)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:359
Expression: m_len !=0
SPID: 54
Process ID: 1896"
Where do I start, is there any repai utility to fix this problem?
I am not a database or SQL expert, any help will be very appreciated.
I can't attach the database back anymore.
Johnny
Hi Johnny
You have probably run out of space where the log file is located. You can
check for open transactions in the database using DBCC OPENTRAN, but there
should not be any as you have detached the database. Use BACKUP LOG to free
up the log file and DBCC SHRINKFILE to shrink it. You may want to see
http://msdn.microsoft.com/library/de...r_da2_1uzr.asp
Once a reasonable size you should change the growth amount to be a fixed
value and not a percentage.
To change the database so it is not suspect see
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
You should also implement a backup schedule or maintenance plan that will
backup the database and also backup the logs.
John
"Johnny" wrote:

> My ProjectServer database suddenly became (suspect), the log file increased
> like balloon 49.9GB, I don't know exactly what was the size before. The mdf
> file is about 640MB. To get the situation worst, the backup wasn't good,
> tried to copy the file to a different folder, so a detached the DB to copy
> both of them.
> Later I tried to attach the DB back and it gave me this error message.
> (SQL2000 SP3)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:321
> Expression: m_len !=0
> SPID: 54
> Process ID: 1832"
> ================================
> (After applying SP4)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:359
> Expression: m_len !=0
> SPID: 54
> Process ID: 1896"
> Where do I start, is there any repai utility to fix this problem?
> I am not a database or SQL expert, any help will be very appreciated.
> I can't attach the database back anymore.
> Johnny
>
>

Error 3624 - SQL-DMO(ODBC SQLState:HY000)

My ProjectServer database suddenly became (suspect), the log file increased
like balloon 49.9GB, I don't know exactly what was the size before. The mdf
file is about 640MB. To get the situation worst, the backup wasn't good,
tried to copy the file to a different folder, so a detached the DB to copy
both of them.
Later I tried to attach the DB back and it gave me this error message.
(SQL2000 SP3)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:321
Expression: m_len !=0
SPID: 54
Process ID: 1832"
================================
(After applying SP4)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:359
Expression: m_len !=0
SPID: 54
Process ID: 1896"
Where do I start, is there any repai utility to fix this problem?
I am not a database or SQL expert, any help will be very appreciated.
I can't attach the database back anymore.
JohnnyHi Johnny
You have probably run out of space where the log file is located. You can
check for open transactions in the database using DBCC OPENTRAN, but there
should not be any as you have detached the database. Use BACKUP LOG to free
up the log file and DBCC SHRINKFILE to shrink it. You may want to see
http://msdn.microsoft.com/library/d...r />
_1uzr.asp
Once a reasonable size you should change the growth amount to be a fixed
value and not a percentage.
To change the database so it is not suspect see
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
You should also implement a backup schedule or maintenance plan that will
backup the database and also backup the logs.
John
"Johnny" wrote:

> My ProjectServer database suddenly became (suspect), the log file increase
d
> like balloon 49.9GB, I don't know exactly what was the size before. The md
f
> file is about 640MB. To get the situation worst, the backup wasn't good,
> tried to copy the file to a different folder, so a detached the DB to copy
> both of them.
> Later I tried to attach the DB back and it gave me this error message.
> (SQL2000 SP3)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:321
> Expression: m_len !=0
> SPID: 54
> Process ID: 1832"
> ================================
> (After applying SP4)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:359
> Expression: m_len !=0
> SPID: 54
> Process ID: 1896"
> Where do I start, is there any repai utility to fix this problem?
> I am not a database or SQL expert, any help will be very appreciated.
> I can't attach the database back anymore.
> Johnny
>
>

Error 3624 - SQL-DMO(ODBC SQLState:HY000)

My ProjectServer database suddenly became (suspect), the log file increased
like balloon 49.9GB, I don't know exactly what was the size before. The mdf
file is about 640MB. To get the situation worst, the backup wasn't good,
tried to copy the file to a different folder, so a detached the DB to copy
both of them.
Later I tried to attach the DB back and it gave me this error message.
(SQL2000 SP3)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:321
Expression: m_len !=0
SPID: 54
Process ID: 1832"
================================ (After applying SP4)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:359
Expression: m_len !=0
SPID: 54
Process ID: 1896"
Where do I start, is there any repai utility to fix this problem?
I am not a database or SQL expert, any help will be very appreciated.
I can't attach the database back anymore.
JohnnyHi Johnny
You have probably run out of space where the log file is located. You can
check for open transactions in the database using DBCC OPENTRAN, but there
should not be any as you have detached the database. Use BACKUP LOG to free
up the log file and DBCC SHRINKFILE to shrink it. You may want to see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_1uzr.asp
Once a reasonable size you should change the growth amount to be a fixed
value and not a percentage.
To change the database so it is not suspect see
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
You should also implement a backup schedule or maintenance plan that will
backup the database and also backup the logs.
John
"Johnny" wrote:
> My ProjectServer database suddenly became (suspect), the log file increased
> like balloon 49.9GB, I don't know exactly what was the size before. The mdf
> file is about 640MB. To get the situation worst, the backup wasn't good,
> tried to copy the file to a different folder, so a detached the DB to copy
> both of them.
> Later I tried to attach the DB back and it gave me this error message.
> (SQL2000 SP3)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:321
> Expression: m_len !=0
> SPID: 54
> Process ID: 1832"
> ================================> (After applying SP4)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:359
> Expression: m_len !=0
> SPID: 54
> Process ID: 1896"
> Where do I start, is there any repai utility to fix this problem?
> I am not a database or SQL expert, any help will be very appreciated.
> I can't attach the database back anymore.
> Johnny
>
>

Sunday, February 26, 2012

Error 3624

All,
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
...Mukund.R.L.Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
..Mukund.R.L.
>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
>> All,
>> I have the below problem while attaching the database,
can
>> any one assist.
>> Thanks in advance.
>> --Error Details
>> Microsoft SQL-DMO(ODBC SQLState-HY000)
>> Error 3624
>> Location : recovery.C:2014
>> Expression: Curr-->log_length >0
>> SPID :53
>> ProcessorId: 1064
>> below is the last lines from Error Log
>> 2004-06-01 10:27:14.45 spid53 Stack Signature for
the
>> dump is 0x9A8706F6
>> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
>> File: <recovery.c>, line=2014
>> Failed Assertion = 'curr->log_length > 0'.
>> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
>> 20, State: 1.
>> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
>> 23, State: 7
>> 2004-06-01 10:27:15.93 spid53 An error occurred
while
>> processing the log for database 'UPSSISGR'..
>>
>> ...Mukund.R.L.
>>
>>
>.
>

Error 3624

All,
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
....Mukund.R.L.
Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>
|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
...Mukund.R.L.

>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from[vbcol=seagreen]
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
can[vbcol=seagreen]
the[vbcol=seagreen]
while
>.
>

Error 3624

All,
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
...Mukund.R.L.Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
..Mukund.R.L.

>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
can[vbcol=seagreen]
the[vbcol=seagreen]
while[vbcol=seagreen]
>.
>