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

No comments:

Post a Comment