July 23, 2008 at 8:40 am
First time posting here......hope someone out there can help.
Situation: Server running SQL 2005 for a single application. Two sites, the LAN is connecting with no problems. The second site, 100 miles away, are connecting with a remote desktop connection (only 2 users). They are able to connect to the appication, yet are kicked out at random times.....usually 5 to 15 minute intervals. On the Windows 2003 server, the Event Viewer Application log shows event ID 18100, source MSSQLSERVER............Process ID (different numbers) killed by hostname (server's name).
Upgraded to SQL 2005 SP2 from the RTM version, rebooted server.....yet the problem persists. Google searches for the problem don't show much.
Anyone experience this before??
July 23, 2008 at 2:55 pm
Architecture matters. Is the application housed locally, or are the remote users trying to log into the database directly from their long distance away?
SQL Server has a very SMALL tolerance for time delays - if only the database is local, you either want to replicate the DB for the remote users in some way and then user a replication strategy to keep everyone on the same page, or otherwise redefine your architecture.
If the application is housed locally, near the DB, then talk to your systems people - it should not be a SQL Server problem, but a problem in how they connect to the application.
Hope this helps... more details will be useful if this doesn't answer the question.
July 23, 2008 at 3:09 pm
using terminal services in application mode would ideal for remote users, the processing is all done on the terminal server which would be on the same LAN as the database. All the remote users receive\return are the displays and keystrokes, etc
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 25, 2008 at 10:02 am
Ok, installed Terminal Services in application mode......yet, the problem persists. The remote site with only 2 users are able to remote into the server with no problem. They are able to log into and begin using their SQL based application with no problem. At random times (matter of minutes), the application kicks them out. The application log within Event Viewer states: Process ID (number) killed by hostname (servername). This only occurs at the remote site. The main site's LAN never experiences this problem. The remote site users are only getting kicked out of the SQL based application.....NOT kicked out of the terminal server connection. The exact error message displayed on the remote user's terminal server connection when kicked out of the application is below:
-2147467259:[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send()).
Thanks in advance for any help.
July 25, 2008 at 10:19 am
Ok, installed Terminal Services in application mode......yet, the problem persists. The remote site with only 2 users are able to remote into the server with no problem. They are able to log into and begin using their SQL based application with no problem. At random times (matter of minutes), the application kicks them out. The application log within Event Viewer states: Process ID (number) killed by hostname (servername). This only occurs at the remote site. The main site's LAN never experiences this problem. The remote site users are only getting kicked out of the SQL based application.....NOT kicked out of the terminal server connection. The exact error message displayed on the remote user's terminal server connection when kicked out of the application is below:
-2147467259:[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send()).
Thanks in advance for any help
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply