Thanks for all the support everyone! I'm just getting back from a bit of a break, so let's see if I can straighten out some questions.
Can you give us more details about your setup?
Currently, we have Amazing Charts 6.1.2 installed on a central server running Server 2k3 SBS. We have about a dozen machines (75% Windows 7 laptops, 25% XP desktops) connecting up, all with 6.1.2 installed as well.
Do you have wired connections? Are your laptops wireless? Are you using a gigabit switch? etc. When did this start?
The desktops are all wired, and the laptops are on wireless about 80% of the time.
And here's a bit more info:
Dell PowerEdge 2900 with Windows 2003 SBS
Connected to a Netgear FS116 16-Port unmanaged 10/100 switch (connects the desktops, server, random wall ports, wireless router, and firewall).
Wireless router is a Linksys WRT54GL (was fine when they were smaller, but things have changed. Upgrading to a Cisco Aironet in the coming months, which will certainly help). Also, if you say it's a wireless problem, I would totally believe you
The connection issues started before I came on as a co-consultant for them (about a year and a half ago). But again, these issues are incredibly random. The last time the connection dropped was when I first posted on July 27th. And that was just a week of connection issues...before July 27th, it had been weeks before the last occurrence, and before THAT it was well over a MONTH! When it's stable, it's stable for a while...but once the issues crop up, it's a week of problems until things settle down again.
I'm not sure that would make it a SQL problem. Usually if there's an issue in a database, the problem would be persistent (though I'm by no means an expert, so I could also very well be wrong).
[...]The first would be is it wireless. If so, that could be an issue. The number one reason for dropped connections, by far, is a wireless network. But, that is generally only one computer at a time.
Reading your error messages, though, does seem to point at SQL. It is even specific for the AC instance. It seems to reference a block in the database, causing it to drop a process.
[...]
In the meantime, have you considered uninstalling AC on the server including the instance? Possibly, a reinstall with SQL and creating a new instance would solve it. Of course, going against that would be that there are so many threads on the net where everyone is helping the user to fix the problem and not simply saying reinstall.
Do you mind my giving Raja your email address so he may contact you if he has time? Would you want to send your o.....a.com email address?
Wireless was my first thought too. Could it be that a laptop is writing something to the database when it loses connection, and then another laptop tries to read the partial data and the database freaks out? Again, databases aren't really my strongest background so go easy on me
And I say let the man get married. He doesn't need to bother with me quite yet (at least not while everything is manageable). He can send to my email if he likes, that's fine.
Next time your connection is dropped, just go to the server and start Amazing charts.You may login into AC and then logout.
Your connections to your workstations will be restored for AC.
I have tried pinging the Server, the router and they all reply back when the problem arises as you have described.
I have not bothered to check as why it happens as the solution seems pretty simple and painless. . Your workstation compluters will have to restart AC.
Give it a try and let me know it it works
Grenville
Actually, that's more or less what I do as well sometimes. Logging in, as well as 'Repair Connections', work to restore the connection. That's why it's weird :P
And it is simple and painless, but the curious side of me is wondering if there's anything I should be doing to fix it (not to mention trying to figure out the cause in the first place).
Thanks for the feedback guys, I hope this helps.
