Project Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Holly Herring — Thu, 16 Nov 2017 18:06:19 GMT

Current Revision posted to OpenRoads | OpenSite Wiki by Holly Herring on 11/16/2017 6:06:19 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

When launching InRoads or GEOPAK in ProjectWise V10.00.02.265 using a managed workspace, user gets the error "Last Error [222] Cannot start application for the specified document. Check your program association. Failed to generate managed workspace configuration file. can't open macro file [C:\Program Files (x86)\Common Files/Bentley Shared/Civil Platform/08.11.09/Bentley Civil Assembly Location MS - Required.2.0.cfg],[C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\MicroStation\config\appl\geopak.3.1.cfg, line 24"

Explanation:

This error is caused because ProjectWise CONNECT V10.00.02.265 is resolving the variable "$(CommonProgramFiles)" to the C:\Program Files\Common Files folder (since it is a 64 application) instead of the C:\Program Files (x86)\Common Files which is required by the 32 bit InRoads and GEOPAK SS2*/SS3*/SS4 products.

GEOPAK Solution:

To resolve the problem for GEOPAK, complete one of the two:

OPTION 1: Open the geopak.3.1.cfg (SS4) file located here: C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\MicroStation\config\appl
- Add CommonProgramFiles=C:\Program Files (x86)\Common Files\ to the top of the file after line 11, %if defined (Load_GEOPAK_SS4)

*GEOPAK SS3 users should edit the geopak.3.0.cfg.

OPTION 2: add a new Managed workspace variable at the Predefined or Global level that sets CommonProgramFiles=C:\Program Files (x86)\Common Files\ This Managed Workspace variable could then be added to the GEOPAK application, or to any files/folders that will use GEOPAK

InRoads Solution:

To resolve the problem for InRoads SS4, complete one of the two:

OPTION 1: Open the inroads.3.1.cfg (SS4) file located here: C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\MicroStation\config\appl
- Add the two variables below to the top of the file after line 6, %if defined (Load_InRoads_SS4)
  - CommonProgramFiles=C:\Program Files (x86)\Common Files\
  - INROADS_PATH=${registryread{"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Bentley\InRoads Group(SELECTseries 4)\08.11.09\PathName"}}

*InRoads SS3 users should edit the inroads.3.0.cfg. InRoads SS2 users should edit the InRoadsAT.cfg. Note that the file path name for INROADS_PATH will be different for SS3 and SS2.

OPTION 2: Add two new Managed workspace variables at the Predefined or Global level that sets CommonProgramFiles=C:\Program Files (x86)\Common Files\ and InRoads_Path=C:\Program Files (x86)\Bentley\InRoads Group (SELECTseries 4)\ This Managed Workspace variable could then be added to the InRoads application, or to any files/folders that will use InRoads
- *Note that the file path name for INROADS_PATH will be different for SS3 and SS2.

Tags: last error 222, error, Last Error [222]

Project Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Holly Herring — Thu, 16 Nov 2017 18:05:15 GMT

Revision 12 posted to OpenRoads | OpenSite Wiki by Holly Herring on 11/16/2017 6:05:15 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

Explanation:

GEOPAK Solution:

To resolve the problem for GEOPAK, complete one of the two:

OPTION 1: Open the geopak.3.1.cfg (SS4) file located here: C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\MicroStation\config\appl

- Add CommonProgramFiles=C:\Program Files (x86)\Common Files\ to the top of the file after line 11, %if defined (Load_GEOPAK_SS4)

*GEOPAK SS3 users should edit the geopak.3.0.cfg.

OPTION 2: add a new Managed workspace variable at the Predefined or Global level that sets CommonProgramFiles=C:\Program Files (x86)\Common Files\ This Managed Workspace variable could then be added to the GEOPAK application, or to any files/folders that will use GEOPAK

InRoads Solution:

To resolve the problem for InRoads SS4, complete one of the two:

OPTION 1: Open the inroads.3.1.cfg (SS4) file located here: C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\MicroStation\config\appl

- Add the two variables below to the top of the file after line 6, %if defined (Load_InRoads_SS4)
  - CommonProgramFiles=C:\Program Files (x86)\Common Files\
  - INROADS_PATH=${registryread{"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Bentley\InRoads Group(SELECTseries 4)\08.11.09\PathName"}}

*InRoads SS3 users should edit the inroads.3.0.cfg. InRoads SS2 users should edit the InRoadsAT.cfg. Note that the file path name for INROADS_PATH will be different for SS3 and SS2.

OPTION 2: Add two new Managed workspace variables at the Predefined or Global level that sets CommonProgramFiles=C:\Program Files (x86)\Common Files\ and InRoads_Path=C:\Program Files (x86)\Bentley\InRoads Group (SELECTseries 4)\ This Managed Workspace variable could then be added to the InRoads application, or to any files/folders that will use InRoads

- *Note that the file path name for INROADS_PATH will be different for SS3 and SS2.

Tags: last error 222, error, Last Error [222]

Project Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Holly Herring — Mon, 06 Nov 2017 15:04:33 GMT

Revision 11 posted to OpenRoads | OpenSite Wiki by Holly Herring on 11/6/2017 3:04:33 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

Answer:

To resolve the problem the user can either

1.) For GEOPAK: edit the geopak.3.1.cfg (SS4) file and add CommonProgramFiles=C:\Program Files (x86)\Common Files\ to the top of the file

For InRoads:

a.) edit the inroads.3.1.cfg (SS4) file and add CommonProgramFiles=C:\Program Files (x86)\Common Files\ to the top of the file

b.) also, add INROADS_PATH=${registryread{"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Bentley\InRoads Group(SELECTseries 4)\08.11.09\PathName"}} to the top of the file

2.) Add a new Managed workspace variable at the Predefined or Global level that sets CommonProgramFiles=C:\Program Files (x86)\Common Files\ and if using InRoads, this: InRoads_Path=C:\Program Files (x86)\Bentley\InRoads Group (SELECTseries 4)\. This Managed Workspace variable could then be added to the InRoads/GEOPAK application, or to any files/folders that will use InRoads/GEOPAK.

*GEOPAK SS3 users should edit the geopak.3.0.cfg. InRoads SS3 users should edit the inroads.3.0.cfg. InRoads SS2 users should edit the InRoadsAT.cfg. Note that file path names will be different for (1b)depending on what select series is being used.

Tags: last error 222, error, Last Error [222]

Project Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Holly Herring — Mon, 06 Nov 2017 15:03:07 GMT

Revision 10 posted to OpenRoads | OpenSite Wiki by Holly Herring on 11/6/2017 3:03:07 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

Answer:

To resolve the problem the user can either

1.) For GEOPAK: edit the geopak.3.1.cfg (SS4) file and add CommonProgramFiles=C:\Program Files (x86)\Common Files\ to the top of the file

For InRoads:

a.) edit the inroads.3.1.cfg (SS4) file and add CommonProgramFiles=C:\Program Files (x86)\Common Files\ to the top of the file

b.) also, add INROADS_PATH=${registryread{"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Bentley\InRoads Group(SELECTseries 4)\08.11.09\PathName"}} to the top of the file

Tags: last error 222, Last Error [222]

Project Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Holly Herring — Mon, 30 Oct 2017 15:37:12 GMT

Revision 9 posted to OpenRoads | OpenSite Wiki by Holly Herring on 10/30/2017 3:37:12 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

Answer:

To resolve the problem the user can either

1.) For GEOPAK: edit the geopak.3.1.cfg (SS4) file and add CommonProgramFiles=C:\Program Files (x86)\Common Files\ to the top of the file

For InRoads:

a.) edit the inroads.3.1.cfg (SS4) file and add CommonProgramFiles=C:\Program Files (x86)\Common Files\ to the top of the file

b.) also, add INROADS_PATH=${registryread{"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Bentley\InRoads Group(SELECTseries 4)\08.11.09\PathName"}} to the top of the file

Project Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Holly Herring — Thu, 14 Sep 2017 19:34:44 GMT

Revision 8 posted to OpenRoads | OpenSite Wiki by Holly Herring on 9/14/2017 7:34:44 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

Answer:

To resolve the problem the user can either

1.) For GEOPAK: edit the geopak.3.1.cfg (SS4) file and add "CommonProgramFiles=C:\Program Files (x86)\Common Files\" to the top of the file

For InRoads:

a.) edit the inroads.3.1.cfg (SS4) file and add "CommonProgramFiles=C:\Program Files (x86)\Common Files\" to the top of the file

b.) also, add "INROADS_PATH=${registryread{"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Bentley\InRoads Group(SELECTseries 4)\08.11.09\PathName"}}" to the top of the file

2.) Add a new Managed workspace variable at the Predefined or Global level that sets "CommonProgramFiles=C:\Program Files (x86)\Common Files\" and if using InRoads, this: "InRoads_Path=C:\Program Files (x86)\Bentley\InRoads Group (SELECTseries 4)\". This Managed Workspace variable could then be added to the InRoads/GEOPAK application, or to any files/folders that will use InRoads/GEOPAK.

Project Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Kevin McDonald — Thu, 14 Sep 2017 15:25:27 GMT

Revision 7 posted to OpenRoads | OpenSite Wiki by Kevin McDonald on 9/14/2017 3:25:27 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

Answer:

To resolve the problem the user can either

1.) For GEOPAK: edit the geopak.3.1.cfg file and add "CommonProgramFiles=C:\Program Files (x86)\Common Files\" to the top of the file

For InRoads:

a.) edit the inroads.3.1.cfg file and add "CommonProgramFiles=C:\Program Files (x86)\Common Files\" to the top of the file

b.) also, add "INROADS_PATH=${registryread{"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Bentley\InRoads Group(SELECTseries 4)\08.11.09\PathName"}}" to the top of the file

Project Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Kevin McDonald — Fri, 08 Sep 2017 16:12:13 GMT

Revision 6 posted to OpenRoads | OpenSite Wiki by Kevin McDonald on 9/8/2017 4:12:13 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

Answer:

To resolve the problem the user can either

1.) For GEOPAK: edit the geopak.3.1.cfg file and add "CommonProgramFiles=C:\Program Files (x86)\Common Files\" to the top of the file

For InRoads:

a.) edit the inroads.3.1.cfg file and add "CommonProgramFiles=C:\Program Files (x86)\Common Files\" to the top of the file

b.) also, add "InRoads_Path=C:\Program Files (x86)\Bentley\InRoads Group (SELECTseries 4)\" to the top of the file

Project Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Beebe Ray — Fri, 18 Aug 2017 13:48:13 GMT

Revision 5 posted to OpenRoads | OpenSite Wiki by Beebe Ray on 8/18/2017 1:48:13 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

Answer:

To resolve the problem the user can either

1.) For GEOPAK: edit the geopak.3.1.cfg file and add "CommonProgramFiles=C:\Program Files (x86)\Common Files\" to the top of the file

For InRoads: edit the inroads.3.1.cfg file and add "CommonProgramFiles=C:\Program Files (x86)\Common Files\" and on another line "InRoads_Path=C:\Program Files (x86)\Bentley\InRoads Group (SELECTseries 4)\" to the top of the file

Project Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Holly Herring — Thu, 10 Aug 2017 20:44:01 GMT

Revision 4 posted to OpenRoads | OpenSite Wiki by Holly Herring on 8/10/2017 8:44:01 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

Answer:

To resolve the problem the user can either

1.) For GEOPAK: edit the geopak.3.1.cfg file and add "CommonProgramFiles=C:\Program Files (x86)\Common Files\" to the top of the file

Project Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Holly Herring — Thu, 10 Aug 2017 14:52:52 GMT

Revision 3 posted to OpenRoads | OpenSite Wiki by Holly Herring on 8/10/2017 2:52:52 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

Answer:

To resolve the problem the user can either

1.) Edit the geopak.3.1.cfg or inroads.3.1.cfg file and add "CommonProgramFiles=C:\Program Files (x86)\Common Files\" to the top of the file
or
2.) Add a new Managed workspace variable at the Predefined or Global level that sets "CommonProgramFiles=C:\Program Files (x86)\Common Files\". This Managed Workspace variable could then be added to the InRoads/GEOPAK application, or to any files/folders that will use InRoads/GEOPAK.

Project Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Holly Herring — Wed, 09 Aug 2017 21:01:07 GMT

Revision 2 posted to OpenRoads | OpenSite Wiki by Holly Herring on 8/9/2017 9:01:07 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

Answer:

To resolve the problem the user can either

1.) Edit the geopak.3.1.cfg file and add "CommonProgramFiles=C:\Program Files (x86)\Common Files\" to the top of the file
or
2.) Add a new Managed workspace variable at the Predefined or Global level that sets "CommonProgramFiles=C:\Program Files (x86)\Common Files\". This Managed Workspace variable could then be added to the InRoads/GEOPAK application, or to any files/folders that will use InRoads/GEOPAK.

Projectect Managed Workspace error starting InRoads or GEOPAK in ProjectWise CONNECT V10.00.02.265

Kevin McDonald — Thu, 13 Jul 2017 21:55:13 GMT

Revision 1 posted to OpenRoads | OpenSite Wiki by Kevin McDonald on 7/13/2017 9:55:13 PM

Product(s):	InRoads/GEOPAK
Version(s):	08.11.09.878
Area:	ProjectWise

Question:

Answer:

To resolve the problem the user can either