Cannot submit machines to the JSS... HELP!

Hey Andy,

We've been seeing this 401 error recently and it usually points towards a corrupted JAMF.keychain and usually is in conjunction with enabling "Certificate-Based-Communication" in the JSS.

On the client machine, we could try removing the JAMF.keychain in Library/Application/Support/JAMF and then running "sudo jamf enroll -prompt" in terminal.

Good luck,
-Jason

Thanks Jason, I will try that.

Here is what I see after a reboot:

Locating Receipts...
Finding Extension Attributes...
Submitting data to https://pegasus.butler.edu:8443//...
There was an error submitting the computer to the JSS. Here is what the JSS reported back:



<?xml version="1.0" encoding="UTF-8"?>
<jamfServlet version="8.4" server="Apache Tomcat/7.0.12">
<institution>Butler University</institution>
<epoch>1329325682</epoch>

        <response>Bad username or password</response>

<sessionLastError></sessionLastError>
</jamfServlet>

Nope, still get the 401 error after deleting the keychain and doing a 'jamf enroll -prompt'. Getting ready to call support.

Andy,

Could we try disabling the collection of fonts/plugins in Inventory Collection preferences and try running Recon again? If all else fails, please feel free to contact our support.

Thanks a lot,
-Jason

Jason:

That was the first thing that support had me check as well (I already contacted them). We are not collecting fonts.

I just sent them a log file; we are seeing the following repeated endlessly in the JAMFSoftwareServer.log:

2012-02-15 13:32:36,699 [ERROR] [JamfEncryptionUtils      ] - Unable to verify signature for computer: 24

The computer numbers change regularly. Basically, it's throwing this error for every machine in the database. Not sure whether this is related to the 401 error. We have also had several blank computer records show up in the database, probably resulting from the failed recon/quickadd runs. I promptly deleted them.

Any help appreciated, although hopefully support will get a handle on this quickly.

--Andy

OK, we resolved the issue temporarily by disabling certificate-based communication in Settings-->Computer Management Framework Settings-->Security.

Not an ideal fix, but at least it will let us enroll computers. I will post details of the final fix once it's in :)

I'm not at the office to verify, but I think this is the same error I was seeing on a few freshl imaged machines. Machine would image fine, but I couldn't push any policies and a recon would fail with a bunch of HTML that when opened would give a 401 error I believe.

I was able to work around the error by running a QuickAdd package against the machine. I haven't had time to bring this up to support.

Steve

I am having the same issue as well. This started for me a couple weeks ago when I tried to enroll a machine that has been built for a while. I was getting the 401 error. I eventually gave up. I had successfully enrolled a different machine since then, so I was thinking that the issue was resolved. However, I tried to enroll one again today and came across the 401 error and it WILL not enroll. I tried it several times with the quickadd package as well as creating a new one. I also tried running the network tool in Recon and enrolling it that way. Everything I tried resulted in a blank record being input in the JSS and the postflight script error 401. (Support also had me try the disable fonts fix, but they were not enabled) Hopefully we'll have something figured out soon.

Hi, I've been having the exact same error as krischelj with some my Macs.

<?xml version="1.0" encoding="UTF-8"?>
<jamfServlet version="8.4" server="Apache Tomcat/7.0.12">
<institution>MimeCast</institution>
<epoch>1330515356</epoch>

<response>Bad username or password</response>

<sessionLastError></sessionLastError>
</jamfServlet>

Same error here, top message is with "Enable Certificate-Based Communication"

ls-mac-99:~ mis$ sudo jamf recon
Password:
Retrieving Inventory Preferences from https://jss.company.com:8443/...
Locating Hard Drive Information...
Locating Hardware Information (Mac OS X 10.7.3)...
Locating Applications...
Locating Receipts...
Finding Extension Attributes...
Locating Mobile Device records...
Submitting data to https://jss.company.com:8443/...
There was an error submitting the computer to the JSS. Here is what the JSS reported back:

<html><head><title>Apache Tomcat/7.0.12 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 401 - </h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>This request requires HTTP authentication ().</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.12</h3></body></html>

This is with "Enable Certificate-Based Communication" unticked;

ls-mac-99:~ mis$ sudo jamf recon
Retrieving Inventory Preferences from https://jss.company.com:8443/...
Locating Hard Drive Information...
Locating Hardware Information (Mac OS X 10.7.3)...
Locating Applications...
Locating Receipts...
Finding Extension Attributes...
Locating Mobile Device records...
Submitting data to https://jss.company.com:8443/...
<computer_id>11</computer_id>

Issue has been resolved on my JSS. Along with disabling Fonts and Plug-ins, I had to uncheck the box for " Include sizes, copyright information, modification dates, bundle IDs and permissions when gathering applications " under the Applicaiton Collection area. Once I did this, I retested and the machines that would not collect are now collecting.

I had this same issue when using the 'sudo jamf recon' terminal command on a re-imaged computer. Turns out I needed to (a) delete the computer from the JSS Inventory and (b) run Recon.app. If you go this scorched-earth avenue make sure you put your computer back in any groups it may need so Managed Prefs work.

We just had this issue and it seems if the date and time sync are turned off on the client this can also result in a 401 error.