I hope this is correct location to post this question, if not please let me know.
I am seeing an issue running Geopak SS3 08.11.09.493 after installing the program using SCCM 2012 (Microsoft's System Center Configuration Manager). For those of you who might not know but SCCM is an automatic way to distribute applications to PC's on a network.
Anyway, this is the only Bentley application that has an issue after the installation completes. MicroStation, InRoads, ProjectWise, Culvertmaster, gINT, View, etc. all work as expected after install using SCCM. If I install Geopak by double clicking the msi or by using a batch file from a network drive (which is simulating what SCCM does) Geopak works as expected. I have tried multiple types of installations using SCCM, packages vs applications, and it all comes out the same. Using the SCCM to install Geopak will give me some VBA errors when trying to run certain pieces of the software.
Is there anyone else out there using SCCM to install Bentley applications? If so, has the Geopak install been successful?
On a side note, I used SCCM to install Geopak SS2 Refresh and it would mess up the install for a program that was previously installed. So if a program like HEC-RAS was installed manually by a user and then Geopak SS2 Refresh was installed by SCCM right after that the HEC-RAS install would try to install again when opening Geopak for use.
TIA
Sean
Hi Sean,
I do know of a conflict with some of the VBA commands when GEOPAK SS2 and SS3 are both installed on the same machine. Could you take a look at this thread (communities.bentley.com/.../89263.aspx) and see if any of the suggestions fix the VBA errors you are seeing? If so, we can then take a look at why the different installation method might be causing the issue (maybe it doesn't register the exe like it does in other installs?).
Thanks,
Kevin
To claify... I am particularly interested in whther running the GEOPAKCOM.EXE file in the bin directory will resolve the VBA errors. This is item #2 in the link I reference above.
Kevin,
Sorry for the late response. Yes I have ran the GEOPAKCOM.EXE and this did not fix the errors. I am pretty sure this has nothing to do with the exe not running at all or not running successfully.
This is probably a stab in the dark but it seems to me that it has something to do rights. Access rights, etc..
Every user has Admin rights to his/her computer.
Update.
I have found a fix for this issue! Based upon several tests, and I mean several, I have found that the Geopak and InRoads installs are system level msi installs. There are 2 different types of msi installs, user and system. Initially when setting up the installs using SCCM2012 I had use the setting for install as user which in most cases with other Bentley software works for our environment because everyone is an administrator to his/her computer. But with the Geopak and InRoads installs the setting to install as user corrupted the install.
I created new application installs and this time set the installs to run as system installs and have not had any issues since.
Answer Verified By: Sean Keene