Home Forums Discussions Problems problems after SBS 2011 upgrade

I just installed the upgrade on SBS 2011 on December 11, 2013. Right after the upgrade, the client computers could not access the Amazing Charts database. I had to call Guardian Angel support, they changed the permissions, on the amazing charts folder on the server and I was able to access the database from the client computers. Apparently, SBS 2011 upgrade change the permissions of data files.

Although I was able to access the database, every time I start amazing charts on a client computer now, I get a message that amazing chart service is not running on the server. Yesterday I called Guardian Angel support, and worked with one of the tech support guys, and he was on remote control of my SBS 2011 server for more than two hours and could not fix the problem. He told me that on Monday morning, he will speak to a senior-level tech support person and call me.

When I run amazing chart utilities and check database, database definition check fails and there is an error message about FILES MISMATCH in amazingcharts.MDF and it says that the actual paths of codes.mdf and meds.mdf are different from expected paths.

In the meantime, I noticed that after the SBS 2011 upgrade, it has filled up my boot partition, which is 120 GB, and only 1.15 GB is left free now. The biggest file is SUSDB.mdf 12.3 GB and biggest folder is inetpub, which is 38 GB. And 37.8 GB of that 38 GB, is in log files, most of it in a folder w3svc1572271583. Can I safely delete log files?

My Windows update repository data, SharePoint data, and exchange data is already stored on the data drive E, which is different from the OS boot drive C. So I am unable to move any other data from Windows small business console to the E partition.

Can anybody help with these two issues?

SUSDB.mdf is the WSUS database. There's a cleanup wizard in the WSUS Administration Console under Options. inetpub is for the IIS log files for WSUS. There was an issue with the original script responsible for deleting the old logfiles. The new script was automatically included in Windows Update.

Check this KB Article for the resolution:
http://support.microsoft.com/kb/2538579

The log files grow when you leave the console open. If you close the SBS console when not in use, it will reduce the size.

Just as reference, mine is <100MB. So 30GB means your log files probably have never been cleared.

When it just won't work... Who ya gonna call?

Sandeep, the ArchAngel

He just doesn't like to blow his own horn like the other archangels.

Thank you Sandeep.

As always, you are a saviour!

I created the new wsuslogcleaner.vbs and ran it and the log file size is reduced to 15 GB!

BUT the Amazing Charts check database is still failing, giving error at Database Definition Check.

Following is the error message:

FILE MISMATCH in AmazingCharts.mdf.

Expected Path = '\\192.168.1.6\Amazing Charts'
Actual Path: 'E:\Amazing Charts'FILE MISMATCH in Codes.mdf.

Expected Path = '\\192.168.1.6\Amazing Charts'
Actual Path: 'E:\Amazing Charts'FILE MISMATCH in Meds.mdf.

Expected Path = '\\192.168.1.6\Amazing Charts'
Actual Path: 'E:\Amazing Charts'

**To fix these errors, try running the 'Repair Connection' tool on the main page of Amazing Utilities.

AC Gaurdian Angel worked for more than 2 hours on Friday on this problem and could not fix it. DO you knowwhat this error is due to? This statrted after the last SBS2011 update.


Sanjeev

This is why I don't like WSUS. I always leave all the updates with Microsoft.

1. Dumb question, but did you run the Repair Connection?

2. Why not revert to before the update.

3. Unless Sandeep comes along, I can try to remote in and help.

I have a few ideas.

http://technet.microsoft.com/en-us/library/cc561139.aspx

Have you looked at this anyway? The paths would see relatively easy to fix, but you have to remember once you get down to below 4GBs, your server will act erratically. Does Exchange work. It is usually the first to go.

Are the files that are on C:\ drive the metadata files for the WSUS files?

Here is another thought: Right click on My Computer, Properties, Advanced System Settings, Advanced, Performance settings, Performance options, Advanced. How large is your paging file? It shouldn't be on your C drive anyway. Best practices would say make the paging file 1.5 times your RAM. That could free up some space.

Download a program called TreeSize. This is a must have program, which after running will show all of your data and files in tree form, so you can see if there are any folders that are too big. Of course, you kind of already know. I was once down to 5GBs, ran TreeSize and found a 32GB backup, which I deleted. 37GBs now were there.

Amazing Chart Service is not running on your server is a bug from over a year ago, you just click through it. Apparently, AC doesn't find it annoying enough to fix it.

Another thing, whether Sandeep or I or Indy can fix this, your main concern right now is your 1.5GBs of space. Maybe the page file can fix that. But, your server is going to stop running. You may want to consider moving AC to another computer temporarily.

Finally, I know that $257 is a bit pricey, but in the scheme of things at least you know you will fix the WSUS and size issue. Microsoft WILL FIX THIS. I would have called them today. They will remote in and work through the night if necessary. Of course, you can't call them on the weekend or they will charge you $500. But, there is an issue with temp files and WSUS. Like you said, you already moved it as best practices would say, although I don't move those things, and I leave the WSUS files on the net. So, something is strange and maybe Sandeep who rocks can fix it, but as far as the WSUS and why it is showing up on the C:\ drive will be corrected 100% by Microsoft. Personally, I have never seen any better support in the world than Microsoft's.

And, finally #2, I wouldn't hold your breath for senior help. I don't mean that in a mean way. AC can likely fix the path issue, but they are not going to understand the WSUS issues, and my guess he/she will just tell you that it isn't compatible with SBS 2011, which, of course, is crazy.

I like it. What I don't like is the way it comes out of the box with SBS 2011. They literally tell the server to download updates for every single Microsoft Product out there.

WSUS Console>Options>Products and Classifications
You'll see everything from Bing to System Center 2012R2. It's a good idea to filter the stuff you don't need. E.g. XP Updates if you don't have any XP systems left.

You're welcome




The error seems to indicate that the tool expects the UNC path but it instead has the Direct Access path. Did you try resetting the path to the database using the utility? Be sure to Run as Administrator

And possibly, as I do, actually use the name of the computer.

My filtering is pretty good on WSUS. But, I was rather overwhelmed with it at first. I still prefer just being told there are updates, looking at them and choosing them.

Sandeep: What about checking the .xml file (AmazingCharts.xml) in the AC folder and see what the path is? Of course, it will probably be the E: one. Wonder if you could change it to the one you WANT to do>

The path should bed E:\Amazing Charts\AmazingCharts.mdf\

Is that what is in the .xml file?

Thank you Sandeep & Bert.

Resetting the path was what I suggested to the Guardian Angel, but for some reason he did not want to do that. He is supposed to speak with some "Senior Technical People" today and call me back. I know, I did that once before and AC lost connection to the database and I had to call Guardian Angels. So I am scared to that on my own.

If they don't, I can do it later. No big deal.

You aren't really resetting the path. The path will always have to go to the server or main computer. That path doesn't change. It's just that sometimes the client doesn't "see" or have the right path to the server. Not sure if that makes sense.

Would be really helpful if you could go to the computer with AC, open it, find the AmazingCharts.xml file, open it and copy and paste to here or make a copy and upload it. You won't mess up anything doing that.

There is no problems accessing AmazingCharts.xml from any terminal. The problem now is with accessing "codes" and "meds" database files. Yesterday, I could not get hold of anyone in technical support on the phone. I will try again today.

Do none of them access it? Having meds a problem is not an uncommon issue and has an easy fix (I think). I just can't remember it.

Have you tried uninstalling AC, going to the AC folder that is left, deleting that, then reinstalling?

Yes, the Guardian Angel guy reinstalled AC. Did not fix the problem. I do not know why he did not want to repair. He was supposed to call me back after speaking to "Senior Technical people" on Monday; it is already Wednesday and no one has called me back yet. I called multiple time today but it goes to VoiceMail.

Use the instant chat on the website, it works faster to get help.

Send me a PM if they can't fix it and I can take a look.

There is little doubt that Sandeep will take care of the problem, but just in case you get together tonight, a few thoughts. (Shots in the dark)

1. I know you got rid of 15GB of log files. Do you now have 16.4GBs?
2. What antivirus are you running, and can you turn it off and try to connect?
3. Can you simply turn off your firewall on the server and client?
4. Dumb question, but are your clients the same version as your server?
5. Have you tried Amazing Utilities -> Advanced -> Try #1 and #7.
6. What are the permissions for the folder and the databases especially on meds.mdf and codes.mdf. You should only need permissions on the folder? Are you using Everyone for the share (as Microsoft recommends) and authenticated users or domain users for the security permissions?
7. Could you please open the AmazingCharts.xml file in the main computer's AC folder and copy and paste its contents? There is nothing in the file that should not be seen. I would find that helpful?

Can you give the outcomes to all the questions? Otherwise, it is difficult to troubleshoot.

Thanks.

"Senior Level" Guardian Angels tried again for more than an hour today and could not fix it. They say they have never seen this problem before. So they uploaded "codes" and "meds" databases to their servers and see if the problem is reproduced on their computer. When they find a solution, they will get back with me.

Well that sounds like a waste of time. Why not do #1 as suggested and do an Emergency repair of a corrupted database. Only it wouldn't work would be if it weren't corrupted.

So here is what I would do. I have had to do this before. It worked a couple of times with meds.mdf. This is usually a med.mdf problem. I don't know why. I cut and pasted the meds.mdf database. May as well move the log file as well, meds.mdl except with you it would be the codes as well. It seems like they already took them so you are in better shape.

You have, what, ten other machines? So, you have ten other meds.mdf and codes.mdf along with their companions meds.ldf, etc. Copy and paste them into the AC database. If it is a corruption issue, then you should be all set. You simply will not hurt AC by doing that. If it doesn't work, nuke 'em.

Very interesting. Now I really want to see lol. Then again, it's not the first time I've heard them say that.

SanjeevP,

The thing that is frustrating for me is you have a number of people trying to help, all of which have a better chance of helping you compared with support.

It is helpful to us to be able to offer other suggestions if you try the ones we provide and give the results. Like did you add a codes.mdf and a meds.mdf to see. You have to trust me. YOU CANNOT HURT AC BY DOING THAT. Even if you could, you could always download again.

Did you try uninstalling AND nuking the AC folder which is left behind that contains certain files and folders that can affect AC.

And, the seven other suggestions? Even if none of them work, they allow us to have a better idea of what may be going on.

Thank you for your help, Bert.

Since I have already been working with Guardian Angels, I did not want to try multiple things, at the same time. And yesterday, they solved the problem.

The Guardian Angel uploaded the codes and meds database from his server. He was able to reproduce the problem on his server and said that these databases were corrupted because the first Guardian Angel, who changed the permission on Amazing Charts folder, [after SBS upgrade] forgot to change the permissions on meds and codes database folders. As a result, the main database lost connection with the meds and codes databases. And that is why, the definition check was failing.

So he fixed the problem by uploading these codes and meds databases from his server and then reinstalling Amazing Charts, and changing the permission on all the folders.

I do not understand databases and permissions much, but it seems the lesson is that you have to change permissions on the main Amazing Charts as well as all the subfolders.

As you know, the original problem was that after the SBS 2011 server software update, the clients could not access Amazing Charts database on the server. At that time, first guardian angel found out that the server update reset the permissions and he changed the permission of the Amazing Charts folder and I was able to access the database from the client computers again. After that, check database was failing.

Hi Sanajeev,

Glad you got it fixed. But, please don't take away from this that you have to change the subfolders permissions. When you install a program, all of the subfolders inherit the permissions of the parent folder. Then you use permissions to change access to any subfolder or file.

Say, you install Amazing Charts and everything is working. Everyone has access to it because they have access to the main folder. Then you decide I do not want all my users to have access to the backups. So, you keep the permissions so AC can put the backups in the folder, but you would add certain users to the permissions and deny them access. By denying them access, you don't change your other permissions. Deny always trumps Allow. Say you do the same for imported items. And, you deny users permission to open the folder. But, you want one user to have access, so you change them. These are all under the Security NTFS settings. They look scary because of the amount of permissions there are, but basically, only Full, Read/Write and Read are the ones to worry about.

While you can change the permissions on the actual databases, it is strange that you have to. I doubt there are many, if any, people on here where it doesn't work out of the box.

Happy Holidays