Home Forums Discussions Problems sbs 2008 ac support

Anyone know why Gaurdian Angels are refusing to support SBS 2008?
My AC backup is failing due to an SQL error and support told me that since My sbs server is both a domain controller and an sql server they cannot support it.

steve,

I have used SBS 2008 for over three years now, and AC runs fine on it.

What is the SQL error you are getting?

Also please see your private message for more information.

Dear Steve,

Without more information it is hard for me to research the issue. I would be happy to look at the problem, if you would email me your practice name. My email is claire@amazingcharts.com. I am sure the staff here is being cautious not to cause any issues that may affect your domain controller.

Claire

02/08/12 04:02:37 AM
Version: AdminService 6.0.10.0
User: Unavailable
GUID: 9ce6eced-57d9-4479-98e6-5ec9089e3164
Active Control: System.String DoFullEncryptedBackup(Boolean, Boolean, System.DateTime ByRef)
Source: :
Error: (5) There was an error creating the backup file.

There was an error while attempting a Full SQL backup

Backup failed for Server 'SRMCSERVER\AMAZINGCHARTS,61067'.

An exception occurred while executing a Transact-SQL statement or batch.

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

SmartexceptionsCore.unhandledException@9256, offset:299

SmartexceptionsCore.unhandledException@9251, offset:231

SmartexceptionsCore.unhandledException@9252, offset:371

SmartexceptionsCore.unhandledException@9136, Offset:845

SmartexceptionsCore.unhandledException@9357, Offset:124

Sandeep,

Is that the normal error or did you get it some other way?

I suspect that the tech might have understood that AC was being hosted by the SQL server of SBS and not the "SQL lite" version that AC installs.

While I am sure that it will run on the more robust version, I think full SQL is NOT a supported version directly. They might not have the training to make sure they don't screw up something else in full SQL, especially in the first tier of support.

That's what he sent me. I have an idea, but I told he can send me a remote support request so I can better idea. I don't want to make recommendations based on a simple event log output without getting the full picture.

Hello,

From the message above it looks like the backup is timing out. If you move the database to a different computer does it complete? Could it be a resource issue? If you go to Microsoft?s forums you find there are noted problems with installing a SQL program on a domain controller. We have found sometimes it works and sometimes it does not. If the problem is windows related we would not be able to correct the issue.

Claire

I have my suspicions as well, but my inclinations have nothing to do with it being a DC or not. Time or details will tell.

I agree. I can't argue with you if you find articles on Microsoft, but if you couldn't install databases on a domain controller, then all things computer would come to a screeching halt.

Also, it is unlikely that it is being installed to the native SQL Server as it isn't set up to make an instance there. If the user is asking about this, I doubt he did anything other than use SQL Server 2005 Express.

Thanx for your response. Sandeep posted the error for me and we are looking at the problem now

Make sure you have the ChilkaDotNet2.dll in the Amazing Charts folder. Would give a different error message, but I would check.

Are you running this from the server?

Are you right clicking and choosing Run As Admin?

Have you tried looking at Properties on Amazing Backup and trying to run it as Windows Server 2003 and XP Pro?

Just some ideas to take up some time.

Let's see what AC Staff says.

steve,

Try be sure to answer everyone's questions as it may be just one that makes the difference. Wendell made a good point about whether or not you are using the default SQL instance that comes with AC. My guess is you are, but it would be good to know. We're trying.

I also think an uninstall and reinstall may fix it. Please look at that file I posted to ensure it is in the AC folder. If not, it won't work.

Any resolution or progress?

I hate to disagree with Bert since it almost always means I'm wrong, but Microsoft did not intend for Line of Business applications to be installed on the SBS 2008 Server. It's just doing too many other things with too much automation to include another instance of SQL. For folks with SQL LOB apps they want peeps to get the SBS 2008 Premium which includes a separate SQL 2005 or 2008 license. That said, there's probably not much reason that a SQL Lite instance wouldn't run on the SBS 2008 Server, but if you tried to install full SQL 2005 the system should try to stop you. I think the automation for SBS 2008 relies on SQL so there is already some sort of database installation.

You are probably correct, but we have installed both the full version of SQL 2005 and SQL 2008 on SBS 2008.

You are definitely correct in that the premium version will give you the separate licenses.

I am curious as well. Didn't get a response since Claire's posting. Maybe AC figured it out?

My SQL friend fixed it. I had guessed permissions in a PM. But, it also required SP4.

I asked Steve to post back with the details so we could all learn.

I was thinking the same. The account used to backup didn't have sufficient permissions.

Exactly. Unfortunately, we both wrote it in PMs. So no one knows how brilliant we are. Or brillianter you are.

I apologize for the tardiness of my final post on this issue. I just got back in the office.
My thanks to Bert,Sandeep,Raja and Claire for their Time and personal involvement in solving this issue.
Claire worked with me Fri afternoon.
Raja spent Friday evening with me working on finding solutions to the problem.
We solved the issue by accessing and changing the permissions within the sql software itself. These were a separate from the windows permissions. I am not versed enough in sql itself to explain where these are. Hopefully I will not need to find them again.
We also updated the V4 patch of SQL.
The backup program is now working as it should.
BTW I have the AC automated backup scheduled to backup at noon . That way the most we can ever lose is half a day, worst case scenario.
I want to thank everyone who was kind enough to offer help on this, your support is appreciated.

Steve Stein
Santa Rosa Medical Clinic
Santa Rosa,NM
eqboal@hotmail.com
575-472-4311

Thanks, though I'm sure you are the brillianter one. I don't know how you find the time ha. But I do have to say, I love this user board.

I didn't write it on the board OR in a PM. I just thought it. Does that make me the brillianterest of all?

Actually, I haven't understood a bit of this thread since Steve asked "Anyone know why...."

Basically, his backup program was timing out due to certain parts of the backup processs not having certain permissions.

Also, SQL Server 2005 Express had some "missing parts" which was fixed by downloading and installing SP4.

I suppose that should be a lesson to all of us if we are having issues. Do we have the latest service pack for SQL. If you do download it, be sure to back up the computer first as service packs can be tricky. Or let Raja do it.

Every OS has its own style to handling errors.

Windows often stares into the distance and says nothing unless you know where to look; kind of like a Malamute that we had that would seem to suddenly go deaf if you told it something she didn't want to hear - I learned to watch it's ears, they would twitch or swivel.

With Linux, you get a response, but it is often of the "I'm sorry Dave, but I can't let you do that."

Thanks Steve for the explanation. The cool thing is it is both fixed and you learned something about SQL.

And, yw.