Home Forums Discussions Problems Need Urgent Help with Setup

We've just relocated our practice and replaced a SBS2003 with SBS2008. I rebuilt a similar file/share structure on the new server and installed AC (5.0.24) on 5 brand new Win7 Pro machines (there are several more). AC refuses to run on any client machine.

As of now, I'm getting the oh-so familiar 'SQL Server Connection Error' that states:


I have run the setup numerous times, checked the firewall ports, and run the 'virtual IT' person and everything comes back with green checks. I tried the 'run as admin' trick on the server. None of these helped. I finally just got the DB to restore correctly so I'm relatively confident that the data is there. We are due to open back up (construction JUST completed) this Tuesday and I'm completely out of ideas after spending two days on this.

Before we abandon the program and resort to paper when we open, I wanted to know if anyone has experienced anything like this and could possibly lend a hand.

iirc, ac utilities have to be run on the server. That leaves me wondering if you have your ac folder shared correctly. Can you browse to the ac folder, create a new file, then delete it?

You should call the AC support phone number and leave an urgent message - they monitor for emergencies that prevent the program from working. Maybe they can log on and look - does the program run on the server and work ?

I think the program wants you to run the utilities on the server.

BUT, Ben is completely correct. The first thing you should do is browse to the server, make a text file, save it, then delete it.

He could be wrong, but it is almost always permissions.

Another thing. When you say replaced, do you mean same server and now reformatted and SBS 2008 on it. You don't have another computer running 2003 and this one running 2008?

No, this is an entirely new box--our 03 SBS box had seen better days. I've been running AC Utilities on this new 08 box, I've tried mapping the server hard drive, sharing a dedicated AC folder, and simply pointing other machines to the default AC install location.

Yep, AC runs perfectly on the server--which made me think it could be a firewall issue. I'm about to dial in to their customer support login here shortly, and I'll post the results once this situation is resolved for those who may come across something similar.

I was just told by tech support that I cannot run Amazing Charts on a SBS 2008 machine (can't be a domain controller?). Has anyone come across a workaround? This is a HUGE setback.

Also, I'm able to create/delete text files in my AC folder on the 08 SBS box if that makes any difference, so the permissions appear to be OK. It looks like my only options are to:

1) Join the old 03 SBS server to this new domain I've created and simply make it a file server where AC sits and have all the clients local AC's pointed to a shared directory there. This will be complex because there can't be more than one SBS on any one network and I don't have another OS to downgrade it to on hand.

2) Reconfigure AC to run P2P, which I have absolutely no idea how to do. I will try this first once I figure out where to start. I've only used servers for AC and I don't understand the topology of the p2p setup or where the physical DB's reside.

Wow! This makes me want to throw my computer across the room. I would call Jon and ask who in support told you that.

You can run AC on SBS 2008. SBS 2003 runs on a domain as well. There is no reason you cannot run AC on a domain. I have run AC for three years both on 2003 and 2008.

Do not put SBS 2003 on with SBS 2008 as you noted due to DHCP, DNS, and FSMO roles, etc. It is its one big limitation. If you have the premium edition, you can run Windows Server 2008 concurrently, but you don't need to.

DO NOT GO BACK TO 2003. THAT'S CRAZINESS.

Peer to peer is basically being off the domain. People will talk P2P all the time, but it is just a bunch of computers in a workgroup connected by a switch or router. Then they choose a "main computer." All you have done is to designated a "super computer" and make it a domain.

Please do not reconfigure AC to peer to peer. This is insanity.

1. Keep SBS 2008 and your domain.
2. Keep AC on the SBS box.
3. Troubleshoot until you figure out why you can't connect.

I will be glad to help, maybe even remote in if that helps. We could put our heads together.

I think the problem with AC support is they are great with AC, but how much do they know about domains and networking? How much do they know about SQL Server? It's a lot to know.

Wow, I am mad.

Currently on with tech still, Carlos has suggested uninstalling SQL 2005 (current) and switching over to SQL Express 2005. My 08 SBS is the Standard Edition. He's working with the development team. Bert, I knew there had to be someone who got it to work using SBS08 out there.

Not sure what capabilities I'll lose in the downgrade, but I don't use SQL for anything besides AC and whatever the server needs to use it for by default. Currently downloading..

I am not so sure you should uninstall 2005 Standard yet. It is a far better SQL server. I am running mine on SQL Server 2005 Standard.

I guess you could try it as long as you can reinstall it. May work. An AC instance on any 2005 SQL should work fine. Very frustrating.

I don't have any SQL Server 05 Standard media, as it came with the OS. Will I still be able to reinstall if Express gives me the same result?

Carlos is very good, I have to say. Did he tell you to uninstall all of SQL or just the AC instance?

Not sure what his intent was regarding the instance or SQL entirely, I simply downloaded and installed Express 05. He's remoted into the server and a client right now. I'm curious as to how you got yours working so well..

That's interesting. It sounds like you didn't use the native SQL server and just used the Express version which was distributed with it. I have heard of issues with that. I simply didn't choose to install Express, and it made a named instance using the native SQL.

Hopefully, he can get it fixed for you. If not, let me know.

I am thinking that when you clicked on SQL Server 2005 in Add/Remove programs, there were a couple of instances. Probably SQL monitoring as well. You would only click the radio button for AC and remove it and not all of SQL.

SOLVED!

The culprit was the SBS08 firewall. Once it was disabled the client machines were able to connect to the shared database where I'd installed AC. For anyone who comes across a SQL error similar to what I wrote above that isn't covered by the FAQ or previous threads here, DISABLE the OEM firewall then simply enable it once the installs are done. Its weird because the virtual IT program didn't see a problem with the firewall being active so I simply overlooked it.

Bert, I didn't ever uninstall SQL Standard because I agreed with you and didn't think it was the problem. Seems to be working fine now, just in time. Thanks to you and Carlos I have retained my sanity once again.

And, firewalls! I can't believe I forgot that.

That's great news! Now, you can just relax and see patients.

Royce,

How quickly we forget.

Today I copied the "Import" file no problem. Then I turned off
the firewall on the "new main" computer and I could reset path on client! Windows 7 firewall setting changes are a little different that XP but managed to ok file MSSQL$AMAZINGCHARTS and open port 61067. Viola, all clients able to access the new VOSTRO main. It's all set up and running perfectly.

This was a person with a similar problem back in May. He was able to finally get the clients to attach by turning off the firewall temporarily.

It's weird, I still have to have the firewall completely disabled on the 08 SBS machine in order for AC to work at all in my network. Did you have to add exceptions for any other programs besides 'MSSQL$AMAZINGCHARTS' within the firewall configuration utility? I just turned my firewall on to test and it kicked everyone off almost immediately..

I suppose I would go into the Windows Firewall on the server, click on Change Settings and then the Exceptions tab and make sure Amazing Charts is there and checked.

Go to Add port and select TCP, add a name such as AC and then 61067. Click OK. If it is already open, you will get an error message telling you it is already open for AC. If you don't get this error, that would be the problem.

While there, you can click on the check box that allows the firewall to notify you if a program is blocked.

Under Advanced, there will be a list of your network connections. You could uncheck these, which should allow you to use the program while you are troubleshooting. These would be internal networks and not traffic entering from the outside.