Failed on runnning maintenance backup plan but....

Hi,
Thank you for your help in advance...
We are running SQL 2K Sp3. For some reason, the maintenance plan (both
backup and optimize) stopped running. I made sure the SQL agent running but
the job never ran successfully. It ran fine before for long time but just
stopped running recently.
I did some tests by setting a maintenanace plan just running a simple db
backup (no transaction log included). it still failed. The error in the
report is " ODBC SQLState:42000" Error 4064...... Cannot open user default
database. Login failed.
However, I setup some backup jobs to backup both db and transaction log by
NOT using maintenance plan. Those work fine.
Do you know what I should look into to fix the problem?
Hope you can help.
Thank you very much for your help.
BobsonHi Bobson,
That should be very easy to fix. Probably the job is running under a user
that has an incorrect default database. Perhaps the default database was
deleted or the user does not have access to it. Change the default database
for this user.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" wrote:

> Hi,
> Thank you for your help in advance...
> We are running SQL 2K Sp3. For some reason, the maintenance plan (both
> backup and optimize) stopped running. I made sure the SQL agent running bu
t
> the job never ran successfully. It ran fine before for long time but just
> stopped running recently.
> I did some tests by setting a maintenanace plan just running a simple db
> backup (no transaction log included). it still failed. The error in the
> report is " ODBC SQLState:42000" Error 4064...... Cannot open user defaul
t
> database. Login failed.
> However, I setup some backup jobs to backup both db and transaction log by
> NOT using maintenance plan. Those work fine.
> Do you know what I should look into to fix the problem?
> Hope you can help.
> Thank you very much for your help.
> Bobson|||Hi Ben,
Thank you very much for your response. After reading your response, I
checked into that but still has no clue.
sa - is default to "master" db. It has full access to it and other dbs.
lsadmin - is the Domain admin account I logged onto the Windows server. It
has full admin right on the local servers and access right to two dbs, ch an
d
pd.
I tried to run the maintenance jobs on master, ch and pd...but no luck. I
also treid to set up a test maintenance job to backup just the Master db...
but failed as well.
What else should I check ?
Thank you agian for your help.
Bobson
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi Bobson,
> That should be very easy to fix. Probably the job is running under a user
> that has an incorrect default database. Perhaps the default database was
> deleted or the user does not have access to it. Change the default databas
e
> for this user.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Bobson" wrote:
>|||Try this:
Right-click the job that is not working. Select View Job History, Show step
details. See the steps and look for 'Executed as user: x' or 'The Job was
invoked by User x'. Check the account under which the SQL Server Agent is
running. Also, on SQL Server Agent Properties go to the Connection tab and
see the account used under 'SQL Server connection'.
Then verify that these logins have a valid default database.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" wrote:
[vbcol=seagreen]
> Hi Ben,
> Thank you very much for your response. After reading your response, I
> checked into that but still has no clue.
> sa - is default to "master" db. It has full access to it and other dbs.
> lsadmin - is the Domain admin account I logged onto the Windows server. It
> has full admin right on the local servers and access right to two dbs, ch
and
> pd.
> I tried to run the maintenance jobs on master, ch and pd...but no luck. I
> also treid to set up a test maintenance job to backup just the Master db..
.
> but failed as well.
> What else should I check ?
> Thank you agian for your help.
> Bobson
>
>
> "Ben Nevarez" wrote:
>|||Hi Ben,
Good morning. Thank you for your response again!
I just checked it...in the Connection tab. It was pointing to Windows
Authenticaitons...so I change it to use SA account instead. And tried to run
the job again. It works!!
Again, thank you very much for your help. Happy holidays to you and your
family!!
Bobson
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Try this:
> Right-click the job that is not working. Select View Job History, Show ste
p
> details. See the steps and look for 'Executed as user: x' or 'The Job was
> invoked by User x'. Check the account under which the SQL Server Agent is
> running. Also, on SQL Server Agent Properties go to the Connection tab and
> see the account used under 'SQL Server connection'.
> Then verify that these logins have a valid default database.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Bobson" wrote:
>|||Hi Bobson,
I am glad you fixed the problem.
Happy holidays!
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" wrote:
[vbcol=seagreen]
> Hi Ben,
> Good morning. Thank you for your response again!
> I just checked it...in the Connection tab. It was pointing to Windows
> Authenticaitons...so I change it to use SA account instead. And tried to r
un
> the job again. It works!!
> Again, thank you very much for your help. Happy holidays to you and your
> family!!
> Bobson
> "Ben Nevarez" wrote:
>sql