So a client has a SQL 2008R2 running on a W2008R2 box, and it is there for two 3rd part programs, one work well with no frequent SQL issues, the other has a problem in staying connect to its small database. A few times users have been denied logins from
the 3rd party interface, but that was restored without any action on my part or the 3rd party's. They said it was a problem communicating with the database, network issues, etc. None of which could be proven.
Now a service, that runs right on the server & starts a mail notification program solely for their program, stop at random, sometimes restarts, and sometimes doesn't. They claim it's the fault of SQL, somehow, but can't explain further, just that their program logs Microsoft error 2147467259 when failing to reconnect. Manually, I can always restart the service, and temporarily have a scheduled Windows task to run a "net start" for the service a couple of time a day, just in case.
They won't help, claiming NONE of their other customers has had this issue. Can anyone here suggest how I can proceed to "fix" this? Thanks.
Now a service, that runs right on the server & starts a mail notification program solely for their program, stop at random, sometimes restarts, and sometimes doesn't. They claim it's the fault of SQL, somehow, but can't explain further, just that their program logs Microsoft error 2147467259 when failing to reconnect. Manually, I can always restart the service, and temporarily have a scheduled Windows task to run a "net start" for the service a couple of time a day, just in case.
They won't help, claiming NONE of their other customers has had this issue. Can anyone here suggest how I can proceed to "fix" this? Thanks.