RE: Msg 15404: Could not obtain information about user

Hi Jason,
I understand that when you changed your DAEMON startup account from
MYDOMAIN\BuildAdmin to MYDOMAIN\BuildUser, you encountered the error when
loading the script in which a trigger created "WITH EXECUTE AS OWNER".
If I have misunderstood, please let me know.

To track the cause of this issue, I need to collect more information from
you:
1. Is MYDOMAIN\BuildUser a singleton user account or a user group?
OWNER must map to a singleton account and cannot be a role or group.

2. What is the type of the trigger MyTable_MyUpdate, a DML trigger or DDL
trigger? and What does it do?
OWNER cannot be specified for DDL triggers.

3. The SQL error logs which are located in the folder
%ProgramFiles%\Microsoft SQL Server\MSSQL(.x)\MSSQL\LOG by default.
You may mail me (changliw_at_microsoft_dot_com) the logs for further
research.

From the error code, it indicated an "Access denied" error. I also
recommend that you run Process Monitor to monitor your daemon and SQL
Server process to see if there are any clues regarding file access. Of
course, you can also mail the trace logs to me. You can download Process
Monitor at this link:
Process Monitor v1.33
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx?PHPSESSID=d926
bdd849b5aab10f7263dd7f5904f2

Look forward to your response. If you have any other questions or concerns,
please feel free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================


.

Relevant Pages

  • RE: SMTP Authentication flag
    ... To locate what the registry key should be for your account, ... can iterate the registry keys to check if the value of the subkey "Account ... Microsoft Online Community Support ... or a Microsoft Support Engineer within 1 business day is acceptable. ...
    (microsoft.public.win32.programmer.messaging)
  • Re: How to connect to SQL from machine without domain
    ... I think SQL authentication is the most proper solution for such an environment. ... A work around is to create a "mirror" account on both database server. ... The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. ...
    (microsoft.public.scripting.vbscript)
  • Re: Triggers - Inserted and Deleted Tables
    ... If you have a DML statement that affects more than one row, ... trigger will fail - I mean, you won't get an error, but the trigger action ... SELECT @OldBalance = Balance ... and I update an account holders checking and savings account. ...
    (microsoft.public.sqlserver.programming)
  • Re: call to xp_cmdshell from trigger problem
    ... I'll look this over maybe there is something we missed in the vbs script ... >> account. ... >> script that is called by the trigger the client get nothing. ...
    (microsoft.public.sqlserver.server)
  • Re: Trigger on D3 DM tables
    ... The logic for the trigger is no biggie but my wonder is 'where' it ... RUNTIME-ERRORS which might cause me a 'circular logic' error). ... Account ACCT has a table ACCOUNTS which has a trigger on data portion. ... Account USER has a qpointer to ACCOUNTS. ...
    (comp.databases.pick)