Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

ap_collector error - event ID 8255

Posted on 2008-06-13
14
5,960 Views
Last Modified: 2012-06-27
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.
0
Comment
Question by:tt0wnsend
  • 4
  • 3
  • 3
  • +4
14 Comments
 
LVL 8

Expert Comment

by:sbagireddi
ID: 21780623
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
 

Author Comment

by:tt0wnsend
ID: 21780921
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
 

Expert Comment

by:markpetch
ID: 21908144
I am having the same problem with a print server

Microsoft Windows Server 2003
service pack 2

Any ideas?
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 1

Expert Comment

by:fusioninternet
ID: 22034149
Just out of interest have either of you got Watchguard System Manager installed on the servers?
0
 

Expert Comment

by:Lazorpoint
ID: 22079229
I have this problem too, and yes we have Watchguard System Manager installed.
0
 

Expert Comment

by:bpickel1975
ID: 22132555
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
 

Author Comment

by:tt0wnsend
ID: 22132581
Yes, I have WatchGuard System Manager installed on that server also.
0
 

Expert Comment

by:bpickel1975
ID: 22132610
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
 

Author Comment

by:tt0wnsend
ID: 22132644
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
 

Expert Comment

by:bpickel1975
ID: 22132762
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
 

Expert Comment

by:8r0k3n71nX
ID: 22133040
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
 
LVL 1

Expert Comment

by:fusioninternet
ID: 22136314
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
 

Expert Comment

by:bpickel1975
ID: 22138781
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
 
LVL 1

Accepted Solution

by:
fusioninternet earned 500 total points
ID: 22138895
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

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction This article will provide a solution for an error that might occur installing a new SQL 2005 64-bit cluster. This article will assume that you are fully prepared to complete the installation and describes the error as it occurred durin…
INTRODUCTION: While tying your database objects into builds and your enterprise source control system takes a third-party product (like Visual Studio Database Edition or Red-Gate's SQL Source Control), you can achieve some protection using a sing…
In a recent question (https://www.experts-exchange.com/questions/29004105/Run-AutoHotkey-script-directly-from-Notepad.html) here at Experts Exchange, a member asked how to run an AutoHotkey script (.AHK) directly from Notepad++ (aka NPP). This video…
In an interesting question (https://www.experts-exchange.com/questions/29008360/) here at Experts Exchange, a member asked how to split a single image into multiple images. The primary usage for this is to place many photographs on a flatbed scanner…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question