Northstar Desktop is not completing the daily commit.

If you get the Northstar Desktop committing screen frozen on the Processing Screen, and it just remains stuck on that status for more than 5 minutes, you might have a problem with the Positouch Nightly process not being able to complete, and therefore the Positouch system is not creating the dbfs files needed by Northstar.
The Norhstar Desktop processing screen will show a frozen processing status as depicted here:

To check if there is a potential issue with the Positouch Nightly process, you may check some things, such as:

a) Using te MS DOS Command prompt go to the L:\sc directory and run the following command:
L:\sc> dir *.$$$, the system will be displaying all the files with the *.$$$, try to search for the file proc.$$$. This file usually is present when the nightly process has not completed, and therefore, no posidbf.exe command would be able to be executed by Northstar Desktop.

 

b) You may also check status of the Backzip files creation. The Positouch creates the Back.zip files during the nightly process. If you notice the absence of current Back*.zip files, it may indicate a problem with the nightly process not completing.

 

c) You can also check the qreports.log. This log is located in the backoffice in c:\qreports\log
You can open it by running the MS DOS command: C:\qreports\notepad qreports.log
The log will indicate that Northstar Desktop is Inserting data into a table, but no information about the completion of the task.
As depicted in the screenshot:

Once you have proven that the nightly process has not been running, you may proceed to apply the following article:

"POSitouch - Basic Troubleshooting of Nightly processing - Nightly" located at:

https://cbsnorthstar.atlassian.net/wiki/spaces/SM/pages/63275189

Once the nightly process has been properly fixed, and there is certainty that the posidbf.exe command can be executed by Northstar Desktop, you will be able to complete the Northstar Desktop processing without freezing.