Installation troubleshooting information
Software version information and software release schedule
Installation switches and MSI mass installation
Each user on a computer has their own profile and their own set of permissions, which prevents unauthorized access to files and folders. Normally these permissions are set properly when the Unisoft software is first installed. However there may be situations when these permissions might need to be manually configured.
If the Unisoft Pronto software does not start correctly after installation locally or on a network it is usually a folder / file permissions issue and below is information and how to fix it.
Also the MARKUP.INI file, which stores user configuration data, may need its permissions adjusted if the BOM or XYR importer template windows are blank and newly created templates are not being saved properly along with other user configuration data.
It is advisable to work with your IT department or other network professional on these types of issues and you may wish to forward this webpage to them.
More details follow.
Troubleshooting CELLS Workflow MES software: Note: If you are having issues with running the Unisoft CELLS Workflow MES Product Tracking software then the permissions issues outlined below for the Unisoft Pronto series of software in most respects apply also to the Unisoft CELLS Workflow MES software. If the Unisoft CELLS Workflow MES software does not run correctly after installation it is usually a folder / file permissions issue. To see if it is a permissions issue try installing the software to a new directory that you the installer creates on the C: root drive, for example c:\cells-test and if the CELLS software runs correctly there it is most likely a permissions issue which you or your IT department can correct. Contact Unisoft for details.
To see if it is a permissions issue that is causing the problem of the Unisoft software not starting correctly then try installing the Unisoft software to a new directory that you the installer creates.
Test folder: A test for a permissions issue is to try installing the Unisoft software to a folder that you create that has lower permissions access on the C: root drive for example c:\unisoft-test . If the software runs ok from that folder that you created then that usually indicates that the other folder you had trouble installing too has a higher access permissions issue.
Below is information about a permissions issue and how to fix it.
Below is an explanation from the Unisoft software department on when the license gives the message "It appears that the license is not valid…."
When the Unisoft software is used we check for backdating by surreptitiously writing a date. When the executable for the Unisoft Pronto series of software modules which is called MARKUP.EXE can't write the file, it displays the "It appears that the license is not valid…." message and switches to shareware mode.
To write the file, of course, MARKUP.EXE needs write-access to the installation directory. So when the "It appears that the license is not valid…." message is displayed it is usually that the user set up the directory on the network as read-only. Therefore, the user needs to set permissions on the Unisoft installation directory to read/write.
Information on setting permissions follows.
The permissions fix that follows has worked for many Unisoft customers with permission issue problems.
Usually the main problem if the Unisoft software does not start correctly is permissions issues with the main directory where the Unisoft software is stored which is by default c:\program files(x86)\unisoft or c:\program files\unisoft .
It is advisable to work with your IT department or other network professional on this type of issue.
Additionally there may be a second permissions issue once the Unisoft software starts successfully and this issue is with the MARKUP.INI file which stores user configuration information and further details on this is below.
After the Unisoft software is installed and if it is not starting successfully then on the installed computer navigate to the Unisoft directory and give the Domain Users full-control to the folder the Unisoft software is install to which is by default c:\program files(x86)\unisoft or c:\program files\unisoft . The domain users is a group that every user on the network is a part of.
After this is done click the Advanced tab, select the Domain Users group from the list and click Replace all child object permissions. This will then give the users permissions to all files and folders in the directory.
The markup.ini file stores user configuration data such as BOM and XYR importer templates and other user data. The markup.ini file is normally located in the c:\windows directory.
The markup.ini file may need its permissions adjusted if with the Unisoft software started the BOM or XYR importer template window is blank and newly created templates are not being saved properly along with other user configuration data.
The markup.ini requires read and write permissions for the user that is running the Unisoft software. Normally these permissions are set properly when the Unisoft software is first installed.
If you are experiencing a problem with the BOM or XYR template window being blank and templates created are not being saved along with other user configuration data then adjust the permission settings on the markup.ini file similar to permissions issues outlined above for the main directory where the Unisoft software is installed.
It is advisable to work with your IT department or other network professional on this type of issue.
Granting users full access to the Unisoft folder generally will resolve license problems. To summarize:
For additional installation troubleshooting information click here.
For installation information click here.
Software version information and software release schedule.
