ap_collector error - event ID 8255

I cannot find this particular error message anywhere. The server that I am receiving this event ID for is a Microsoft Server 2003 with SQL 2005 installed.
tt0wnsendAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
fusioninternetConnect With a Mentor Commented:
I'm not sure but i believe that the sql being installed could be  a red herring.
Ther server we have his installed on doesn't have sql installed on it and the error to us appears to be totally watchguard related.

I have seen a couple of articles on the watchguard site which recommend changing a coupe of the ini filse for watchguard logging adn re-running the logging wizard, bu tnot yet anaged to impliment them.
0
 
sbagireddiCommented:
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?
0
 
tt0wnsendAuthor Commented:
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
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
markpetchCommented:
I am having the same problem with a print server

Microsoft Windows Server 2003
service pack 2

Any ideas?
0
 
fusioninternetCommented:
Just out of interest have either of you got Watchguard System Manager installed on the servers?
0
 
LazorpointCommented:
I have this problem too, and yes we have Watchguard System Manager installed.
0
 
bpickel1975Commented:
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 ?
0
 
tt0wnsendAuthor Commented:
Yes, I have WatchGuard System Manager installed on that server also.
0
 
bpickel1975Commented:
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.
0
 
tt0wnsendAuthor Commented:
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.
0
 
bpickel1975Commented:
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.
0
 
8r0k3n71nXCommented:
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.
0
 
fusioninternetCommented:
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.
0
 
bpickel1975Commented:
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.