Welcome to ISAserver.org
Forums |
Register |
Login |
My Profile |
Inbox |
RSS
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
"The query stopped because an error occurred while it was running."
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login | |
|
"The query stopped because an error occurred while... - 3.Jun.2005 2:23:00 PM
|
|
|
dfosbenner
Posts: 116
Joined: 14.Nov.2001
From: Maybrook, NY USA
Status: offline
|
I get the error above when doing a query. "Live" works OK, but setting anything to a previous time period produces the error.
This started all of a sudden a couple days ago. I noticed it after I move the location of the ISA Logs to another drive. I've since moved them back to the default location, but the error persists. I've rebooted. I'm running W2K3 SP1 with ISA2K4 SP1.
Anyone have an idea?
Queries are very helpful in determining if connection attempts succeed or not, and what rule is preventing them. I'd like to get this solved.
|
|
|
|
RE: "The query stopped because an error occurred w... - 4.Jun.2005 10:21:00 AM
|
|
|
tshinder
Posts: 47644
Joined: 10.Jan.2001
From: Texas
Status: offline
|
Hi Dave,
Are you using MSDE logging?
Thanks! Tom
|
|
|
|
RE: "The query stopped because an error occurred w... - 6.Jun.2005 11:10:00 AM
|
|
|
dfosbenner
Posts: 116
Joined: 14.Nov.2001
From: Maybrook, NY USA
Status: offline
|
Hi Tom,
Yes, I am using MSDE logging. Is there a way to run some kind of a "cleanup", reindex, or something on the databases?
|
|
|
|
RE: "The query stopped because an error occurred w... - 6.Jun.2005 12:30:00 PM
|
|
|
dfosbenner
Posts: 116
Joined: 14.Nov.2001
From: Maybrook, NY USA
Status: offline
|
I found the link below in another post, and it worked. Apparently ISA doesn't detach databases properly when it lets you move them. Detach & Reattach Databases
|
|
|
|
RE: "The query stopped because an error occurred w... - 31.Jul.2005 9:21:00 PM
|
|
|
Guest
|
If you are not using MSDE (advanced logging) and appear this message then you need set Log On account for service Microsoft Firewall to "Local System". It's work.
|
|
|
|
RE: "The query stopped because an error occurred w... - 5.Apr.2008 1:53:37 PM
|
|
|
marvinmiller
Posts: 51
Joined: 2.Jan.2006
Status: offline
|
I'd like to weigh in on this one too... I just had that exact error today and I couldn't figure out why. I reverse publish some websites and I noticed a user in the US coming on and requesting endless amounts of data from one of my sites. This went on for hours (and maybe days) so he was up to something. As a result, I created a network set containing his IP address and then modified my web publishing rules to block requests from that address. After verifying that my solution worked (kept that IP off my sites) I then tried to do a dB query to see just how long he had been on the site for. To my surprise I kept getting the same error - "The query stopped because an error occurred while it was running." Microsoft KB states that if there is too much data you might get this same error so I dropped the time element down to 7 days - same message. I then dropped it down to 24 hours - same message. There's nothing wrong my ISA - it's been running 100% for months now. In my case I suspect the problem is caused by my creating a network set with his IP address in it and blocking it by using the exceptions box in the From tab in the web publishing rule. I suspect that someone this interferes with the query. I just posted this in the hopes that someone else encountering the same issue might have the same circumstances - and that this might shed some light on it. BTW, I am using the stock ISA 2004 logging, the stock locations and SP#3 with whatever other updates were available.
_____________________________
Best & thanks; Marvin http://www.asksomeone.net
|
|
|
|
RE: "The query stopped because an error occurred w... - 25.Sep.2008 8:14:00 AM
|
|
|
misitmichaelf
Posts: 1
Joined: 25.Sep.2008
Status: offline
|
Just to throw in my two cents - I was also getting the same error but with ISA 2006. I asked a co-worker to check it out and he was not getting the error. Turns out it was a problem with my windows profile. Blew it away and then re-logged in and now it's working just fine!
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|