We use CentreWare to help us mange our Xerox printers. We are in the process of moving our installation to a new server and are in the process of connecting all the printers. We have several reports configured to collect usage and activing information from the printers and from what I can see they are all SMart eSolution configured.
I'm having problems when I try to Register them. I get errors
Proxy Not Found: [macaddress] [localhost MYDOMAIN\Swood]
The mac address is the CentreWare server mac. We don't use a proxy in our network and I've configured the new server with the same network setting as the old one, not to use a proxy. Is there a way to force CentreWare to ignore the proxy settings?
The new server is running version 5.12.14 and the old server is on 5.2.42.
I have 4 WorkCentre 5875 v1, 1 WorkCentre 5855 v1 and 2 WorkCentre 7845 v1. The Proxy message seems to be coming from the server with CentreWare installed on it. Is it really originating at the printer itself?
I just discovered another clue that may help explain my issue. The CentreWare server's Application log had these events in the Application when trying to register
Proxy Not Found: 06155D099916 System.Web.Services.Protocols.SoapException: Proxy Not Found: 06155D099916
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters)
at Xerox.CWW.CWWLib.edge.ProvisionRequestInterface.registerProxyDeviceV2(String proxyLoginID, PhysicalDeviceInfo physicalDeviceInfo) in c:\XGS-SDI\XOS\Device Management\Version\XDMCWW\5.12\Common\CWWLib\Mainline\Source\Web References\edge\Reference.cs:line 698
at Xerox.CWW.CWWLib.SchedMetering.registerProxyDevice2(PhysicalDeviceInfo physicalDeviceInfo, String strRemoteUserAddress, String strRemoteUserID, String& strTotalMessage, ArrayList& transactions) in c:\XGS-SDI\XOS\Device Management\Version\XDMCWW\5.12\Common\CWWLib\Mainline\Source\SchedMetering.cs:line 5548
Looks to be a web server issue possibly. We're running this on Server 2012 R2.