Extracting Sql: runnning

Showing posts with label runnning. Show all posts

Thursday, March 29, 2012

Failed to set proper user name ('domain\username') for the connection

Im runnning a Trace from Production against a Development box and getting
this error message:
Failed to set proper user name ('domain\username') for the connection
.. I have removed the db_id from the Trace table. Also, all the Logins/ Users
are set to the proper default DB. So Im really confused as to why I would be
getting this? Any ideas?
TIA, ChrisR
Hi
Have you got the same db_id for the database(s) on the production and
development servers? You may want to restore master! Alternatively try to
save the trace as a SQL File and then run that, you should not get this
problem and it will be easier to debug any problems that you do get.
John
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%23qqMGq7CFHA.4052@.TK2MSFTNGP15.phx.gbl...
> Im runnning a Trace from Production against a Development box and getting
> this error message:
> Failed to set proper user name ('domain\username') for the connection
> . I have removed the db_id from the Trace table. Also, all the Logins/
> Users
> are set to the proper default DB. So Im really confused as to why I would
> be
> getting this? Any ideas?
>
> TIA, ChrisR
>
|||John if Im not mistaken, the problem should have been fixed by simply
removing the db_id... therefore not requiring the restore of Master.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:e6jSfhHDFHA.2180@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Hi
> Have you got the same db_id for the database(s) on the production and
> development servers? You may want to restore master! Alternatively try to
> save the trace as a SQL File and then run that, you should not get this
> problem and it will be easier to debug any problems that you do get.
> John
> "ChrisR" <ChrisR@.noEmail.com> wrote in message
> news:%23qqMGq7CFHA.4052@.TK2MSFTNGP15.phx.gbl...
getting[vbcol=seagreen]
would
>
|||Hi
That is not what I understand! Profiling it may help.
John
ChrisR wrote:[vbcol=seagreen]
> John if Im not mistaken, the problem should have been fixed by simply
> removing the db_id... therefore not requiring the restore of Master.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:e6jSfhHDFHA.2180@.TK2MSFTNGP10.phx.gbl...
and[vbcol=seagreen]
try to[vbcol=seagreen]
this[vbcol=seagreen]
get.[vbcol=seagreen]
> getting
connection[vbcol=seagreen]
Logins/[vbcol=seagreen]
I[vbcol=seagreen]
> would
|||It generally does work if you remove database ids from the
trace. Double check to make sure all the users captured in
the trace have a default database of the target database.
The commands should then be executed in the default database
so the database id isn't an issue.
-Sue
On 8 Feb 2005 00:01:01 -0800, "John Bell"
<jbellnewsposts@.hotmail.com> wrote:
[vbcol=seagreen]
>Hi
>That is not what I understand! Profiling it may help.
>John
>ChrisR wrote:
>and
>try to
>this
>get.
>connection
>Logins/
>I
|||Hi
Another through, although you say there default databases are set for
all users, check that there are no orphaned users.
John
John Bell wrote:[vbcol=seagreen]
> Hi
> That is not what I understand! Profiling it may help.
> John
> ChrisR wrote:
simply[vbcol=seagreen]
Master.[vbcol=seagreen]
> and
Alternatively[vbcol=seagreen]
> try to
get[vbcol=seagreen]
> this
> get.
and[vbcol=seagreen]
> connection
> Logins/
why[vbcol=seagreen]
> I
sql

Failed to set proper user name ('domain\username') for the connection

Im runnning a Trace from Production against a Development box and getting
this error message:
Failed to set proper user name ('domain\username') for the connection
. I have removed the db_id from the Trace table. Also, all the Logins/ Users
are set to the proper default DB. So Im really confused as to why I would be
getting this? Any ideas?
TIA, ChrisRHi
Have you got the same db_id for the database(s) on the production and
development servers? You may want to restore master! Alternatively try to
save the trace as a SQL File and then run that, you should not get this
problem and it will be easier to debug any problems that you do get.
John
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%23qqMGq7CFHA.4052@.TK2MSFTNGP15.phx.gbl...
> Im runnning a Trace from Production against a Development box and getting
> this error message:
> Failed to set proper user name ('domain\username') for the connection
> . I have removed the db_id from the Trace table. Also, all the Logins/
> Users
> are set to the proper default DB. So Im really confused as to why I would
> be
> getting this? Any ideas?
>
> TIA, ChrisR
>|||John if Im not mistaken, the problem should have been fixed by simply
removing the db_id... therefore not requiring the restore of Master.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:e6jSfhHDFHA.2180@.TK2MSFTNGP10.phx.gbl...
> Hi
> Have you got the same db_id for the database(s) on the production and
> development servers? You may want to restore master! Alternatively try to
> save the trace as a SQL File and then run that, you should not get this
> problem and it will be easier to debug any problems that you do get.
> John
> "ChrisR" <ChrisR@.noEmail.com> wrote in message
> news:%23qqMGq7CFHA.4052@.TK2MSFTNGP15.phx.gbl...
> > Im runnning a Trace from Production against a Development box and
getting
> > this error message:
> >
> > Failed to set proper user name ('domain\username') for the connection
> >
> > . I have removed the db_id from the Trace table. Also, all the Logins/
> > Users
> > are set to the proper default DB. So Im really confused as to why I
would
> > be
> > getting this? Any ideas?
> >
> >
> >
> > TIA, ChrisR
> >
> >
>|||Hi
That is not what I understand! Profiling it may help.
John
ChrisR wrote:
> John if Im not mistaken, the problem should have been fixed by simply
> removing the db_id... therefore not requiring the restore of Master.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:e6jSfhHDFHA.2180@.TK2MSFTNGP10.phx.gbl...
> > Hi
> >
> > Have you got the same db_id for the database(s) on the production
and
> > development servers? You may want to restore master! Alternatively
try to
> > save the trace as a SQL File and then run that, you should not get
this
> > problem and it will be easier to debug any problems that you do
get.
> >
> > John
> >
> > "ChrisR" <ChrisR@.noEmail.com> wrote in message
> > news:%23qqMGq7CFHA.4052@.TK2MSFTNGP15.phx.gbl...
> > > Im runnning a Trace from Production against a Development box and
> getting
> > > this error message:
> > >
> > > Failed to set proper user name ('domain\username') for the
connection
> > >
> > > . I have removed the db_id from the Trace table. Also, all the
Logins/
> > > Users
> > > are set to the proper default DB. So Im really confused as to why
I
> would
> > > be
> > > getting this? Any ideas?
> > >
> > >
> > >
> > > TIA, ChrisR
> > >
> > >
> >
> >|||It generally does work if you remove database ids from the
trace. Double check to make sure all the users captured in
the trace have a default database of the target database.
The commands should then be executed in the default database
so the database id isn't an issue.
-Sue
On 8 Feb 2005 00:01:01 -0800, "John Bell"
<jbellnewsposts@.hotmail.com> wrote:
>Hi
>That is not what I understand! Profiling it may help.
>John
>ChrisR wrote:
>> John if Im not mistaken, the problem should have been fixed by simply
>> removing the db_id... therefore not requiring the restore of Master.
>>
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:e6jSfhHDFHA.2180@.TK2MSFTNGP10.phx.gbl...
>> > Hi
>> >
>> > Have you got the same db_id for the database(s) on the production
>and
>> > development servers? You may want to restore master! Alternatively
>try to
>> > save the trace as a SQL File and then run that, you should not get
>this
>> > problem and it will be easier to debug any problems that you do
>get.
>> >
>> > John
>> >
>> > "ChrisR" <ChrisR@.noEmail.com> wrote in message
>> > news:%23qqMGq7CFHA.4052@.TK2MSFTNGP15.phx.gbl...
>> > > Im runnning a Trace from Production against a Development box and
>> getting
>> > > this error message:
>> > >
>> > > Failed to set proper user name ('domain\username') for the
>connection
>> > >
>> > > . I have removed the db_id from the Trace table. Also, all the
>Logins/
>> > > Users
>> > > are set to the proper default DB. So Im really confused as to why
>I
>> would
>> > > be
>> > > getting this? Any ideas?
>> > >
>> > >
>> > >
>> > > TIA, ChrisR
>> > >
>> > >
>> >
>> >|||Hi
Another through, although you say there default databases are set for
all users, check that there are no orphaned users.
John
John Bell wrote:
> Hi
> That is not what I understand! Profiling it may help.
> John
> ChrisR wrote:
> > John if Im not mistaken, the problem should have been fixed by
simply
> > removing the db_id... therefore not requiring the restore of
Master.
> >
> >
> > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > news:e6jSfhHDFHA.2180@.TK2MSFTNGP10.phx.gbl...
> > > Hi
> > >
> > > Have you got the same db_id for the database(s) on the production
> and
> > > development servers? You may want to restore master!
Alternatively
> try to
> > > save the trace as a SQL File and then run that, you should not
get
> this
> > > problem and it will be easier to debug any problems that you do
> get.
> > >
> > > John
> > >
> > > "ChrisR" <ChrisR@.noEmail.com> wrote in message
> > > news:%23qqMGq7CFHA.4052@.TK2MSFTNGP15.phx.gbl...
> > > > Im runnning a Trace from Production against a Development box
and
> > getting
> > > > this error message:
> > > >
> > > > Failed to set proper user name ('domain\username') for the
> connection
> > > >
> > > > . I have removed the db_id from the Trace table. Also, all the
> Logins/
> > > > Users
> > > > are set to the proper default DB. So Im really confused as to
why
> I
> > would
> > > > be
> > > > getting this? Any ideas?
> > > >
> > > >
> > > >
> > > > TIA, ChrisR
> > > >
> > > >
> > >
> > >

Failed to set proper user name ('domain\username') for the connection

Wednesday, March 21, 2012

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 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.
> 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 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 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 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.
> >
> > Bobson|||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:
> 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 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 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.
> > >
> > > Bobson|||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:
> 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:
> > 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 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 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.
> > > >
> > > > Bobson|||Hi Bobson,
I am glad you fixed the problem.
Happy holidays!
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" 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:
> >
> > 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:
> >
> > > 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 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 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.
> > > > >
> > > > > Bobson

Thursday, March 29, 2012

Failed to set proper user name ('domain\username') for the connection

Failed to set proper user name ('domain\username') for the connection

Failed to set proper user name ('domain\username') for the connection

Wednesday, March 21, 2012

Failed on runnning maintenance backup plan but....

Failed on runnning maintenance backup plan but....

Failed on runnning maintenance backup plan but....

Extracting Sql

Blog Archive

About Me