ActiveXPosh in PrimalScript?
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.
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.
- j.logan@logancomputerser.com
- Posts: 3
- Last visit: Wed Jul 19, 2017 7:52 am
ActiveXPosh in PrimalScript?
I have been attempting to make use of ActiveXPosh located in the Support Downloads>>Free Components area, as I thought this was now integrated with PrimalScript. Is that accurate? I wanted to try it out before buying, but the ActiveXPosh in the free components folder (both v2 and v3) fail to create the object when running your own included vbscript. I don't want to even download and install the trial if this component is not included/is deprecated.
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
Re: ActiveXPosh in PrimalScript?
That component has always been part of PrimalScript. I haven't looked at it in some time but it should still work. If it fails to create, most likely you didn't register the COM object or your don't have a prerequisite installed for it to register properly.
Hard to tell without any actual error code or message.
Hard to tell without any actual error code or message.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- j.logan@logancomputerser.com
- Posts: 3
- Last visit: Wed Jul 19, 2017 7:52 am
Re: ActiveXPosh in PrimalScript?
Thank you, I will give the trial a shot. I did register the dll and it states it went through just fine. However, as the last version in the free section is V3, I am guessing it is looking for both PS V3 and .Net 3.
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
Re: ActiveXPosh in PrimalScript?
Like I said, usually a failure to create an object produces an error code. That code is really important to determine what happened.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- j.logan@logancomputerser.com
- Posts: 3
- Last visit: Wed Jul 19, 2017 7:52 am
Re: ActiveXPosh in PrimalScript?
So I installed PrimalScript2017 trial, and I do not see the ActiveXPosh module unless I am looking in the wrong spot. As for the code I am using and the resultant error, I download a version and register it successfully:
I then attempt to run the vbscript located in the same directory where ActiveXPosh is installed, and get the following error, showing that it cannot create the object.
I then attempt to run the vbscript located in the same directory where ActiveXPosh is installed, and get the following error, showing that it cannot create the object.
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
Re: ActiveXPosh in PrimalScript?
The component is typically installed here: C:\Program Files\Common Files\SAPIEN Common
The PrimalScript installer registers the component correctly (usually) but manually running regasm version can screw things up.
I am assuming your Windows install is 64 bit, but I cannot be sure. The error code is usually related to cross platform problems, like trying to create a 32 bit object from a 64 bit program or vice versa.
The correct registration call is
regasm.exe activexposh.dll /codebase
From your path to regasm you ran the 32 bit version of it.
The 64 bit version is in C:\Windows\Microsoft.NET\Framework64\v2.0.50727 (note \framework64\ versus \framework\)
If you want to run and use it on a 64 bit machine from a 64 bit VBScript engine, you need to register it as a 64 bit component.
The PrimalScript installer registers the component correctly (usually) but manually running regasm version can screw things up.
I am assuming your Windows install is 64 bit, but I cannot be sure. The error code is usually related to cross platform problems, like trying to create a 32 bit object from a 64 bit program or vice versa.
The correct registration call is
regasm.exe activexposh.dll /codebase
From your path to regasm you ran the 32 bit version of it.
The 64 bit version is in C:\Windows\Microsoft.NET\Framework64\v2.0.50727 (note \framework64\ versus \framework\)
If you want to run and use it on a 64 bit machine from a 64 bit VBScript engine, you need to register it as a 64 bit component.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.