| View previous topic :: View next topic |
| Author |
Message |
Stmacken
Joined: 16 Feb 2016
Posts: 2
Location: Inverness, Scotland
|
 Posted: Tue Feb 16, 2016 5:46 am Post subject: PG Admin Fatal Error #339 |
 |
|
I am responsible for packaging PageGate 7.0.21 so that we can deploy it to XP machines using SCCM to the specific users that need it. I have managed to convert the pgssetup.exe (which was extracted from the %temp% folder while running Pgsetup.exe) into a usable msi file.
It installs successfully and after adding regsvr32.exe MSWINSCK.ocx to get rid of the Runtime error '339' Component 'MSWINSCK.ocx' or one of it's dependencies not correctly registered. A file is missing or invalid' when launching PageGate Server. I still get the below error when trying to launch PageGate Admin.
PG ADMIN Fatal Error
Error #339 Invalid Operation. In Procedure: tadmin_resize
I have looked through previous posts and the net in general but can't find a suitable fix for this.
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4369
|
| Posted: Tue Feb 16, 2016 9:38 am Post subject: |
|
|
| Just to double check, what component(s) of PageGate are you trying to deploy to those windows XP machines? The reason I ask is that you mentioned using the pgssetup.exe that was extracted from the main installer but that specific sub-setup file is the one that's tied to the installation of the PageGate Server and should not be used on a workstation since that's the primary, core server install. |
|
| Back to top |
|
Stmacken
Joined: 16 Feb 2016
Posts: 2
Location: Inverness, Scotland
|
| Posted: Tue Feb 16, 2016 11:09 am Post subject: |
|
|
I'm installing PageGate Admin, Server and Monitor and it's only PageGate Admin that is showing the error.
After registering the 'mswinsck.ocx' file, PageGate Server now opens fine, had no issues with Monitor but when launching PageGate Admin I receive the below error.
I'm just making sure on my side that it isn't an issue with the way I created the msi or the builds we use to test the applications.
Just wondered if you knew of this issue and if there was a fix for it
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4369
|
| Posted: Tue Feb 16, 2016 11:18 am Post subject: |
|
|
The trouble is that if you're using the server install for the Admin on a workstation, that's not the right version of the Admin. When you do the server install, it installs all of the major components of the server - including the server copy of the admin and monitor.
Also, the PG Admin installation has a few OCX/DLL files that it registers as an automatic process during the installation, so there's more than just the mswinsck.ocx file that will need to be registered and may be part of the issue.
I suppose you could segregate out the pgasetup.exe and pgmsetup.exe files from the installation but you'd also need to grab every support file the installation needs to call on as well.
I'd recommend uninstalling what you have in place now, then use the pgsetup.exe file to launch a properly extracted installation, then run through the "Install Additional PG Admin" and "Install Additional PG Monitor" installations on those systems. |
|
| Back to top |
|
|
