Skip navigation
All Places > Knowledge Base & Downloads > Blog > Authors Lindsay Lamb
1 2 3 Previous Next

Knowledge Base & Downloads

43 Posts authored by: Lindsay Lamb

In the event that the Pharos Database Service fails to start (hangs and times out), confirm the settings within "Sql Server Configuration Manager".

 

This scenario has been found to occur when customers are migrating their database, or bringing up a new SQL server- though it has yet to be determined exactly why these settings become misconfigured.

 

1) Open "SQL Server Configuration Manager" window, expand "SQL Server Network Configuration".

2) Click to highlight "Protocols for MYSQLSERVER". Confirm that TCP/IP's status is set to Enabled.

 

Image

 

3) Right click "TCP/IP" and choose Properties -> IP Addresses tab.

 

Ensure that the TCP Port field for each IP is configured for port 1433.
Ensure that the Active field for each IP is set to Yes, and the respective IP Address for each IP is configured properly. IP1 = IPv6, IP2 = IPv4, IP3 = IPv6 loopback, IP5 = IPv4 loopback. These IP address should be that of the server which hosts the sql server.

 

Image

 

4) The Pharos Database Server service should now be able to start without issue.

Environment
  • Pharos Systems MobilePrint 2.0
  • Canon imageRUNNER multifunction device
  • Canon imageRUNNER Advanced multifunction device
  • Pharos Systems Print Center
  • Pharos Systems iMFP for Canon
  • Microsoft Windows 2008 R2 Server
  • Microsoft Windows 2008 Server
  • Microsoft Windows 2012 R2 Server
  • Microsoft Windows 2012 Server

Symptoms
  • Jobs do not print with expected attributes.
  • Single sided jobs print double sided.
  • Double sided jobs print single sided.
  • Black and white jobs print in color.
  • Color jobs print in black and white.

Cause
While Pharos Systems MobilePrint allows users to change the finishing options of jobs that have already been rendered by the print driver (plex mode, number of copies, color mode, and number of pages per sheet), some driver manufacturers have chosen to use proprietary (non-standard) attributes instead. By manipulating the printer driver configuration and managing the defaults for the user account running the MobilePrint Worker service, much of this can be resolved.

Resolution
 
1. Log into the server using the account that runs the MobilePrint Worker service.
2. Go into Properties for the queue utilizing the Canon imageRUNNER-ADV 5045 PCL6 driver.
3. On the General tab, click the "Preferences" tab. Configure preferences here for SINGLE-SIDED finishing and COLOR mode. Click OK and APPLY this change.
4. Go to the Advanced tab. Uncheck the "Enable Advanced Printing Features" option. APPLY this change.
5. While on the Advanced tab, click the "Printing Defaults" button. Configure preferences here for SINGLE-SIDED finishing and COLOR mode. Click OK and APPLY this change.

 

Once this has been done, launch the MobilePrint Administrator web page and ensure that the Canon devices is using the iR-ADV PCL driver and that the "Black and White Conversion" is being handled by the Printer.

Symptoms:

  • Windows service does not start.
  • ERROR: "Error 1502. The service did not respond to the start or control request in a timely fashion" when starting a Windows service.
  • The "Pharos iMFP Management Console" does not launch.
  • ERROR: "The Pharos iMFP Management Console has stopped working."


Environment:

  • Pharos iMFP for Konica-Minolta v1.2.x
  • Pharos iMFP for Konica-Minolta v1.3.x
  • Pharos iMFP for Konica-Minolta v1.4.2
  • Microsoft Windows 2008 Server
  • Microsoft Windows 2008R2 Server
  • Microsoft Windows 2012 Server
  • Microsoft Windows 2012R2 Server

 

Cause:

The "Pharos iMFP for Konica-Minolta" service requires that Microsoft .NET 2.0 components be installed on the host server.


Resolution:

  1. Install the Microsoft .NET 2.0 components on the host server:
  2. Launch Server Manager.
  3. Click the "Add Roles" link.
  4. Put a checkbox in the "Application Server" option.
  5. In the dependency dialog box that appears, click the "Add required features" button to install .NET Framework 3.5.1 features.
  6. Select any additional Role Services that may be required for the server. Click "Next."
  7. Continue through any additional screens until you come to the "Install" step. Click the "Install" button.
  8. Restart the server as required.

How can the SQL connection's server instance, username and / or password be updated for Pharos Systems SiteMonitor?

 

This procedure utilizes the SiteMonitor installation utility (SiteMonitor.msi) to generate a new configuration file.  It will be necessary to locate the correct Blueprint Enterprise installation package that matches the version that is installed.

  1. On the Analyst server, navigate to the X:\Program Files (x86)\PharosSystems\SiteMonitor\Service folder, where X is the drive letter onto which Blueprint Enterprise was installed.  If the OS is 32-bit, navigate to the X:\Program Files\PharosSystems\SiteMonitor\Service folder
  2. Move the PharosSystems.SiteMonitor.Service.exe.config file out of this folder and place it on the desktop temporarily.
  3. Launch the SiteMonitor.msi installer from the Blueprint installation package.
  4. Click the Next button.
  5. Choose the Repair option.
  6. Within the Site Monitor Setup window that appears, enter the correct SQL server instance, username and password for the SiteMonitor database.
  7. Click the Next button.
  8. Cick the Repair button.
  9. Click the Finish button when completed.
  10. Launch the Pharos Systems Site Monitor Administrator to verify that the service is online and operational.

Environment:

  • Pharos Systems Blueprint Enterprise v5.1
  • Microsoft Windows Server - Cluster Services


Symptom:

  • An invalid Windows Registry key is defined for the creation of the Pharos Systems Secure Release Service generic service for a Microsoft Windows clustered server implementation. This error will cause Secure Release Here job lists to fail at the terminal.


Resolution:

Please use the attached update to the "Blueprint Installation Guide" that comes with the product software download. This update corrects a Windows Registry key error for the Pharos Systems Secure Release Service generic service configuration.

Environment:

  • Pharos iMFP for HP version 4.x (HP FutureSmart)


Symptoms:

  • Install appears to be successful, but after restarting the Pharos application does not run.
  • Uninstalling and reinstalling does nothing to solve the problem.
  • This only happens on some devices, not on most.


Cause:

There is a pre boot menu option called "Skip Disk Load". The option exists right next to "Cold Reset" which is one of the more frequently used options. We have seen folks turning this "Skip Disk Load" feature On by accident while trying to do Cold reset.  If this is option is checked, then Device will not load anything from Disk. The solution loads fine on Disk, but Device behaves as if it doesn't exist. Since it is a sticky setting, multiple reboots and reloading of SW would not have any affect.

Resolution:

Change "Skip Disk Load" to off and then restart the device.

Note: Access to the boot menu should be done by individuals familiar with the HP hardware.

Magtek card reader is connected to supported Xerox iMFP device, however card swipe events are no detected, i.e. nothing is happening after a card swipe.

 

#1. Xerox devices MUST see sentinels in card data obtained from a Magtek card reader.  If the data read from the card does not have sentinels, the Xerox device will completely ignore the card swipe.  Your card readers were configured so that sentinels were disabled, therefore the Xerox was ignoring the card swipe.

 

To re-enable to sentinels, execute the following command to the card reader using the Magtek USBMSR Demo program:

     01 04 63     <send msg>    (This restores the default state to sentinel data flags)
     02     <send msg>

 

If you then swipe a card, the returned data should look something like this:
     ;6008962500504550=99121200000000000000?

 

Note that the ; character the the starting sentinel for Track 2 data.  The ? is the ending sentinel.

 

 

#2. Some older Xerox devices do not like card swipes that contain only Track 2 data.  This will create a situation in which the 1st card swipe will work but then subsequent card swipes will be ignored.  To resolve this issue, reconfigure the card reader to send the Track 1 sentinel of % for the Track 2 data.  This will trick the Xerox into believing that the data is Track 1, thusly allowing each card swipe to behave normally.

 

To change the Track 2 sentinel, execute the following command to the card reader using the Magtek USBMSR Demo program:
     01 15 25     <send msg>        (This sets the Track 2 sentinel to the % character)
     02     <send msg>

 

If you then swipe a card, the returned data should now look something like this:
     %6008962500504550=99121200000000000000?

 

Note that the % character is now the starting sentinel for Track 2 data.  This will trick the Xerox into thinking the data is Track 1.  The ? is the ending sentinel.

Pharos SignUp Client logging on a Windows 7 SignUp Client it fails to log.

 

"Knowlege Base article #626,  Pharos Logsetter Utility says I can't use the log setter to turn on logging for the SignUp Client so I need to know how to get a SignUp Client Log."


Uniprint 8.1

There is currently an issue with logging the signup client as it does not produce a Signup Client log but will produce 2 other logs those being the UILog and the CPLog

 

The issue seems to be with the logsetter tool and how logging is done on Vista and Windows 7 machines.

 

Included is a tool that can be used called "remotetracer" (see attachment)

 

1. What you need to do is get this exe on a machine somewhere.  The server is probably a good choice, since it will need to run uninterrupted for a while.  On the server, run it from the command prompt.  It may tell you it needs additional configuration to work properly (i.e. adding a pipe name to the registry).  Update the registry if needed and exit the program, and run it again like this:

 

remotetracer > clientlog.txt

 

2. Now on the SignUp client to be logged, browse to HKLM\Software\Pharos\SignUp Client\Log and add a new REG_SZ value called "PipeName".  Set this value to "\\server\pipe\remotetracerpipe".  The other values should be as you would typically set for file logging (level 5, options 31, types 15, etc... if in doubt, use the logsetter and make sure all checkboxes are enabled, then add the PipeName afterward).  After this, reboot the client and when it restarts you should see clientlog.txt on the server begin to increase in size.

 

While this is going on, make sure we are still writing the CP, UI, and SUServer logs.

 

There are two additional keys for client logging on Vista/W7, for logging different components.These are for the Credential Provider (CP Log) and Client UI (UI Log) components. Instead of a 'Log' subkey (HKLM\Software\Pharos\SignUp Client\Log), you create one called CP Log (HKLM\Software\Pharos\SignUp Client\CP Log) and one called UI Log (HKLM\Software\Pharos\SignUp Client\UI Log).

 

The UI component is basically just the clock icon and popup messages, so logging that is not too interesting. If you do decide to log the UI component, that process runs as the user and so requires a log location the user can write to. The other one (CP Log) logs little more than function traces, but logs with system privileges.

 

The two new subkeys use the same format as the original Log key, so the easiest thing to do is set logs using the logsetter, then export that subkey (HKLM\Software\Pharos\SignUp Client\CP Log) and modify it to create the same values under the new names.

 

This should get you logs of the SignUp Client.



Uniprint 8.2 and later


There are 3 specific registry keys used to enable detailed logging on a Uniprint Signup client.  The attached zip file (SignUp Client Logging Registry Keys.zip) will create 3 files.

1. The Signup Client log
This log contains information on the client and its communications to the server.

2. The Signup CP Log
This log contains information on some of the underlying components of the client provider mechanism.

3. The Signup UI log
This log contains information on the User Interface of the client.

These 3 log files will be created in the directory "c:\windows\temp\pharoslogs".


This directory must be manualy created on the client machine.  If you are using a PC State software such as Deepfreeze or Clean Slate then the registry keys may need to be modified to point to a folder in the "Safe Space" of the client system so they do not get deleted when the client machine reboots and the PC is reverted back to a "clean state".

The 3 log file names will be:
1. signupclient-log.txt
2. signupCP-log.txt
3. signupUI-log.txt

After applying the registry keys you will need to restart the client PC.

To delete all the logs files created and start with a new set you will need to stop the "Pharos SignUp Client" Windows service, delete the files and then restart the service.

There are two folders in the zip file, one for 32-bit clients, and another for 64-bit clients.

There are 2 independent Uniprint environments, i.e. 2 different principal servers and databases.  Most users are confined to either one, but there is a subset of users who want to interact with both environments.  However, the printers from one package are overwritten or removed by the other package.  Is this scenario possible?

 

Overview

The printers from one package are overwritten or removed by the other package because there is a conflict in the SpoolQueueId collected from the Windows Registry.

 

Technical

The same "SpoolQueueId" in the "LocalPrinters" key under the "Popup Client" registry.  Notice the value of "SpoolQueueId" was set with the [module_id] for the printer module in a package.  The [module_id] is unique within an environment, but it's incremental.  So, it's possible for the [module_id] to overlap between independent Uniprint environments.  This value must be randomized so that the packages can coexist.

 

The [module_id] of a queue is stored in the [modules] table.  It's created by a trigger after the queue is added to the database.  The column is an 'identity' data type.  The 'Identity seed' of the queue must be changed so that the seed depends upon a unique value in each environment, such as the Site Code.

 

Resolution

In this example, use the Site Code as the unique value in each environment.  The Site Code includes 2 digits at the end.  The SQL script below collects the last 2 digits from the Site Code, which is derived from the License Key stored in the database.  This is represented as @licensekey in the SQL script.  Then, @seed is generated randomly using @licensekey as a salt.

 

-- Script Start --

use pharos

declare @seed int
declare @licensekey nvarchar(255)

select @licensekey=license_quick_key from system
select @licensekey=right(@licensekey,2)
select @seed = 0

begin try
&#160;&#160;select @seed = 2000 * convert(int, @licensekey)
end try
begin catch
end catch

select @seed = 1000+@seed
DBCC CHECKIDENT (modules, RESEED, @seed)
go


-- Script End --

Run the SQL script (above) on the Pharos database in each of the independent Uniprint environments.  The SQL script creates a new random next incremental value for [module_id] on each of the Pharos databases.  New queues and packages will now receive a unique [module_id] and "SpoolQueueId".  However, this will not affect existing ones.

 

It's often easier to rebuild the queues and packages for one of the independent Uniprint environments.  If this is not a feasible option, then there are several options for how to handle existing queues and packages that have already been deployed.

 

The "SpoolQueueId" is based upon [module_id], as described above.  The client packages only use the "SpoolQueueId" when installing or upgrading itself in order to decide whethere to delete an existing printer (queue).


Option 1:

 

1.  Install package A
2.  Run a customized REG file that changes the Windows Registry key named "SpoolQueueId" for each print queue installed under HKLM\SOFTWARE\Pharos\Popup Client\LocalPrinters. This is accomplished using a custom action incorporated with the package
3.  Install package B

 

Option 2:

 

1.  Run the database update script on one of the Pharos databases
2.  Build new queues on one of the Pharos databases
3.  Build a new package C that includes the new queues
4.  Install package A
5.  Install package C instead of B

 

Disadvantage: More setup and additional queues on one of the Pharos databases.

 

Option 3:

 

1.  Run the database update script on one of the Pharos databases
2.  Update the existing queues' [module_id] on one of the Pharos databases, which includes 3 tables: [modules], [module_os], and [package_modules]
3.  Rebuild the existing package from the updated database (above)
4.  Install package A
5.  Install package B

 

Disadvantage: Could cause duplicate printers for those who have the package with the original unmodified [module_id].

How do I configure the MobilePrint listening port?  Also, can I use a certificate with a common name (CN) that is different than the hostname of the MobilePrint server?

 

1. First, shutdown the MobilePrint services. There are 5 services. Here is a common shutdown order:

  • Pharos Systems MobilePrint Website Service
  • Pharos Systems MobilePrint Authenticator Service
  • Pharos Systems MobilePrint Worker Service
  • Pharos Systems MobilePrint Workflow Service
  • Pharos Systems MobilePrint Configurator Service

 

2. Next, locate the 2 MobilePrint configuration files named "LocalServer.config.xml" and "MobilePrint.Configurator.config.xml". Here are their default locations:

  • C:\Program Files (x86)\PharosSystems\MobilePrint\LocalServer.config.xml
  • C:\ProgramData\PharosSystems\MobilePrint\MobilePrint.Configurator.config.xml

 

3. To change the default port number 9001 to 443, edit both configuration files and replace 9001 with 443.

 

Example 1: LocalServer.config.xml


<BootstrappingConfiguration>
<Port>443</Port>
<AppDataLocation>C:\ProgramData\PharosSystems\MobilePrint\</AppDataLocation>
<Configurators json:Array="true" xmlns:json="http://james.newtonking.com/projects/json"> 
<Name>MY MOBILEPRINT SERVER HOSTNAME</Name> 
<Port>443</Port> 
<Zone>Global</Zone>
</Configurators>
</BootstrappingConfiguration>



Example 2: MobilePrint.Configurator.config.xml


<ServerConfiguration>
  <Port>443</Port>
  <PrintServers json:Array="true" xmlns:json="http://james.newtonking.com/projects/json">
    <Name>DO NOT CHANGE PRINT SERVER HOSTNAME</Name>
    <Port>808</Port>
  </PrintServers>
  <Workflows json:Array="true" xmlns:json="http://james.newtonking.com/projects/json">
    <Name>MY MOBILEPRINT SERVER HOSTNAME</Name>
    <Port>443</Port>
  </Workflows>
  <Workers json:Array="true" xmlns:json="http://james.newtonking.com/projects/json">
    <Name>MY MOBILEPRINT SERVER HOSTNAME</Name>
    <Port>443</Port>
  </Workers>
<Configurators json:Array="true" xmlns:json="http://james.newtonking.com/projects/json">
    <Name>MY MOBILEPRINT SERVER HOSTNAME</Name>
    <Port>443</Port>
  </Configurators>
  <Authenticators json:Array="true" xmlns:json="http://james.newtonking.com/projects/json">
    <Name>MY MOBILEPRINT SERVER HOSTNAME</Name>
    <Port>443</Port>
  </Authenticators>
  <Websites json:Array="true" xmlns:json="http://james.newtonking.com/projects/json">
    <Name>MY MOBILEPRINT SERVER HOSTNAME</Name>
    <Port>443</Port>
  </Websites>
</ServerConfiguration>




4. To change the MobilePrint certificate, edit the configuration file named "LocalServer.config.xml"

 

5. MobilePrint uses the certificate configured as <SslThumbprint>MY CERTIFICATE THUMBPRINT</SslThumbprint> where MY CERTIFICATE THUMBPRINT is the hexadecimal thumbprint of a certificate in the Windows Certificate Manager (certmgr.mmc) on the MobilePrint server.

 

<SslOverrideConfiguration>
  <RequireTrustedCertificates>false</RequireTrustedCertificates>
  <SslThumbprint>MY CERTIFICATE THUMBPRINT</SslThumbprint>
</SslOverrideConfiguration>


 

6. In addition, the certificate's common name (CN) should match the hostname configured as <Name>MY MOBILEPRINT SERVER HOSTNAME</Name> in both "LocalServer.config.xml" and "MobilePrint.Configurator.config.xml"

  • See Example 1 and 2 above.
  • The issuer or central authority (CA) who issued (signed) the CN certificate must be stored in the Windows Certificate Manager (certmgr.mmc) as a trusted or root certification authority.

 

7. Now, start the MobilePrint services. Here is a common start order:

  • Pharos Systems MobilePrint Configurator Service
  • Pharos Systems MobilePrint Workflow Service
  • Pharos Systems MobilePrint Worker Service
  • Pharos Systems MobilePrint Authenticator Service
  • Pharos Systems MobilePrint Website Service

Symptoms:

  • iMFP for Xerox fails to successfully manage a Xerox device.
  • The management console shows success (device status is Managed) but the blocking screen on the Xerox device does not show the expected screen with the key.
  • It may show a soft keyboard and request authentication.
  • Attempting authentication may result in a DNS error message.

 

Environment:

  • iMFP for Xerox version 2.5 or higher (software only solution)
  • Xerox device with McAfee enabled

 

Cause:

With the McAfee feature enabled on some Xerox devices some of the configuration performed by the iMFP for Xerox management console appears to be blocked. As a result the installation and configuration is incomplete resulting in the symptom above.

 

Resolution:

Disable the McAfee protection on the Xerox device. This is performed from the web interface of the device, Properties tab in the Security section. This will require a reboot of the device. After the device reboots use the Management Console remove the Pharos and then reinstall the Pharos solution. At this point the installation should succeed and the expected blocking screen will be displayed.

 

  NOTE: Pharos is working with Xerox to understand this further. A software update may be made available in the future to address this. On some devices with McAfee enabled our installation process works fine. We do not yet understand fully what is causing this. We have observed that McAfee can be successfully re-enabled after Pharos installation and the engine runs successfully.

Goal:

  • Create customized Pharos Popup for Mac package.


Environment:

  • Pharos Uniprint Suite 8.3
  • Pharos Uniprint Suite 8.4
  • Apple MacOS 10.6
  • Apple MacOS 10.7
  • Apple MacOS 10.8
  • Apple MacOS 10.9

 

Resolution

As in previous versions of the Mac package, our most current offering allows for customization of the package for mass deployment.  This will allow users to install shared Pharos Uniprint Print Server queues at the same time that the Popup and Notify client are installed.

 

Please download the "TechNote Automatic Popup and Print Queue Configuration for Mac OS X" attached for those instructions. The Pharos Uniprint 8.3/8.4 MacOS X base package must be downloaded separately.

Goal:

  • Understand the current supported product list for Microsoft Windows Server 2012 R1 and R2.

 

Resolution

The following products include support for Microsoft Windows 2012 Server

 

Windows Server 2012 R1

Uniprint 8.3 Service Pack 1 (SP1) and earlier

  • Not Supported

 

Uniprint 8.4 and 9.0 General Release

  • Pharos Administrator
  • Pharos Remote
  • Pharos Reports
  • Principal Server (Database, License, etc.)
  • Print Server (LPD, Popup, Secure Release, etc.)
  • SignUp Server

 

Blueprint 5.0 and earlier

  • Not Supported

Blueprint 5.1 General Release

  • Analyst
  • Blueprint Administrator
  • Collector
  • Tracker
  • Site Monitor
    • Site Monitor Database: Supported
    • Site Monitor Service: Supported
    • Site Monitor Administrator: Not Supported

 

MobilePrint 1.3.1 and earlier

  • Not Supported

 

MobilePrint 1.3.2 and 2.0

  • Authenticator
  • Configurator
  • Website
  • Worker
  • Workflow

 

Windows Server 2012 R2

Uniprint 8.3 Service Pack 1 (SP1) and earlier

  • Not Supported

 

Uniprint 8.4 and 9.0 General Release

  • Pharos Administrator
  • Pharos Remote
  • Pharos Reports
  • Principal Server (Database, License, etc.)
  • Print Server (LPD, Popup, Secure Release, etc.)
  • SignUp Server

 

Blueprint 5.1

  • In Controlled Release - link to software available upon request

 

 

Blueprint 5.0 and earlier

  • Not supported 

 

MobilePrint 1.3.2 and earlier

  • Not Supported

 

MobilePrint 2.0

  • Authenticator
  • Configurator
  • Website
  • Worker
  • Workflow

Goal:

  • Configure Pharos MobilePrint to use Office 365 as its email server.

Environment:

  • Pharos MobilePrint 1.3.2 and 2.0
  • Microsoft Office 365

 

 

 

Resolution:

To configure Pharos MobilePrint for Microsoft Office 365 Mail Server, perform the following steps.

1. Obtain your Office 365 email settings


a. Sign in to your account using Outlook Web App. For help signing in, see Sign in to Outlook Web App (NOTE: this is a link to Microsoft.com)


b. In Outlook Web App, on the toolbar, click Settings (the Gear icon) > Options > Account > My account > Settings for POP and IMAP access.


c. The POP3, IMAP4, and SMTP server name and other settings you may need to enter are listed on the Settings for POP and IMAP Access page under POP setting or IMAP setting, and SMTP setting.


An example of the dialog box presented is shown below:


Office 365 mail settings


2. Configure MobilePrint

a. Launch the MobilePrint Administrator web page (https://<MobilePrint Server's hostname>:9001/admin/settings.html) and log in.


b. Go to the
Email Server Connection menu item.


c. Modify the IMAP and SMTP Account sections to reflect those found in the Office 365 configuration (step 1). An example is shown below. Please note that the Port, Username, and Password fields will be different.


MobilePrint email configuration


d. Save the configuration and test.

Symptoms:

  • ERROR: "Service cannot be started. System.TypeInitializationException: The type initializer for '<Module>' threw an exception. ---> System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
  • Pharos Systems Secure Release Service fails to start
  • User cannot print (Secure Release or Direct)

Environment:

  • Uniprint 8.3 (any build)
  • Microsoft Windows Server
  • Microsoft .NET 4.5


Cause:

It has been found that the installation of Microsoft .NET 4.5 on a server running any build of Uniprint 8.3 (including Service Pack 1) will cause the Secure Release Service (SRS) to stop working due to an incompatibility between a component of SRS and a module installed with .NET 4.5. This can happen during Windows Update with the application of Microsoft patch KB2858725.


Resolution:

Please read below to determine what to do depending on the Uniprint server's current state:


Microsoft .NET 4.5 Is NOT Installed

Action: Do NOT install Microsoft .NET 4.5. You will be notified via the Pharos Communities site when it will be safe to install this version of .NET (this will be accompanied by an update to Uniprint).


Microsoft .NET 4.5 IS Installed

Action: Uninstall Microsoft .NET 4.5 and then reinstall Microsoft .NET 4.0. This will restore .NET 4.0 functionality. You will be notified via the Pharos Communities site when it will be safe to install this version of .NET (this will be accompanied by an update to Uniprint).