Are you sure that the error message from other COM objects are the same?
Formerly you posted this result:
<connectionAttempts> <connectionAttempt> <description>Access is denied. </description> <status>0x80070005</status> <saslogin></saslogin> <sasmachinednsname></sasmachinednsname> <sasclassid></sasclassid> <sasprogid>SAS.Workspace.1.0</sasprogid> <threadid>17200</threadid> <name>mylocalserver</name> </connectionAttempt> </connectionAttempts>
That XML error message is formatted in SAS error XML which means that you were at least able to successfully create these two COM objects
$objFactory = New-Object -ComObject SASObjectManager.ObjectFactoryMulti2 $objServerDef = New-Object -ComObject SASObjectManager.ServerDef
According to your log the error occurs when you call
$objFactory.CreateObjectByServer(...)
I hope this helps you to isolate the error.
I ran into exactly same xml error message when I try accessing a C#/SAS Web Application hosted in IIS. I solved this issue by
going to: IIS Manager -> Application Pools -> Advanced Settings -> Identity, update Identity from Application Pool Identity to LocalSystem.
You guys are right, looks like a Windows execution privilage issue.
It's finally time to hack! Remember to visit the SAS Hacker's Hub regularly for news and updates.
Check out this tutorial series to learn how to build your own steps in SAS Studio.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.