<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Select Server Gateway has just stopped working.....</title><link>https://communities.bentley.com/communities/other_communities/licensing_cloud_and_web_services/f/forum/41302/select-server-gateway-has-just-stopped-working</link><description>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</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Re: Select Server Gateway has just stopped working.....</title><link>https://communities.bentley.com/thread/91672?ContentTypeID=1</link><pubDate>Wed, 28 Oct 2009 02:11:39 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:7e6458bf-949a-4a88-9aa4-8461745ed6e6</guid><dc:creator>Altimes</dc:creator><description>&lt;p&gt;
Thanks for the response Marcus.&amp;nbsp; After sleeping on the problem I tried a couple of &amp;quot;no-change&amp;quot; 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). 
&lt;/p&gt;
&lt;p&gt;
FYI and anyone else who may strike a similar issue, I did two things.&amp;nbsp; The first was to disable an re-enable the https (port 433) forwarding on our hardware firewall (it was enabled, so, in theory a &amp;quot;no-change&amp;quot;) 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).&amp;nbsp; After that I tried manually starting the gateway service and it came up cleanly (I hope). 
&lt;/p&gt;
&lt;p&gt;
Now,&amp;nbsp; 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.&amp;nbsp; Nonetheless, it would useful for those of a technical leaning to have a list of simple (?) steps that progressively validate the communications links needed.&amp;nbsp; Our local support gave the identity of one site that we should have been able to get a &amp;quot;telnet on port 80&amp;quot; response from but also said that there where a number of others, without identifying them. 
&lt;/p&gt;
&lt;p&gt;
Any thanks for response. 
&lt;/p&gt;
&lt;p&gt;
Alan. 
&lt;/p&gt;
&lt;p&gt;
[Postscript] - Perhaps I was a little hasty,&amp;nbsp;the support ticket that I raised identified that they COULD reproduce the problem and that it was a Bentley&amp;nbsp;internal database error that the sales guys had to fix up.&amp;nbsp; So, patience may have been a virtue....
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Re: Select Server Gateway has just stopped working.....</title><link>https://communities.bentley.com/thread/91498?ContentTypeID=1</link><pubDate>Tue, 27 Oct 2009 15:36:04 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:212a72aa-4bcd-4ae8-ab70-c1119e670ad1</guid><dc:creator>Marcus.Kellermann</dc:creator><description>&lt;p&gt;
The gateway should be providing more details as to exactly why it won't startup.&amp;nbsp; 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.&amp;nbsp; If needed you can post the log file here and I'll take a look at it.
&lt;/p&gt;
&lt;p&gt;
&amp;nbsp;-Marcus Kellermann
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>