SSL Error - Token supplied to function is invalid (Full Version)

All Forums >> [ISA Server 2004 General ] >> ISA 2004 SBS



Message


robbosch -> SSL Error - Token supplied to function is invalid (23.May2008 8:08:38 PM)

I have an SBS server running ISA 2004 SP3.  The problem is very odd (I've worked a lot with the ISA 2004 firewall in SBS).  So no SSL web site are working as published via the Internet Connection Wizard.  The wizard generates all the rules and the certificates are generated correctly (verified by comparing to other SBS installs).  Every browse to an SSL site causes the following error in the browser:

Error Code: 500 Internal Server Error. The token supplied to the function is invalid (-2146893048)

The ISA log shows a failed connection.  Browsing to the SSL sites locally is no issue or from the LAN, only on the public side.

The symptoms are classic ones related to certificate issues on the listener but that isn't the case here...even tested by creating my own SSL certs.

I've done a repair on ISA and reinstall of SP3 and still cannot get this to work.

Anyone have any ideas?

Rob




Rotorblade -> RE: SSL Error - Token supplied to function is invalid (25.May2008 5:26:52 PM)

Rob,

Have you researched RSS issue with ISA and Windows SP2? Unable to browse SSL sites is a symptom.

RB





robbosch -> RE: SSL Error - Token supplied to function is invalid (26.May2008 12:01:49 PM)

I ended up disabling ISA on this machine for now until I can figure out the problem (using the old RRAS basic firewall ).  It could be the RSS issue but the install is the same that we have used on about 50 other SBS machines without issue.  I also had ISA working at one point on this machine. 

I completely uninstalled ISA, verified everything works with the RRAS basic firewall, did a clean install of ISA, applied SP3, and still got the same error.  The issue appears to be with ISA since the web sites work fine internally and with the basic firewall.

This is the oddest ISA issue I've seen.  I'm tempted to just leave it as is and do a swing migration to a new install at some point. 

Rob




Page: [1]