SAP2000 V18 "Port 80/443 not responding" message

[Alex Machado]

Good Morning, fellas!

I just got admited in a new company where they use SAP2000 version 18. It just happen whenever i try to use the Standalonekey renewer it gives me this error. Both ports are open now in the router and firewalls. Anyone can help me with this?

 

[JoshPlumSE]

Alex -

This sounds vaguely familiar to a RISA issue that we dealt with a couple of years ago. I'll share it with you as a possible issue since it was related to a similar stand alone key. That being said, I no longer work for RISA and I don't have access to my e-mail archives. So, this is coming purely out of my not-so-perfect memory.

There was a case where the computer was expecting to have a supplemental drive plugged into it. This caused issues with the Sentinel key for some bizarre reason. We had to go into the computer settings and specifically tell the computer not to expect that supplemental drive to be there.

It wasn't really a RISA issue, but more of a computer issue that caused some odd problems with the software / drivers that were trying to read the Sentinel USB key.

I genuinely don't know if this is your issue. But, it sounds similar enough to what we experienced that I thought I should mention it.

 

[Alex Machado]

I did "solved" using an external network. But now im stuck with another error. Locking code one, ask for a 2010 but the one in the server is 2000.

 

[JoshPlumSE]

That's tricky.... You'll have to discuss this with CSI tech support. I can give you some insight into the issue (based on my experience at RISA), but I can't guarantee it will be the same. The locking code is generally information on the server that the license file needs to ensure the identity of the server. This is needed because the identity of the server needs to be unique (or close to it) to protect their licensing.

Now, different versions of the Sentinel licensing routine work off of different locking codes. If your Sentinel RMS License service running on the server is "generation A" then it cannot read or understand locking codes from "generation B" (though the B service would understand generation A locking codes). You need to make sure that you have the correct utilities to generate the locking codes that the CSI guys need.

Another problem may be that Generation B of the Sentinel RMS service may not be compatible with Server 2000, which is pretty old now.

Lot's of frustrations for both users and program support on these types of things. With Windows and Sentinel constantly changing an updating their security settings, this stuff changes much more frequently than I would have liked.