The user is getting the below Warning Message when launching the Promis.e Application. There are multiple reasons due to which this issue may occur. In this article are listed the most frequent issues that result in the below Error Message
1. Renaming or changing the folder/ file name in the WorkSpace .
How to fix the above issue a. Open the Promise.cfg located in WorkSpace folder for OOTB WorkSpace the file is located in the location "C:\ProgramData\Bentley\Promise CONNECT Edition\Configuration\WorkSpaces\Promise ANSI-IEEE Example\Standards\Promise" and open the file in Notepad / Notepad ++. If the WorkSpace is located on Network location skip to next step else skip to Step C. b. If the WorkSpace is located in the network location browse to the "WorkSpaceSetup.cfg" file located in "C:\ProgramData\Bentley\Promise CONNECT Edition\Configuration" and open it in Notepad / Notepad ++. The check the network location where the WorkSpace is located. Now in network location browse to the Promis.e.cfg file. c. Now check if the file name and the path is actually present in the WorkSpace folder where the Promise. cfg is located for each variables like Parts Database MDB file or Multi_Language_UI.mdb file or the Templates ........ If there is any difference then the Promise.cfg should be updated accordingly for the new location or else the folder / file name should be renamed back to original details which ever applied according to the user requirement. 2. One of the Configuration files is corrupted.
a. The user needs follow the steps from Previous case steps to reach the WorkSpace / WorkSet folder and they need to check my replacing files from the Backup WorkSpace / WorkSet by doing trial and error to check which of the configuration is actually corrupted. For example they can start with the first variable Parts Database mdb file and then Multi_Language_UI.mdb and then with the Options folder by replacing the files in actual WorkSpace/WorkSet with the once from the backup. The user can launch Promis.e after replacing file/files for each configuration to check if it fixes the issue. Note: Make sure that Promis.e is not running when replacing a file. Note: Please make a Backup of the WorkSpace and WorkSet before replacing the files.
3. Incomplete Creation of WorkSpace / WorkSet
a. When the user starts creating new WorkSpace / WorkSet using Promis.e CONNECT User Interface but the configurations files are not copied after creating them the user can follow the below Wiki Link to complete the Processes.