After several months of silently just doing its job our Select Server Gateway has decided that life in not good anymore. This is running on a Windows 2003 R2 x64 server with very few other applications on it (file serving and Exchange 2007 are its only real jobs). Manual server startup gives rise to a 1067 error that local bentley support tells us in a communication issue that *I* should fix. OK, but we have not knowingly changed anything... I've looked but cannot find any kind of list of diagnostics to undertake to isolate the underlying issue. It leads me to speculate if the Bentley side of things may have changed recently or am I the only one suffering from this ?
I've raised a ticket with Bentley support, <rant>I even tried the 'Live chat" but gave up and closed the window after being told that its was "Paging staff" for 2000 seconds with 0 ahead of me in the queue - must be based on our local major Telcos' support model. </rant>.
Nonetheless, just wonder if anyone else has gone through a similar problem and might to able to give some pointers as to how to diagnose the root cause ? Firewall (3 com) has both port 80 and port 443 forwarded to the server.
Thanks for the response Marcus. After sleeping on the problem I tried a couple of "no-change" things this morning and the gateway server appears to have started (I'll really know when I get into the office and fire up Microstation).
FYI and anyone else who may strike a similar issue, I did two things. The first was to disable an re-enable the https (port 433) forwarding on our hardware firewall (it was enabled, so, in theory a "no-change") and the other was to manaully stop and start the default IIS web site on the server (another issue had made me suspicious of that component of the server). After that I tried manually starting the gateway service and it came up cleanly (I hope).
Now, I had power-cycled the firewall and rebooted the server a couple of times trying to resolve the issue yesterday, which you would have thought would haved achieved that same results. Nonetheless, it would useful for those of a technical leaning to have a list of simple (?) steps that progressively validate the communications links needed. Our local support gave the identity of one site that we should have been able to get a "telnet on port 80" response from but also said that there where a number of others, without identifying them.
Any thanks for response.
Alan.
[Postscript] - Perhaps I was a little hasty, the support ticket that I raised identified that they COULD reproduce the problem and that it was a Bentley internal database error that the sales guys had to fix up. So, patience may have been a virtue....
The gateway should be providing more details as to exactly why it won't startup. Please look in the Windows Event log and/or the C:\Program Files\Bentley\SELECTServer\Logs\SS-Bentley.SelectServer.Gateway.exe.log logs file for details. If needed you can post the log file here and I'll take a look at it.
-Marcus Kellermann