Troubleshooting of Management Services

File C:\Temp\xyz.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see “get-help about_signing” for more details.

• Run once:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned

• See also Initiating Tpms.Powershell.

Client: A local exception was caught. StatusCode: 401, ReasonPhrase: 'Unauthorized' (From Exception: HttpClientException)

• Maybe Tpms.Powershell can’t log onto Tpms.Service.
• Restart the machine on which you installed Tpms.Service.
• Check whether Windows PowerShell runs as Administrator.
• Check whether credentials must be specified to access a remote machine, e. g. with

  New-TpmsObj­SetupAgent -Credential

  See script containing Start-TpmsSetupByAgent.

• On the Tpms.Service machine, add the account used to log on to the Tpms.Powershell computer to the local Administrators group.
• See also the section User permissions.

Client: A local exception was caught. An error occurred while sending the request (From Exception: HttpRequestException) Unable to connect to the remote server (From Exception: WebException) No connection could be made because the target machine actively refused it ... (From Exception: SocketException)

• Maybe Tpms.Powershell can’t log onto Tpms.Service.
• Restart the machine on which you installed Tpms.Service.
• Check whether Windows PowerShell runs as Administrator.
• On the Tpms.Service machine, add the account used to log on to the Tpms.Powershell computer to the local Administrators group.
• See also the section User permissions.

Client: A local exception was caught. InnerDispatch: Level: Error, Origin: Client, Message: StatusCode: 500, ReasonPhrase: 'Internal Server Error'', Version: 1.1, Content: System.Net.Http.StreamContent

• The error may occur on older versions when trying to connect from Tpms.Service to Tpms.Agent (siehe Initiating Tpms.Powershell).
• Check if Microsoft Visual C++ 2013 Redistributable (x64) is installed. If necessary, install it manually.

InnerDispatch: Level: Error, Origin: Client, Message: StatusCode: 401, ReasonPhrase: 'Unauthorized', Version: 1.1, Content: System.Net.Http.StreamContent

• Maybe Tpms.Powershell can’t log onto Tpms.Service.
• Restart the machine on which you installed Tpms.Service.
• Check whether the account which was used to start the Tpms.Powershell terminal window is able to log onto the Tpms.Service machine.
• See also the section User permissions.

Service: An error occurred while sending the request. Message: The remote server returned an error: (401) Unauthorized. (From Exception: WebException) Message: The target principal name is incorrect (From Exception: Win32Exception)

• Maybe Tpms.Service can’t log onto Tpms.Agent.
• Restart the machines on which you installed Tpms.Service or Tpms.Agent.
• Change the address of the Tpms.Agent computer from FQDN to hostname or IP address, for example, from:

$srv = New-TpmsObjSetupAgent -Name tpmsagent.ourdomain.local -Port 5050

to:

$srv = New-TpmsObjSetupAgent -Name tpmsagent -Port 5050

If the execution of the Start command generates another error message, such as HTTP Error 400, the request hostname is invalid, then switch back and try again with the FQDN.

• See also the section User permissions.

The remote name could not be resolved

• The stated target machine’s address is possibly wrong.
• Check whether the name resolution works forward as well as reverse – e. g. with:

ping -a <IP address of the target machine>

followed by:

ping <hostname of the target machine>

No connection could be made because the target machine actively refused it

• The stated target machine’s TCP port is possibly wrong.

Service: An exception occurred on the service. An error occurred while trying to retrieve the certificate. (From Exception: CriticalException) No certificate matching the search criteria could be found. (From Exception: KeyNotFoundException)

• Retrieve the certificates from the relevant Tpms.Agent. See script containing Start-TpmsSetupByAgent – from a remote machine with the -Credential parameter, from the local machine without this param­eter.

Service: The remote certificate is invalid according to the validation procedure

• The server certificate from the remote machine issued by ThinPrint CA is missing on the Tpms.Service machine or invalid. See Certificates (Local Computer)→ Personal.
• The ThinPrint CA root certificate of the remote machine couldn’t be found on the Tpms.Service machine. See Certificates (Local Computer)→ Trusted Root Certification Authorities.
• Tpms.Service retrieves both certificates from the Tpms.Agents with running the cmdlet Start-TpmsSet­upByAgent. For this, the program versions of Tpms.Agent and Tpms.Service must match.

Service: 0x80131509. Conflict (From Exception: WebException)

• Tpms.Service can’t access Tpms.Agent because of a certificate conflict.
• See also Service: The remote certificate is invalid according to the validation procedure (above).

Service: Object reference not set to an instance of an object (From Exception: NullReferenceException)

• Maybe the license check by the relevant Tpms.Agent failed.
• In case License Server has just been installed: Restart the license server.
• On the Tpms.Agent machine, check the specified license server address in the Windows Registry in hkey_local_machine\software\ThinPrint\cclucs\LicenseServer. Afterwards restart the TP License and User Configuration Service (formerly Cortado License and User Configuration Service).

Service: The agent was unreachable ... An existing connection was forcibly closed by the remote host (From Exception: SocketException)

• Tpms.Service can access Tpms.Agent, but the Agent didn’t send the relevant certificate.
• See also Service: The remote certificate is invalid according to the validation procedure (above).
• Or Tpms.Agent has stopped working. Check whether the relevant Windows service is running.
• For troubleshooting purpose, stop the relevant Windows service, then run – the same .exe file – Tpms.Agent.exe manually as administrator and check the terminal protocol.

Tpms.Agent as a Windows service disabled

running Tpms.Agent.exe as administrator

Agent: Operation concluded: [State: "Failure", Type: "printer (native)", Name: "\\printserver1.ourdomain.local\MyTestPrinter", Message: "AddPrinter failed.", "The specified port is unknown. (Exception from HRESULT: 0x80070704)"]

• With printer definition possibly a printer port was given which isn’t defined or doesn’t exist.
• Possibly the port name was given using a variable which contains more than the port denomination, e. g. $port instead of $port.name
• See also New-TpmsObjPrinter.

Agent: Operation concluded: [State: "Failure", Type: "server", Name: "printserver1.ourdomain.local", Message: "server "printserver1.ourdomain.local" failed due to unmet dependencies: ["\\printserver1.ourdomain.local\MyTestPrinter"]"]

• See above “... The specified port is unknown ...”

Agent: Non-failure exception occurred. Resuming. Open Printer 2 failed ... The printer name is invalid ...

• Let the Windows service Tpms.Agent run under the account of a domain admin who was not yet logged on to this computer.
• Printers can only be created remotely via PowerShell on this computer after the respective admin has logged on there and opened the Printers folder once.

Agent: An exception occurred while running the set printer routine. Aborting. Set printer intern level 2 failed. (From Exception: CriticalException)

• Tpms.Agent couldn’t set printer properties. Maybe a parameter hasn’t given properly – e. g. the printer driver name using the -Driver parameter.

Agent: Operation concluded: [State: “Failure”, Type: “v-layer connection”, Name: “\\server-hv.ourdomain.local\Lexmark T644@branch02”, Message: “OpenPrinterFailed”

• An Output Gateway printer object (here, Lexmark T644@branch02) and a native printer object couldn’t be united to a V-Layer pair because the native printer object couldn’t be found.
• Check whether there is a syntax error (or a wrong variable is used) with the definition of the native printer using New-TpmsObjPrinter.

Agent: An exception occurred while running the add printer routine. Aborting. AddPrinter failed. (From Exception: CriticalException) The printer driver is unknown. (Exception from HRESULT: 0x80070705) (From Exception: COMException)

• Tpms.Agent couldn’t create the relevant printer.
• Install the relevant printer driver manually.

Agent: An exception occurred while running the add printer routine. Aborting. AddPrinter failed. (From Exception: CriticalException) The printer name is invalid. (Exception from HRESULT: 0x80070709) (From Exception: COMException)

• Tpms.Agent couldn’t create the relevant printer. Maybe a wrong character was used in the printer name – e. g. backslash ( \ ) or comma ( , ).
• Possibly an inappropriate printer driver type is used. On this, see the section Connecting printers to ThinPrint Ports.

example for a v3 or type 3 printer driver

Agent: An exception occurred while running the add printer routine. Aborting. AddPrinter failed. (From Exception: CriticalException) The format of the specified share name is invalid. (Exception from HRESULT: 0x800704BF) (From Exception: COMException)

• A printer can’t be created because the share name or the printer name already exists on the target machine. Choose another share name or rename the already existing one.

Service: The model failed the validation. key: job.SrvModelList[0].PrnModels[0].Shr.Name error: Windows share names are restricted to 32 characters. This share name has 33 characters. exception: (From Exception: ValidationException)
Client: A local exception was caught. StatusCode: 400, ReasonPhrase: 'Bad Request', Version: 1.1

• This Tpms version supports only share names of up to 32 characters. If you need longer share names, please contact our support for a fix: thinprint.com/en/resources-support/support-request

Agent: An exception occurred while running the add printer routine. Aborting. AddPrinter failed. (From Exception: CriticalException) The specified port is unknown. (Exception from HRESULT: 0x80070704) (From Exception: COMException)

• Tpms.Agent couldn’t create the relevant printer port because the spelling of the relevant cmdlet is wrong.

Agent: Failed to fetch the template for the printer. Open Printer 2 failed. ... (From Exception: UnauthorizedAccessException)

• The Tpms.Agent could not access the remote template.
• If the template in question is on a remote server, its name must be specified with FQDN address. Example:

-Template "\\cps48.ourdomain.local\_Tpl_Lexmark T644".

• The service of the Tpms.Agent that creates the printers must run with an account that has the permis­sion to access the share of the template located on a remote computer.

Agent: Operation concluded: [State: "Failure", Type: "SrcTpBase", Name: "seh001:4000::1, Message: "The query for the client printer data failed."]

• Tpms.Agent couldn’t connect to the relevant ThinPrint Client (here, with the hostname seh001 = Thin­Print gateway appliance SEH TPG-65) via TCP port 4000 to retrieve the printer list.
• Check whether the name resolution works forward as well as reverse – e. g. with:

ping -a <IP address of the ThinPrint Client>

followed by:

ping <hostname of the ThinPrint Client>

Agent: State: “Failure”, Type: “SrcTpBase”, Name: “192.168.149.21:4000:88:1”, Message: “The query for the client printer data failed.”

• Tpms.Agent couldn’t connect to the Connection Service (running on 192.168.149.21) via TCP port 4000 to retrieve the printer data from the ThinPrint Client with its Client ID 88.
• Check whether the name resolution works forward as well as reverse – e. g. with:

ping -a <IP address of Connection Service>

followed by:

ping <hostname of Connection Service>

• Check whether the ThinPrint Client is connected to the Connection Service

ThinPrint Client with Client ID 88 connected to the Connection Service (running on 192.168.149.21) with TCP port 4001 

Agent: Operation concluded: [State: “Failure”, Type: “SrcTpBase”, Name: “192.168.149.21:4000:88:1”, Message: “The query for the client printer data failed.”]

• Tpms.Agent could connect to the Connection Service (running on 192.168.149.21) via TCP port 4000 however couldn’t retrieve the printer data from the ThinPrint Client with its Client ID 88.
• Check whether the machine the agent is running on is enabled on the Connection Service.
• Check the firewall settings on both the Tpms.Agent machine and the Connection Service machine.

Client: The server does not contain any sync objects. (From Exception: ValidationException)

• This message can occur when Tpms.Agent couldn’t retrieve printer data from a ThinPrint Client (see above) or from the Connection Service or data couldn’t be read from a file, e. g. a .csv file.

Client: A local exception was caught. No server apply model was provided. (From Exception: PSArgumentException)

• This message can occur as e result of the both messages The query for the client printer data failed or The server does not contain any sync objects (see above).
• Maybe one of the parameters of the cmdlet New-TpmsObjApplyAgent wasn’t given properly.

Sometimes the native driver’s properties aren’t transferred from the relevant Tpms template to the new printers

• This is a known issue of Tpms version 1.0 Beta.
• With the Beta version, use printer objects as templates from the same machine on which the relevant Tpms.Agent is running.
• Perform an update to the Tpms 1.0 release version.

The native driver’s properties are properly transferred from the ThinPrint Client machine or from the relevant Tpms template to the new printers however not the default settings

• This is a known issue of Tpms version 1.0 Beta.
• Perform an update to the Tpms 1.0 release version.

Agent: Operation concluded: [State: "Failure", Type: "port (thinprint)", Name: "\\tpms002.ourdomain.local\ThinPort:", Message: "Generic failure "]

• Maybe Tpms tried to delete a printer port a printer is still assigned to.

Agent: Operation concluded: [State: "Failure", Type: "v-layer connection", Name: "\\tpms002.ourdomain.local\ThinPrint.Tpms.Transport.Models.Printers.PrnTpModel", Message: "OpenPrinterFailed"]

• Maybe one of the parameters of the cmdlet New-TpmsObjVLayerPair wasn’t given properly.

Agent: Operation concluded: [State: "Failure", Type: "port (tcp/ip)", Name: "\\tpms002.ourdomain.local\Lexmark-TPOG:", Message: "Del port data level 1 failed.", "The requested resource is in use. (Exception from HRESULT: 0x800700AA)"]

• The printer port Lexmark-TPOG: couldn’t be deleted.
• Maybe a printer is still connected to this port.
• This message can occur when a V-Layer connection is to be removed but one of the (two) printers has already removed by the same script. This is not critical (= non-failure exception).

ThinPrint Port Manager shows “0” instead of “unlimited” in the Bandwidth column

• This is a know bug of version 1.0 Beta.
• 1.0 Beta: Please use the -BandwidthCtrl parameter to specify a bandwidth value between 1000 and 10,000,000 bit/s (bps). Otherwise the default value will be used (256,000 bps). See also New-TpmsObjTpPortTcp.
• Perform an update to the Tpms 1.0 release version.

ThinPrint Port Manager: bandwidth value “0” instead of “unlimited”

Get-TpmsDriverRepositoryOptions shows:

VersionPreference RepositoryFolder 
UseNewest 1048a1799adc42d5b371c7ae6d2f06b9

• The repository folder has not yet been set.
• Use Set-TpmsDriverRepositoryOptions to define a driver repository.

Import-TpmsDriverArchive: Exception of type 'ThinPrint.Tpms.Transport.Client.RemoteApiException' was thrown. At line:1 char:1 + Import-TpmsDriverArchive -ArchivePath "C:\TPMS\drivers\Universal Printing System ...

• An error occurred while uploading a driver to the repository.
• Check the syntax of the Import-TpmsDriverArchive cmdlet – particularly the path to the ZIP file and the name of the INF file.

You are using several adminstrator accounts but some get the exception: „No connection could be made because the target machine actively refused it 127.0.0.1“

• An error occurre if an administrator executes a script or command
• If you execute the command „Get-TpmsServiceUrl“ then you are getting the output „http://local­host:62091“ and not the correct address of the Tpms service
• Check if you get the correct address of the Tpms service when executing the command „Get-TpmsSer­viceUrl“
• Be sure that every administrator account did execute the command „Set-TpmsServiceUrl“ once.