How to Install and Configure a Printer on your StreamServe Host Windows Server

Scenario: I am continuously being asked to set up printers so that they can communicate with StreamServe. The best way to do this is to configure a printer on the Test host server, make sure its successfully printing and then replicate in the Live host server. This tutorial shall instruct you how to add a printer to a Windows Server.

PLEASE NOTE: The printer I am adding is a ZEBRA label printer for the Goods Intake Bay of a warehouse

  1. Click Start and select Devices and Printers and select the Add a printer option (Figure 1)
37
Figure 1
  1. Select Add a local or network printer as an administrator (Figure 2)
38
Figure 2
  1. Select Add a local printer (Figure 3)

    39
    Figure 3
  2. Select the Create a new port option and make sure it is a Standard TCP/IP port (see Figure 4)
  3. Click Next

    40
    Figure 4
  4. Type the new IP address into the Hostname or IP address textbox (Figure 5). This will automatically input the same IP into the Port name textbox

TIP: If the IP address is already being used then the suffix _1 will be appended to the IP address in the Port name textbox e.g.  xx.xx.xx.xxx_1

  1. Click Next
41
Figure 5
  1. The IP of the printer is queried and detected as long as it is online on the network
  2. Select the Generic Network Card as the Device Type (Figure 6)
  3. Click Next
42
Figure 6
  1. Select the Manufacturer and Printer model you are configuring (Figure 7)

TIP: Click the Windows Update button to update the list of models / drivers from a central Microsoft repository.

  1. Click Next
43
Figure 7
  1. Type the Printer name – you should make this a meaningful name. In this case the name is INTAKE_BAY (Figure 8).
  2. Click Next to install the printer
code10
Figure 8
  1. Select the Share this printer … option , type in a meaningful Location and type the IP address into the Comment textbox (Figure 9)
  2. Click Next
code11
Figure 9

IMPORTANT: The printer is now installed. I advise you to run a test page (Figure 10) to make sure it is printing OK.

code12
Figure 10

IMPORTANT: The printer is now visible in Devices and Printers (Figure 11)

code13
Figure 11

Troubleshoot: Control Center producing the error: Connect time-out

Explanation: You are trying to connect to your site ‘Test’ but you received a connecting message for a while and then the Control Center produces the Connect time-out error (see Figure 1). This is happening because the Management Gateway Service has been stopped. You must restart this service.

1
Figure 1: The Connecting to message turns into the a Connect time-out error

Solution: Restart the Stopped Service

  1. Open the Services application on your host server and check the status of the StreamServe Management Gateway service – it has been stopped (see Figure 2)
2
Figure 2: the stopped service
  1. To restart the service, right click on it and select Start and the service will be restarted (see Figure 3)
3
Figure 3: The restarted service
  1. Re-connect to the site and it should connect OK

Troubleshoot: M3 Users are not receiving output (Part 2)

Explanation: Users are complaining that their submitted jobs in M3 are not being received in their inboxes.

Problem Diagnosis

  1. Open MNS206 (M3 Output. Manage per Job)
  2. Change the Sorting order to 6-Output Status
  3. Type SND into the Sts column and type the date into the Ent dt column
  4. Press Enter

You now have a list of jobs that have the status SND (Sent) which means they have been sent but not saved or received by M3 – they have a status of SAV when they are successfully received by M3. Figure 1 indicates a sample job with SND.

1
Figure 1: A submitted job with status SND

Problem: The problem is with M3. You need to contact your M3 administrators and ask them to view its performance. They should especially check if any autojobs need to be restarted.

Once M3 has been fixed, all jobs with status SND will now automatically begin to hit StreamServe and produce output for users.

You do not need to resend jobs! 

You should monitor all traffic for a while and constantly refresh MNS206 to see jobs change status from SND to SAV (Sent & Saved).

Troubleshoot: M3 Users are not receiving output (Part 1)

Scenario: Users are complaining that their submitted jobs in M3 are not being received in their inboxes.

Problem Diagnosis:

  1. Open MNS206 (M3 Output. Manage per Job)
  2. Change the Sorting order to 6-Output Status
  3. Type MSG into the Sts column and type the date into the Ent dt column
  4. Press Enter

You now have a list of jobs that have the status MSG (Error Detected) – these jobs were sent during the downtime. Figure 1 indicates a sample job with MSG. Now You must find out what error has been detected.

50
Figure 1: A submitted job at status MSG
  1. Right-click on one of the MSG jobs and select Display
    1. The E panel is triggered
  2. The Message is CR_0025 and the description tells you that the server is not responding –  Figure 2 displays these details
49
Figure 2: Job error message onn MNS206/E panel

Problem: The problem is with StreamServe. The Control Center service is no longer running so it needs to be restarted.

Solution: 

  1. Click back to return to MNS206
  2. Open Control Center – the service will not be running
  3. Start the service

All jobs with status MSG will now automatically begin to hit StreamServe and produce output for users.

You do not need to resend jobs! 

You should monitor all traffic for a while and constantly refresh MNS206 to see jobs change status from MSG to SAV (Sent & Saved).

Troubleshoot: Control Center producing an ‘Fatal error: args start.arg(2:No such file or directory)’ error

Explanation: The first time you deployed an exported project in Control Center you did not check the Include argument file in export checkbox

The very first time you export a project you must check the Include argument file in export checkbox so that the start.arg file is created in the Working Directory

Figure 1 displays the checkbox to check:

32
Figure 1

Export, deploy and test!

Troubleshoot: Control Center producing the ** UNLICENSED ** warning

Explanation: The application license is not present in your Working Directory folder structure

  1. Obtain the strs.lic file

TIP: Copy an existing / valid file from the same path as another application of another licensed project

  1. Open the Working Directory by accessing the Platform folder on the host server:

..\ManagementGateway\5.6.1\root\applications\Application_Name\Platform

  1. Paste the file into the Platform folder

31

Export, deploy and test! The ** UNLICENSED ** will now disappear.