Failed to open database: Cannot open database "dbname" requested by the
login. The login failed.Keep getting Database connection error at
midnight, and then loss of data. Happens 1-2 times per week (but not
every day).As the failure is only once or twice a week I don't believe
the failure is related to the login, also the service is running as
local system, and the database connection is using Integrated Security.
The SQL service is running.has some one come across this issue?
Thanks in advance..
Andzandz
Is it SQL Server 2000?
Can you check your server errorlog and post the errors that show up there?
"andz" <anand411@.gmail.com> wrote in message
news:1153814521.878454.281140@.b28g2000cwb.googlegroups.com...
> Failed to open database: Cannot open database "dbname" requested by the
> login. The login failed.Keep getting Database connection error at
> midnight, and then loss of data. Happens 1-2 times per week (but not
> every day).As the failure is only once or twice a week I don't believe
> the failure is related to the login, also the service is running as
> local system, and the database connection is using Integrated Security.
> The SQL service is running.has some one come across this issue?
> Thanks in advance..
> Andz
>|||Hi Uri...
Herez the server error lod..
Server log extract:
2006-07-25:00:01:07 Bytes served today 8442940
2006-07-25:00:01:07 Date changed to 7/25/2006
2006-07-25:00:01:09 Failed to open database: Cannot open database
"WhosOnV4" requested by the login. The login failed.
2006-07-25:00:01:10 Could not reopen database.
Extract from SQL log:
7/24/2006 11:53:55 PM Successfully logged in and out of SQL Server
vizhost5\sql2005 login=sa
7/25/2006 12:08:55 AM Successfully logged in and out of SQL Server
vizhost5\sql2005 login=sa
7/25/2006 12:23:55 AM Successfully logged in and out of SQL Server
vizhost5\sql2005 login=sa
Database connection string:
Provider=SQLNCLI;Initial Catalog=WhosOnV4;Data
Source=VIZHOST5\SQL2005;Integrated Security=SSPI;
Uri Dimant wrote:[vbcol=seagreen]
> andz
> Is it SQL Server 2000?
> Can you check your server errorlog and post the errors that show up there?
>
> "andz" <anand411@.gmail.com> wrote in message
> news:1153814521.878454.281140@.b28g2000cwb.googlegroups.com...|||andz
Check MDAC versions ,seems that comes from OLEDB provider.
Take a look at this
http://support.microsoft.com/defaul...kb;en-us;Q31454
"andz" <anand411@.gmail.com> wrote in message
news:1153824325.168904.149550@.b28g2000cwb.googlegroups.com...
> Hi Uri...
> Herez the server error lod..
> Server log extract:
> 2006-07-25:00:01:07 Bytes served today 8442940
> 2006-07-25:00:01:07 Date changed to 7/25/2006
> 2006-07-25:00:01:09 Failed to open database: Cannot open database
> "WhosOnV4" requested by the login. The login failed.
> 2006-07-25:00:01:10 Could not reopen database.
> Extract from SQL log:
> 7/24/2006 11:53:55 PM Successfully logged in and out of SQL Server
> vizhost5\sql2005 login=sa
> 7/25/2006 12:08:55 AM Successfully logged in and out of SQL Server
> vizhost5\sql2005 login=sa
> 7/25/2006 12:23:55 AM Successfully logged in and out of SQL Server
> vizhost5\sql2005 login=sa
> Database connection string:
> Provider=SQLNCLI;Initial Catalog=WhosOnV4;Data
> Source=VIZHOST5\SQL2005;Integrated Security=SSPI;
> Uri Dimant wrote:
>|||Thanks a lot for you response...
MDAC version is 2.82.1830.....Application not closed when maintenance
jobs or backup jobs are being done on the database.However, although a
'sleep' has now been configured for the application during the backup
period.
Andz
Uri Dimant wrote:[vbcol=seagreen]
> andz
> Check MDAC versions ,seems that comes from OLEDB provider.
> Take a look at this
> http://support.microsoft.com/defaul...kb;en-us;Q31454
> "andz" <anand411@.gmail.com> wrote in message
> news:1153824325.168904.149550@.b28g2000cwb.googlegroups.com...
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment