been experiencing similar problems. The crashing has only been
occassional, but this week we also lost two forms in SQL view and on the
SQL database. The forms appear to exist on the AR Server but they are
missing from the SQL view and the SQL database. We are still in the
process of investigating.
ARS List wrote:
> Remedy 4.5.1WINNT 4.0SQL Server 7.0 (clustered - on a separate server
> than Remedy ARS) Remedy is crashing on me - at least daily - and this
> issue has proven very difficult to troubleshoot. It seems as if the AR
> Server is losing connectivity to the SQL Server - however only for a
> brief period of time. When I stop and restart the services,
> everything works fine - for somewhere between an hour and a day. The
> network that the servers are on is new, and I have the same
> application running fine on Development servers. I have verified that
> all of the executable files, and .dlls in the remedy directory are
> exactly the same as our development server. Pinging the database from
> the remedy server is always successful.There have been several DNS
> changes within the new network recently.Thinking that this may have
> been a name resolution issue, I specified the IP address of the SQL
> Server machine in the ar.conf file. Has anybody seen this before? Any
> clues on how to continue troubleshooting? Our network guys keep
> saying that it is an application issue, not a network issue - but I
> have the same application running without problems on a different
> network... The problems occur during idle times, and during times
> where traffic is hitting the remedy server - but most often when the
> AR Server has been idle for an hour or too, and you try to access a
> form. The errors I am seeing in the arerror.log file are below. They
> can be reproduced easily by stopping the SQL Server service:Tue Jan 09
> 01:36:20 2001 390603 : Failure during SQL operation to the database
> (ARERR 552)
> Tue Jan 09 01:36:20 2001 Possible network error: Write to SQL
> Server Failed. General network error. Check your documentation. (SQL
> Server 10025) : ConnectionWrite (send()).
> Tue Jan 09 01:36:20 2001 Possible network error: Write to SQL
> Server Failed. General network error. Check your documentation. (SQL
> Server 10025) : ConnectionWrite (send()).
> Tue Jan 09 01:36:20 2001 390603 : Failure during SQL operation to the
> database (ARERR 552)
> Tue Jan 09 01:36:20 2001 Possible network error: Write to SQL
> Server Failed. General network error. Check your documentation. (SQL
> Server 10025) : ConnectionWrite (send()).
> Tue Jan 09 01:36:20 2001 390603 : AR System server terminated --
> fatal error encountered (ARNOTE 21)
> Tue Jan 09 01:36:20 2001 390603 : Failure during SQL operation to the
> database (ARERR 552)
> Tue Jan 09 01:36:20 2001 DBPROCESS is dead or not enabled. (SQL
> Server 10005)
> Tue Jan 09 01:36:20 2001 DBPROCESS is dead or not enabled. (SQL
> Server 10005)
> Tue Jan 09 01:36:20 2001 390603 : Failure during SQL operation to the
> database (ARERR 552)
> Tue Jan 09 01:36:20 2001 DBPROCESS is dead or not enabled. (SQL
> Server 10005)
> Tue Jan 09 01:36:20 2001 DBPROCESS is dead or not enabled. (SQL
> Server 10005)
> Tue Jan 09 01:36:20 2001 390603 : Failure during SQL operation to the
> database (ARERR 552)
> Tue Jan 09 01:36:20 2001 DBPROCESS is dead or not enabled. (SQL
> Server 10005)
> Tue Jan 09 01:36:20 2001 DBPROCESS is dead or not enabled. (SQL
> Server 10005)
> Tue Jan 09 01:36:20 2001 390603 : Failure during SQL operation to the
> database (ARERR 552)
> Tue Jan 09 01:36:20 2001 Possible network error: Error in closing
> network connection. General network error. Check your documentation.
> (SQL Server 10018) : ConnectionClose (closesocket()).
> Tue Jan 09 01:36:20 2001 Possible network error: Error in closing
> network connection. General network error. Check your documentation.
> (SQL Server 10018) : ConnectionClose (closesocket()).
--------------C2962492764526AF13DD15E0
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
We are running the same set-up in our development environment and have been experiencing similar problems. The crashing has only been occassional, but this week we also lost two forms in SQL view and on the SQL database. The forms appear to exist on the AR Server but they are missing from the SQL view and the SQL database. We are still in the process of investigating.
ARS List wrote:
Remedy 4.5.1WINNT 4.0SQL Server 7.0 (clustered - on a separate server than Remedy ARS) Remedy is crashing on me - at least daily - and this issue has proven very difficult to troubleshoot. It seems as if the AR Server is losing connectivity to the SQL Server - however only for a brief period of time. When I stop and restart the services, everything works fine - for somewhere between an hour and a day. The network that the servers are on is new, and I have the same application running fine on Development servers. I have verified that all of the executable files, and .dlls in the remedy directory are exactly the same as our development server. Pinging the database from the remedy server is always successful.There have been several DNS changes within the new network recently.Thinking that this may have been a name resolution issue, I specified the IP address of the SQL Server machine in the ar.conf file. Has anybody seen this before? Any clues on how to continue troubleshooting? Our network guys keep saying that it is an application issue, not a network issue - but I have the same application running without problems on a different network... The problems occur during idle times, and during times where traffic is hitting the remedy server - but most often when the AR Server has been idle for an hour or too, and you try to access a form. The errors I am seeing in the arerror.log file are below. They can be reproduced easily by stopping the SQL Server service:Tue Jan 09 01:36:20 2001 390603 : Failure during SQL operation to the database (ARERR 552)
Tue Jan 09 01:36:20 2001 Possible network error: Write to SQL Server Failed. General network error. Check your documentation. (SQL Server 10025) : ConnectionWrite (send()).
Tue Jan 09 01:36:20 2001 Possible network error: Write to SQL Server Failed. General network error. Check your documentation. (SQL Server 10025) : ConnectionWrite (send()).
Tue Jan 09 01:36:20 2001 390603 : Failure during SQL operation to the database (ARERR 552)
Tue Jan 09 01:36:20 2001 Possible network error: Write to SQL Server Failed. General network error. Check your documentation. (SQL Server 10025) : ConnectionWrite (send()).
Tue Jan 09 01:36:20 2001 390603 : AR System server terminated -- fatal error encountered (ARNOTE 21)
Tue Jan 09 01:36:20 2001 390603 : Failure during SQL operation to the database (ARERR 552)
Tue Jan 09 01:36:20 2001 DBPROCESS is dead or not enabled. (SQL Server 10005)
Tue Jan 09 01:36:20 2001 DBPROCESS is dead or not enabled. (SQL Server 10005)
Tue Jan 09 01:36:20 2001 390603 : Failure during SQL operation to the database (ARERR 552)
Tue Jan 09 01:36:20 2001 DBPROCESS is dead or not enabled. (SQL Server 10005)
Tue Jan 09 01:36:20 2001 DBPROCESS is dead or not enabled. (SQL Server 10005)
Tue Jan 09 01:36:20 2001 390603 : Failure during SQL operation to the database (ARERR 552)
Tue Jan 09 01:36:20 2001 DBPROCESS is dead or not enabled. (SQL Server 10005)
Tue Jan 09 01:36:20 2001 DBPROCESS is dead or not enabled. (SQL Server 10005)
Tue Jan 09 01:36:20 2001 390603 : Failure during SQL operation to the database (ARERR 552)
Tue Jan 09 01:36:20 2001 Possible network error: Error in closing network connection. General network error. Check your documentation. (SQL Server 10018) : ConnectionClose (closesocket()).
Tue Jan 09 01:36:20 2001 Possible network error: Error in closing network connection. General network error. Check your documentation. (SQL Server 10018) : ConnectionClose (closesocket()).
--------------C2962492764526AF13DD15E0--
Previous Topic
Index