Custom Reports and Forms on Network

If you store custom reports on a network resource, please enter the UNC path (for example, \\server\directory\custom) instead of a mapped network drive (for example, S:\custom) when prompted for the Custom Reports folder during the J1 Desktop installation. J1 Client Application Services is a Windows Service, and a limitation is that they cannot recognize mapped drives (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q180362).

If J1 Desktop is already installed, you can change the Custom Reports and Forms value in the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\JENZABAR\J1\<J1 version number>\Folders\Custom Reports and Forms

 

Logon User for Client Application Services

When J1 Client Application Services is installed, it asks for the login/password of the Windows user under which this Service would run (later, the same can be accessed in the Log On tab of the Properties window). This login account should have access to all local and network resources to successfully run J1 Desktop.  

1.         Check the Log File.  It will most likely provide information on why the Service did not start.

2.         Make sure the J1 Desktop application was run at least once on the machine. The first time J1 Desktop is run, it creates an ODBC DSN as well as registry entries required by J1 Client Application Services.

1.         Verify that J1 Client Application Services was installed and is started. Check this by opening the Services Manager (Start | Settings | Control Panel | Administrative Tools | Services). Start the Service if it has been stopped.

2.         Run the following SQL select statement: select database_name, db_name() from process_def.

If the database names do not match, run the following SQL statement: update process_def set database_name = db_name().

3.         Perform a SQL Profiler trace. Verify that the correct database name is being passed to the stored procedure named PROCESS_SCHEDULE$CHECK_STATUS. The name passed to the stored procedure needs to match the db_name() value.

4.         Open the Process Machine Definition window. Make sure the computer name exists and that the Run Scheduled Processes? checkbox is selected.

5.         If you performed a SQL trace, make sure the machine name being passed to the stored procedure named PROCESS_SCHEDULE$CHECK_STATUS is the same as the value stored in the Process Machine Definition window.

1.         Verify that J1 Client Application Services was installed and is started. Check this by opening the Services Manager (Start | Settings | Control Panel | Administrative Tools | Services). Start the Service if it has been stopped.

2.         Run the following SQL select statement: select database_name, db_name() from process_def

If the database names do not match, run the following SQL statement: update process_def set database_name = db_name().

3.         Perform a SQL Profiler trace. Verify that the correct database name is being passed to the stored procedure named PROCESS_SCHEDULE$CHECK_STATUS. The name passed to the stored procedure needs to match the db_name() value.

4.         Open the Process Machine Definition window. Make sure the computer name exists and that the Run Scheduled Processes? checkbox is selected.

5.         If you performed a SQL trace, make sure the machine name being passed to the stored procedure named PROCESS_SCHEDULE$CHECK_STATUS is the same as the value stored in the Process Machine Definition window.

If the job has been in the 'In Progress' status for an abnormally long time, follow the steps below:

1.    Make sure the user running the job has administrative rights. Verify or configure the "Jenzabar Client Application Services" Windows Service runs as a user in the local Administrators group for that machine to ensure the service can monitor and ???kill??? those scheduled jobs that hung or failed to complete. The CAS constantly checks to see how long jobs have been running and removes hung jobs from the system and marks them as ???Killed,??? but it must be run as a user in the local Administrators group.

When the CAS is installed, a configuration option lets your IT department specify the user under which the CAS service will run. If this user is not already in the administrator group, you can change the user via the Windows Services manager OR uninstall/reinstall the CAS and specify a different user. Steps for installing the CAS are included in the J1 Desktop installation and upgrade guides available on MyJenzabar.

2.         Check the Windows Task Manager for the appropriate J1 process executable. It will be named something like J1<version number>.exe. Right-click on the process, and select End Process. This will kill the hung process. Next, identify the process in the Process History window and change the status from 'In Progress' to 'Killed.'

3.         Check the My Documents folder on the machine hosting J1 Client Application Services. Make sure it is not mapped to a lettered network drive (for example, H:\).

4.         Open the Services manager (Start | Settings | Control Panel | Administrative Tools | Services). Right-click on the service named "J1 Client Application Services" and click on the Log On tab. Make sure that the same user who is currently logged in to the machine is also associated with the Service. Because some J1 Desktop processes make use of PBLs, files, etc., located on network resources, you need to be sure the service can access these network resources by being able to log in as a valid user.

5.         If you store custom reports on a network resource, please enter the UNC path (for example, \\server\directory\custom) instead of a mapped network drive (for example, S:\custom) when prompted for the Custom Reports folder during the J1 Desktop installation. J1 Client Application Services is a Windows Service, and a limitation is that they cannot recognize mapped drives (https://support.microsoft.com/en-us/topic/2b693418-fb80-1149-7034-78af6e6847ba).

If J1 Desktop is already installed, you can change the Custom Reports and Forms value in the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\JENZABAR\J1\<J1 version number>\Folders\Custom Reports and Forms

There is a setting within the WindowsService.exe.config file titled 'MaxHoursScheduledProcessAllowedToRun'. The process will automatically be killed if the in-progress job has been running longer than the 'MaxHoursScheduledProcessAllowedToRun' value.  

	The CAS Windows service will need to be running as a user with the ability to kill local tasks/processes.
	The WindowsService.exe.config file can be found where you???ve installed the J1 CAS: C:\Program Files (x86)\Jenzabar\J1 <version>\Client Application Services

 

1.         Check the My Documents folder on the machine hosting J1 Client Application Services. Make sure it is not mapped to a lettered network drive (for example, H:\).

2.         Open the Services manager (Start | Settings | Control Panel | Administrative Tools | Services). Right-click on the service named "J1 Client Application Services" and click on the Log On tab. Make sure that the same user who is currently logged in to the machine is also associated with the Service. Because some J1 Desktop processes make use of PBLs, files, etc., located on network resources, you need to be sure the service can access these network resources by being able to log in as a valid user.

3.         If you store custom reports on a network resource, please enter the UNC path (for example, \\server\directory\custom) instead of a mapped network drive (for example, S:\custom) when prompted for the Custom Reports folder during the J1 Desktop installation. J1 Client Application Services is a Windows Service, and a limitation is that they cannot recognize mapped drives (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q180362).

If J1 Desktop is already installed, you can change the Custom Reports and Forms value in the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JENZABAR\J1\<J1 version number>\Folders\Custom Reports and Forms

1.         Open the Process Definition window. Verify that a notification group is associated with the process.

2.         Open the Notification Group Definition window. Verify that J1 Desktop users are "selected."

3.         Open the Users window. Verify that the Notifications Enabled checkbox is selected for the particular user.

4.         Open the Maintain Config Table window. Look for the Characteristic named "REFRESH_INTERVAL." Make sure the user who has not yet received an application alert has waited the number of seconds specified in the setting.

5.         Have the user who is not receiving an application alert open the User Preferences window. Make sure that the Preferred Method in the Notifications group box is either Application Alert or Both App. Alert and E-mail.

1.         Open the Process Definition window. Verify that a notification group is associated with the process.

2.         Open the Notification Group Definition window. Verify that J1 Desktop users are "selected."

3.         Open the Users window. Verify that they have an ID Number assigned. If so, open the Maintain Address window and make sure that at least one email address has the Notifications Enabled? checkbox selected.

4.         Open the SMTP Relay Configuration window. Ensure that a Relay Server Name has been selected.

5.         Verify that the machine selected as the Relay Server has J1 Client Application Services installed and running. Also, open the Log File on the Relay Server machine (Start | Settings | Control Panel | Administrative Tools | Event Viewer). It may provide information on why a message was not sent (i.e., it was blocked by the anti-virus software, the machine does not have permissions to relay messages to the SMTP server, etc.).

6.         Have the user who is not receiving an e-mail message open the User Preferences window. Make sure that the Preferred Method in the Notifications group box is either Email or Both App. Alert and Email.

7.         If the e-mail notification was created by a Purchasing event, have the user who is expecting the e-mail message open the Set My Profile Sharing Preferences window and verify that the e-mail address entered is valid.