ap_collector error - event ID 8255

Strange! It looks more like a Postgre sql error.
How are you trying to connect to the server? Are you using Management studio or some other client?

I am using Management Studio but not having any connection problems connecting to the SQL server or Management studio - just keep having these errors in my event log

I am having the same problem with a print server

Microsoft Windows Server 2003
service pack 2

Any ideas?

Just out of interest have either of you got Watchguard System Manager installed on the servers?

I have this problem too, and yes we have Watchguard System Manager installed.

We are also seeing this behavior. When it accours it causes the server to stop answering RPC and RDP connections. We have Watchgaurd installed. Does anyone have a resolution ?

Yes, I have WatchGuard System Manager installed on that server also.

Mee thinks we are starting to find a common thread. I have recently installed another ap which has SQL desktop engine and that is where my trouble begins.

I just checked my event logs for that server and looks like I quit having the error on 6/13/2008 but I don't remember changing anything that would have corrected the problem. WG System Manager is still installed. Looks like I did uninstall the report server and log server from that server because there were other issues with report server and log server (WatchGuard) not workling properly on an SQL server and/or with the WG Suystem Management installed on the same server.

My call is that it is goignt to be the log server. I have signs pointing to this. I have disabled logging and will be able to watch and see if the errors cease.

We have WG SysMgr installed on 2 servers. Both running MSSQL and the only one that reports the error is the secondary log server. I have removed the WG SysMgr  from the secondary server and will watch the event logs.

We started to get this error after we redirected the watchguard logging to the D Drive from teh the C Drive, have yet to find out how to stop it.

We moved logging to another box and as it stands the issue seems to be resolved. It has not been a full day yet but I will report back. I was clued in by Postgress and ap_collector event logs that refer to the WatchGuard. How many people have other types of SQL instances running on the boxes that are having issues? We have mutilple on this particular DC it acts as a print server as well.