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.
Don't miss out on SAS Innovate - Register now for the FREE Livestream!
Can't make it to Vegas? No problem! Watch our general sessions LIVE or on-demand starting April 17th. Hear from SAS execs, best-selling author Adam Grant, Hot Ones host Sean Evans, top tech journalist Kara Swisher, AI expert Cassie Kozyrkov, and the mind-blowing dance crew iLuminate! Plus, get access to over 20 breakout sessions.
What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.
Find more tutorials on the SAS Users YouTube channel.