Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

CoCreateInstanceEx fails after installing XP Service Pack 2

CoCreateInstanceEx fails after installing XP Service Pack 2

CoCreateInstanceEx fails after installing XP Service Pack 2

We have a VB app that calls VB COM+ components on a separate server machine (classic 3 Tier).  To instantiate a COM+ object on the server, we invoke a function that calls CoCreateInstanceEx:

Dim ServerInfo as COSERVERINFO
'Decide on the appropriate context value.
    If RunOnComputer = "" Then
       Context = CLSCTX_SERVER
    End If

    'Setup the COSERVERINFO structure.
    ServerInfo.pwszName = StrPtr(RunOnComputer)
    ServerInfo.pAuthInfo = VarPtr(objAuthInfo)

    ' Create an instance of the object
    lRet = CoCreateInstanceEx(typGUID, CLng(0), Context, ServerInfo, CLng(1), typMQI)

Normally the ServerInfo.pwszName (denoting the server's hostname/IP) was equal to an empty string.  The intention was that the name would be obtained through the COM+ proxy's RemoteServerName named value.  

After installing XP Service Pack 2, the call to CoCreateInstanceEx fails, with the Error Handler throwing Error 70 - Permission Denied.  We can get around this by explictly setting COSERVERINFO.pwszName to the server's IP address or hostname.

What it is the rationale for this error being thrown?  Are there any non-code changes (ie. modifying DCOM ACLs, Transaction Config. security, etc.) that would allow the call to CoCreateInstanceEx with the empty string assigned to ServerInfo.pwszName?

RE: CoCreateInstanceEx fails after installing XP Service Pack 2


You should run dcomcnfg because the SP2 installation disables COM+.



Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close