SAS Integration Technologies and Vista
Ok, I am sure that I will get some grief about this but I needed to submit my SAS code from a .NET application. this was on my new PC which is running Vista 32. Anyway, no matter what I did, I kept getting the following error:
"Retrieving the COM class factory for component with CLSID {440196D4-90F0-11D0-9F41-00A024BB830C} failed due to the following error: 80040154."
Well, normally that is addressed by simply installing the IntTech client and setting permissions to None in dcomcnfg. It didn't work this time.
Here is what i did to fix it (people can try these in isolation to see which one is the root):
1. Right-click on the the inttech.exe file and run it in compatibility mode for Win XP SP2
2. Go into dcomcnfg and set every single SAS DCOM object with permissions of None.
I could play with this some more but I am now behind.
"Retrieving the COM class factory for component with CLSID {440196D4-90F0-11D0-9F41-00A024BB830C} failed due to the following error: 80040154."
Well, normally that is addressed by simply installing the IntTech client and setting permissions to None in dcomcnfg. It didn't work this time.
Here is what i did to fix it (people can try these in isolation to see which one is the root):
1. Right-click on the the inttech.exe file and run it in compatibility mode for Win XP SP2
2. Go into dcomcnfg and set every single SAS DCOM object with permissions of None.
I could play with this some more but I am now behind.
posted by Alan Churchill at
9:49 PM
4 Comments:
Alan,
Try this:
http://listserv.uga.edu/cgi-bin/wa?A2=ind0803A&L=sas-l&P=R8359&m=251486
Regards, Audi
By
Audi, at 9:05 AM
That CLSID is the SAS.Workspace 1.0, and the 0x80040154 means "class not registered".
If you're working with local SAS, this can be fixed with "sas /register" from your command prompt (in the SAS application directory).
On Vista, you might need to open your CMD window with "Run as Administrator" to affect this type of change - it hits the registry.
For remote SAS sessions, your inttechc\setup fix probably did the trick, because it registers the SAS.tlb (typelib) as part of its work. Again, you might have to Run as Administrator, but your "compatibility" mode approach might have amounted to the same thing.
By
Chris, at 10:32 AM
Alan,
I don't have a Unix question. But was wondering what ever happened to the Fireworks business. Did it explode like the Pinto?
By
DC.Past@yahoo.com, at 11:36 PM
I believe the proper command to register the clssids is sas /regserver. That worked for me.
By
Alan Churchill, at 7:30 AM
Post a Comment
<< Home