Discussion:
WMI error with root\MicrosoftBizTalkServer
(too old to reply)
dfosterh
2008-10-16 01:05:01 UTC
Permalink
Hi there,

Using wbemtest.exe from C:\WINDOWS\system32\wbem, I execute the following
query using 2 different logins with 2 different results:

Connect: root\MicrosoftBizTalkServer
Query: SELECT * FROM MSBTS_GroupSetting

Both logins are domain accounts that belong to the local administrator
group. The local administrator group has full permissions to both the root
and root\MicrosoftBizTalkServer nodes in the WMI Control properties panel.
I've also tried granting the same privileges to the specific account that
fails. One account returns results, the other returns:

Error Info:
Number: 0x80004005
Facility: <Null>
Description: Unspecified error

Additional information:

1. I can run queries against root/CIMV2 from both accounts.
2. The error from a .NET app using ManagementObjectSearcher is "Syntax error
or access violation"

Any insights will be greatly appreciated.
dfosterh
2008-10-16 19:03:02 UTC
Permalink
Found a solution, but disturbed by the connotation.

If I crank up the priveleges of the login to sysadmin on the SQL Server (on
a different physical box) it works. This means, as far as I can deduce, that
the BizTalk WMI resource is impersonating the current user. I thought WMI
only passed tokens.

Can anyone at MS tell me what permissions the login requires on SQL for this
operation? I prefer not to grant the BizTalk service account SQL sysadmin
when I release to production.
Paul Somers[MVP]
2008-11-03 06:50:20 UTC
Permalink
Hi,

You are correct it will impersonate the current user, that user needs to
have access to the BTS admin group, and the SSO admin group. These groups
permissions should have sufficent permissions o nthe BTS databases.

Paul.
Post by dfosterh
Found a solution, but disturbed by the connotation.
If I crank up the priveleges of the login to sysadmin on the SQL Server (on
a different physical box) it works. This means, as far as I can deduce, that
the BizTalk WMI resource is impersonating the current user. I thought WMI
only passed tokens.
Can anyone at MS tell me what permissions the login requires on SQL for this
operation? I prefer not to grant the BizTalk service account SQL sysadmin
when I release to production.
Loading...