Script Packager and Com Objects

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
User avatar
kellydyane
Posts: 3
Joined: Tue Apr 28, 2009 10:46 am

Script Packager and Com Objects

Post by kellydyane » Tue Apr 28, 2009 10:46 am

I am using the script packager to package an HTA application (on Windows XP) and have included a dll for the MS Soap Toolkit. When I run this on a system (Server 2003) I get an error that the object cannot be created. When I find the dll on the file system (%windir%system32) and try and register is manually, the registration fails. What am I doing wrong.

Should the dll be registered when I run the packaged exe?

User avatar
Alexander Riedel
Posts: 7053
Joined: Tue May 29, 2007 4:43 pm

Script Packager and Com Objects

Post by Alexander Riedel » Tue Apr 28, 2009 5:15 pm

Usually when a dll cannot be registered some dependency or prerequisite is not installed.
I find the tool here: http://www.dependencywalker.com/
very handy to determine what other dlls a module depends on.

The SOAP toolkit has a runtime installer, found here:
http://www.microsoft.com/downloads/deta ... layLang=en

I think it would be easier to run this once on a server rather than including individual dlls.

Alex
Alexander Riedel
SAPIEN Technologies, Inc.