Job Server Technical Support
Solutions to frequently encountered problems are provided in the Trouble Shooting Help topic for BJS Administrator. After starting BJS Administrator, select Contents in the Help menu. Choose Search, then select the Trouble Shooting Help topic.
Technical Support Request Form
To expedite your technical support request, please provide the following. After this information is provided, the records will be updated, and technical support staff will reply.
Feel free to cut and paste this text and email it. Camellia Software’s
full contact information is on the order form in BJSINFO.ZIP.
The support staff does not participate in online video or telephone
1. The number of usernames per server
2. BJS build number on both clients and servers
3. Current licensed user's name, email, telephone number and address where
the BJS server is installed. Street name and number, city, state, municipality or province and postal code. Country name.
4. Purchase dates of all licenses
5. The number of Windows NT 4.0, Windows 2000, 2003, 2008, 2012 Original Release, 7, 8, XP and Vista computers running the BJS service.
6. Please send a copy of the BJSSYS.DAT file.
This file is located in the BJS installation directory on your BJS Server.
The path for this file will be :
Where ...BJS is the directory where you installed Batch Job Server.
7. Microsoft operating system(s) being used.
8. The complete text of any error messages in the application event log or
Each Windows computer executing BJS batch jobs is considered to be a BJS server. Test servers, development servers, backup servers, emergency servers, disaster recovery system servers, cloned servers, and production servers must be licensed. Each of these computers requires a separate BJS license.
Batch Job Server Support Pricing
All technical documentation for Batch Job Server including information on obtaining technical support is contained in the Help system for BJS Administrator. To install BJS Administrator, return to the Batch Job Server home page and download Batch Job Server.
An incident is automatically closed by Camellia Software Staff after 10 calendar days from the date of the last communication by the end user (customer), if the end user is not exchanging ongoing communication. The end user may reopen the incident by starting a new incident, by contacting Camellia Software via email. If you have additional questions, contact our office via email.
Migrate BJS Jobs to New BJS Servers
1. Stop the BJS service on the old server and the new server, after
installing BJS Administrator and the BJS service.
2. Copy the BJS\CTRLDATA directory from the old server to the new server
3. Populate the Batch Users, Batch Job Dir Users and Batch Support local
groups on the new server with the appropriate BJS user accounts.
4. Start the BJS service on the new BJS server.
5. Modify the usernames for your batch jobs to usernames in the new
domain, if necessary.
6. Modify the UNC BAT file path locations for your jobs, if necessary.
7. Set the BJS service parameters to the values used on the old BJS
server. This is done in the Server Administration dialog in BJS
Administrator. Select Administer in the Server menu to display this
dialog, then click the Change Service Parameters button.
8. Stop and restart the BJS service to complete migrating the server.
Locating the BJS Build Number
In the Startup Message: The BJS version and build are in the BJS service startup message in the Application Event log. Stop and restart the BJS service and then open the application event log and find the startup message.
In the Job Log Header: An alternate way to find the BJS version and build is to open BJS Administrator, connect to BJS on the computer where the BJS service is running. Then double-click on a job appearing in the Active Job List. This appears right after you connect. The job log for the job will appear on the screen. The BJS version and build are in the job log header.
Limitations of the Microsoft Operating Systems
Technical problems experienced are not always caused by BJS. These
problems can be caused by limitations or the design of the Microsoft
Windows operating systems. For those with BJS technical support, Camellia Software staff will work to
discover if this is the case.
Our experienced, senior level staff has extensive experience with
Windows. Our knowledge of the Windows operating systems is based on
publicly available information from Microsoft and their corporate website.
Camellia Software does not represent Microsoft. We are third party
software developers for the Windows operating systems.
If it is determined that a problem originates from a Microsoft product,
you will be asked to open a support incident with Microsoft. We will be
happy to work with you and Microsoft to resolve the incident.
If an incident is opened, please let us know how it resolves.
We reserve the right to reject questions,
emails, or telephone calls that include inappropriate content,
profanity, slander, disparaging references to other retailers, spam or
personal information. Thank you for your understanding and have a