Error: unexpected status code 200

DirkNijs asked a question.

December 11, 2018 at 8:00 AM

Hi all, we are deploying a Linux agent 5.2.0 on a RHEL 5.8. With most servers it goes well. But in few servers we got the error: " Cannot send to server. Server replied with unexpected status code 200 " after a manual scan and send. We checked most things so far: connection to the INV server on http and https works, certificates are ok and reachable, networking seems to be ok, no proxies are in place, ... But I have no glue anymore why the agent is not able to send his data ? Handshake is ok... look into the screenshot. Anybody an idea in what direction I have to look?

Portal User
8 years ago
Hi Dirk, Intersting, normally the code 200 means that everything is working as it should. If you browse to the inventory server from this computer with the full URL stated in the log ( https://myinvenotyrserver.com:443/api/receiver/receive ) you should get an error message 405 (method not allowed) Is that what you are getting, or do you have some other message? How large are the snowpack files generated by these servers? Larger than usual? Maybe they are so big they time out during transfer. Also, on the inventory server side there are some logs that might tell you more. The log for inventory server can be found here: C:\ProgramData\SnowSoftware\Inventory\Server. If you try another scan from the server and remember what time you did it, see if there are any error messages in the inventory server log that corresponds to the send attempt.
Expand Post
DirkNijs
8 years ago
Hi all, finally, we discovered the reason why we got the error 200. It took us a lot of time but we learned a lesson: First we found out, deleting the snowpacks in the agent solved the problem. And for most systems this seems to be the solution because the first scan creates a larger package... For one system, the problem was not solved. After deleting the snowpacks, scan and send it seems ok, but after an hour the error 200 was there again. You can say in general, the snowpacks were too big, as mantioned by Martin Christersson! I wrote more information in a new post which you can find here .
Expand Post
- Portal User
  8 years ago
  That's a really helpful post Dirk! Glad to hear that you solved it in the end!
  Expand Post
Siegfried Gammay (Flexera Software)
8 years ago
Hi Dirk, is TLS 1.2 installed and active on the RHEL 5.8 system? If you want to use https connections the snowagent need TLS 1.2 for establishing a session to the INV server. /Siggi
Expand Post
DirkNijs
8 years ago
Hi all, thanks for your idea's. So far, none of the solutions was helpfull. As soon I have a solution, I'll post it here. Thanks and have a great day! Just logged a case to SNOW support. I hope somebody there has an answer.
Expand Post
DirkNijs
4 years ago
Hi all,
Another thing I found out, is: for some weird reason, the config file is changed! In the server config part, a space or carriage return was added and causing the same problem. By removing these empty spaces, the problem was solved.
Kind regards, Dirk
Expand Post

Related Product Forums

→ Flexera One

→ Snow Atlas

→ FlexNet Manager

→ Snow License Manager

→ App Broker

Need help finding an answer?

Ask a Question →

Error: unexpected status code 200