Archive for February, 2012

I recently logged a call with Quickbooks South Africa (4th of Jan 2012)  with a problem I had getting my Quickbooks 2010 company file to upgrade to Quickbooks 2012.

After being advised to uninstall and reinstall the program and a whole string of other problems they came to the conclusion that they cannot assist me.

Thereafter I contacted the Quickbooks UK offices.  I advised them that I had spoken to the local Quickbooks office and that they could not help me.  They again took me through the same procedures of uninstalling and reinstalling the product.  Still no resolution.  I then waited about a week before they got back to me.  A support representative connected to my computer and redid all the diagnostics steps that had already been tried, including uninstalling .NET etc.  Still no resolution.  He then took a copy of my company file and advised that it could take up to 2 weeks before they got back to me.

Last night I received an e-mail from them:

I am writing to you regarding the QuickBooks Version 2010 Release 4 Company File send for review and received on Jan 17th, 2012.

As I understand it, you are unable to upgrade your QuickBooks version 2010 Company data file to version 2012 as it crashes during the upgrade process.

I have reviewed your file. I am able to upgrade the file to version 2012 if I shorten the business number.

The business number you have entered is 16 characters including numbers, alphabets, special characters and spaces. If you shorten it to 15 characters you should be able to upgrade it to version 2012.

Open the file in Version 2010, Go to the Company Menu and choose Company Information.

On the Company Information window, Click on the Business Number and shorten it by a character. I had removed one of the slash. You may want to remove some other character. But please make sure that the Business Number is not longer than 15 characters including numbers, alphabets, special characters and spaces. Click on OK to Save the Change.

Go back to the Company Menu and go to Company Information to ensure that the change was saved.

You can now upgrade the corrected file to version 2012 and it should upgrade without any issues.

I did as advised and my company file has been successfully upgraded to 2012.

I’m very happy that the problem has been resolved, it’s just horrific that it took a WHOLE MONTH to resolve such a silly problem.  One would think that the programmers would have been able to put some sort of validation in the software to prevent this type of data validation issue.

Need a quick and dirty way to check the size of all users’s Deleted Items in your Exchange Mailbox Database – here is a nifty powershell script I concocted from a variety of other scripts on the net.

C:\Windows\system32>Get-Mailbox -ResultSize unlimited | Get-MailboxFolderStatistics | where{$_.FolderType -eq "DeletedItems"} | Select-Object Identity, {$_.FolderAndSubFolderSize.ToMb()}, ItemsInFolderAndSubFolders | Export-Csv c:\deleted_items.csv

It exports the data to a CSV file on the root of the C: drive (deleted_items.csv).

You can open this in Excel and easily use the SUM function to get a total of all the users’s Deleted Items folders.

(I wrote this on an Exchange 2010 server, it should work on Exchange 2007 also, but I haven’t tested this on Exchange 2007.)

Moving the database (SUSDB)

The following instructions are for moving the SUSDB and should be valid irrespective of if you are using SBS or WSUS as a standalone product.

As with a regular SQL Server datastore, you can detach and move the database.

Since the database is a normal SQL database, you can simply detach, move and reattach the database. In order to do this, you will however need some tools. Note that these tools are not part of the operating system, so if you haven’t already installed them previosly, then you will need to do so now.

The tools you need are eith SQL Server Managment Studio or SQL Server Management Studio Express. At the time of writing the express (free) version can be downloaded from here:
SQL 2005:
SQL 2008:
or search on Google if the above links aren’t valid.
Please download the correct version for your platform (x86 or x64) – Note that SBS 2008+ is ALWAYS x64.

NOTE: You can also download and use the command line tools instead of the full management studio. (If you are familliar with these tools and their usage, then these instructions will probably be a piece of cake for you.)

Command line tools:
sqlncli.msi and SQLServer2005_SQLCMD.msi (Search for them on Google or Microsoft Download)

Prior to moving the database, please stop the following services:

  • IIS Admin Service
  • Update Services (Not Windows Update Service!).

You can do this via the commandline or by using the Services MMC snap-in (start run, services.msc).

Command line:

net stop "update services"
net stop w3svc

(Once the database has been moved you will need to restart these services. Also note that if you have any other services which are dependant on the above services – such as Terminal Services Gateway – they will also be stopped and will need to be restarted.)

Once the services have been stopped, you can proceed to detach the database.

Via SQL Server Management Studio (or Express):

  • Login to server as an administrator.
  • Click Start/Programs/Microsoft SQL Server 2005/SQL Server Management Studio Express. (NOTE: If you are not logged in as Administrator, Right click on SQL Server Management Studio and select Run As Administrator.)
  • Fill in the following information and then click Connect
    • Server type: Database Engine
    • Servername: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
    • Authentication: Windows Authentication
  • Expand Databases, right-click on SUSDB and select Tasks > Detach…  (Please continue reading before proceeding with this step, unless you are 100% sure where your current SUSDB files are located.)
  • Select the “Drop Connection” checkbox and click OK.  (There shouldn’t be any open connections as we have stopped all the relevant services.)
  • Move C:\WSUS\SUSDB folder to the <new drive>:\WSUS directory.  (Assuming that your SUSDB is currently located here – otherwise you can check where it is located prior to detaching the database by viewing it’s properties.)
  • To reattach the database, right-click on Database and select Attach…
  • On the Attach Databases page select the Add button.
  • Browse to the new location of the SUSDB and click OK twice to complete task

Via command line:

  • Login to server as administrator
  • To detach the database:
    c:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLCMD.EXE" -E -S np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -Q "sp_detach_db 'SUSDB'
  • Now move the SUSDB.mdf and SUSDB.ldf to their new location. In the example below, we use D:\WSUSDB\. Use explorer to move the files to the path you’d like.
  • Then we reattach the database:
    c:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLCMD.EXE" -E -S np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -Q "sp_attach_db @dbname=N'SUSDB',@filename1=N'E:\WSUSDB\SUSDB.mdf', @filename2=N'D:\WSUSDB\SUSDB_log.ldf'

Moving the content folders (SBS 2008+):

  • Start the Windows SBS Console
  • Click on the Backup and Server Storage icon
  • Click on the Server Storage Tab
  • Select Move Windows Update Repository Data (Right hand side)

Moving the conent folders (non SBS):

The “movecontent” command:

C:\Program Files\Update Services\Tools\wsusutil.exe" movecontent [newpath] [logfile]

For example:

C:\Program Files\Update Services\Tools\wsusutil.exe" movecontent \\server\WSUS$\ c:\wsusmove.log
C:\Program Files\Update Services\Tools\wsusutil.exe" movecontent D:\WSUS c:\wsusmove.log