JSS SCCM Plug-in

chad_lemke
New Contributor

I am trying to install the JSS SCCM Plug-in and the installer says the setup ended prematurely. I go into event viewer and it says:

Windows Installer installed the product. Product Name: JSS SCCM Proxy Service. Product Version: 3.41.0.1. Product Language: 1033. Manufacturer: JAMF Software. Installation success or error status: 1603.
Product: JSS SCCM Proxy Service -- Installation failed.

I am using SCCM 2012 R2 CU4 running on Windows Server 2012 R2, and installing Plug-in version 3.41.0.1. Any suggestions on what is causing this failure? Thanks!

10 REPLIES 10

davidacland
Honored Contributor II

I've had a lot of other problems getting the plugin going in general, mostly around certs and trying to get the other techs to do their bits right!

Never had a problem with the proxy service installation though. Do you have any anti-virus software installed on the server?

chad_lemke
New Contributor

No antivirus software is installed on the server. All the certificates are in place and installed in SCCM. Had 3.4 working before, but it is no longer on the server. It's like someone uninstalled it. I wonder if I should reinstall 3.4, and upgrade to 3.41?

jennifer
Contributor

@chad.lemke What version of the JSS are you running?

I remember we had some issues with the JSS and the plugin having mis-matched versions.

lois_fredrickso
New Contributor
New Contributor

Could the JSS SCCM Plug-In be installed on a Different server? Let's look at the name on the ISV Proxy Certificate. The FQDN on the certificate will tell you exactly what server has the JSS SCCM Plug-In installed on it.

chad_lemke
New Contributor

@jennifer We are on v9.65.

@lois.fredrickson I am sure it was installed on this server. There is a JSS_SCCM_proxy.log file located in C:Program Files (x86)JAMF SoftwareJSS SCCM Proxy Service. The proxy certificate in issued to the computer I am installing the Plug-in on, which is the Primary SCCM Server.

I also tried installing 3.4 again and same results as 3.41 I received.

chad_lemke
New Contributor

This was resolved with help from @lois.fredrickson . It ended up being a permissions issue in the SCCM server. Permissions were not set properly on the certificate it was trying to access in the Crypto folder.

lisamcray
New Contributor II

@lois.fredrickson and @chad.lemke Would you be able to share a bit more detail as to how this was resolved? We are having a similar problem with the installer.

dooley_do
New Contributor

I'd be interested in any more info on this. I have a case open with support but I am trying to use 3.41 and I have installed it on the same box as my JSS (Windows Server 2012). The SCCM certifcate side looks fine but the proxy service errors when it is started, logging the following which looks more like an issue connecting to the JSS itself:

2015-07-09 11:19:47,338 INFO JAMF.JSS.ProxyService.Program - Preparing to run the JSS SCCM Service Proxy service (v3.41.0.1)
2015-07-09 11:19:47,354 INFO JAMF.JSS.ProxyService.JssProxyService - Starting the JSS SCCM Proxy Service
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - Preparing to load settings from the configuration file.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - Verifying configuration file exists.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - The default polling interval is : 30 minute(s).
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - Management Point: XXXXXX.XX.XX
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - Site Code: XXX
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - ISV : f5600eff-493c-4460-8466-e410170c4487
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - Management Point uses HTTPS: True
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - Friendly name of ISV Proxy certificate: SCCM Client Certificate
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - Registration request time out: 1 minute(s).
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - Use Proxy Server Domain when ADStatus is 'Not Bound': True
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - SCCM 2012 Assembly name: JAMF.JSS.ProxyService.Plugins.SCCM2012.dll
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - SCCM 2012 method name: JAMF.JSS.ProxyService.Plugins.SCCM2012.Sccm2012
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.ConfigFile - Save all JSS messages: False
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - Settings for the JSS server: 'https://xxxxxxxx.xx.xx:8443'
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - The username is 'sccm_proxy'.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - The password for the JSS server has been specified.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - The JSS server 'https://xxxxxxxx.xx.xx:8443' was last successfully polled at '01/01/1970 00:00:00' UTC.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - The time offset of the JSS server is '0'.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - Sending computer hardware to SCCM is 'True'.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - Sending computer software to SCCM is 'True'.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - Sending mobile device hardware to SCCM is 'True'.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - Sending mobile device software to SCCM is 'True'.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - Sending personal mobile device software to SCCM is 'True'.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - The default text editor is: notepad.exe
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - Use Domain.NetBios for the FQDN: True
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.Utilities - Loaded settings from the configuration file.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.JssProxyService - Starting the timer thread.
2015-07-09 11:19:47,370 DEBUG JAMF.JSS.ProxyService.JssProxyService - Started the timer thread.
2015-07-09 11:19:47,370 INFO JAMF.JSS.ProxyService.JssProxyService - Started the JSS SCCM Proxy Service
2015-07-09 11:19:52,393 DEBUG JAMF.JSS.ProxyService.JssProxyService - Entering StartCheckingForUpdatedJssDevices()
2015-07-09 11:19:52,393 DEBUG JAMF.JSS.ProxyService.JssProxyService - Starting SendDevicesToTargetSystems()
2015-07-09 11:19:52,393 DEBUG JAMF.JSS.ProxyService.JssProxyService - Starting SendAllUpdatedDevices() for the server https://xxxxxxxx.xx.xx:8443.'
2015-07-09 11:19:52,471 INFO JAMF.JSS.ProxyService.JssProxyService - Checking for all devices in the JSS which have been updated since 0 (01/01/1970 00:00:00).
2015-07-09 11:19:52,471 DEBUG JAMF.JSS.ProxyService.JssProxyService - Starting SendComputerGroup() for the server https://xxxxxxxx.xx.xx:8443.'
2015-07-09 11:19:52,518 ERROR JAMF.JSS.ProxyService.JssProxyService - There was an expected error checking for updates.
System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1. at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.Throw(String res, String arg) at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() at System.Xml.XmlTextReaderImpl.ParseDocumentContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace) at System.Xml.XmlDocument.Load(XmlReader reader) at System.Xml.XmlDocument.LoadXml(String xml) at JAMF.JSS.ProxyService.JssProxyService.SendComputerGroup(JssServer server, String id, String name, Nullable`1 lastUpdatedEpoch) at JAMF.JSS.ProxyService.JssProxyService.SendAllUpdatedDevices(JssServer server) at JAMF.JSS.ProxyService.JssProxyService.SendDevicesToTargetSystems(JssServer[] jssServers, UpdateType updateType, String id, String name) at JAMF.JSS.ProxyService.JssProxyService.StartCheckingForUpdatedJssDevices(Object state)
2015-07-09 11:19:52,518 DEBUG JAMF.JSS.ProxyService.JssProxyService - Finished StartCheckingForUpdatedJssDevices()

davechristensen
New Contributor II

@dooley_do did you find a fix on this? We are also experiencing the same error now, although the plugin had been working fine for the past few months. As always, we're not aware of anything having changed to interfere with the plugin's operation.

lisamcray
New Contributor II

I just spent several weeks working on issues with our JSS SCCM Proxy Plug-in. We are in a domain joined Windows server environment. In this environment, the installer only works if the user account performing the install is that of the person who originally installed the plugin on the server. In our case, the installer fails if run while logged in as any other account (local or domain admin) other than that of the original installer. Our fix was for the person who originally installed the plugin to log into the server with the plugin uninstalled, and delete the RSA Key Container using the command:

aspnet_regiis -pz "JSSProxyServiceKey

After the key had been successfully deleted we logged in to the server with a domain service account with admin rights to the server and completed the install. The problem still exists that only the account that installed the proxy can reinstall the proxy, but now the support team has a shared account that can be used.

The other issue we faced, once 3.41 was installed, was "an unexpected error getting the device info from the JSS!"

67ef0a5680d145249eb2b9dcccc6ec32

I worked with several JAMF engineers over several weeks and tried and numerous troubleshooting steps. In the end the fix was unexpected. We changed the account and the password.

We were using a domain service account with the proxy, say for example username admincasper and a password abc$123. We did some testing with a new local admin account and then in the end created a new service account example username adminproxy and a new password abc_123, and it immediately started working. We were never completely sure what the root cause was, except that potentially the Proxy service had difficulty with unique characters in the password.