Problem repackaging SAS 9.1 Base
Hi,
I am repackaging SAS 91 base application using Wise. I always have error 1911 on sassps .dll. The strange thing is that this DLL is not in the self reg table and is set to "do not register" under file details. It seems that Wise is still trying to register this dll. Do you have an idea where to look from there? There is about 130 references to that file in the tables.
Thanks for your inputs.
Bob
I am repackaging SAS 91 base application using Wise. I always have error 1911 on sassps .dll. The strange thing is that this DLL is not in the self reg table and is set to "do not register" under file details. It seems that Wise is still trying to register this dll. Do you have an idea where to look from there? There is about 130 references to that file in the tables.
Thanks for your inputs.
Bob
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
SAS is a bear but it can be re-packaged. You may, however, be better off recording an ISS file and using that in an MSI wrapper to silent deploy it.
Coming to your actual problem, this wouldn't be the first vendor to produce DLLs with the DLLRegisterServer entry-point which don't actually contain any COM information: the JRE support files NJAVAxyz.DLLs are my favourites. WiseComCapture merely looks for this entry-point to decide if a file is registerable. It should, of course, go further but there you are...
If the file doesn't register with RegSvr32, then abandon trying to register it. To determine where your MSI is attempting to register that file, run the MSI through the Wise debugger. When the 1911 dialog pops up, switch back to the debugger: it will be halted at the action responsible.
Coming to your actual problem, this wouldn't be the first vendor to produce DLLs with the DLLRegisterServer entry-point which don't actually contain any COM information: the JRE support files NJAVAxyz.DLLs are my favourites. WiseComCapture merely looks for this entry-point to decide if a file is registerable. It should, of course, go further but there you are...
If the file doesn't register with RegSvr32, then abandon trying to register it. To determine where your MSI is attempting to register that file, run the MSI through the Wise debugger. When the 1911 dialog pops up, switch back to the debugger: it will be halted at the action responsible.
Posted by:
AngelD
16 years ago
Check the CustomAction table for entries similar to [SystemFolder]msiexec.exe /y "[#sassps.dll]"
Posted by:
jmcfadyen
16 years ago
it can also be registered using Registry Typelib ClassId tables and cause a similar issue.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
