Go Offline with Microsoft Dynamics CRM 4.0

At a customer, one of their clients couldn't go offline.
After some digging I discovered that the Local Data Group Setup was taking all Accounts. The clients that worked going offline only had a few accounts and none of these accounts had any error. After the Local Data Group on these records were set to all accounts they failed too.
So as the error said that the lenght of customeraddress1 was too long, I looked at the field in both the local SQL Express on the client and on the crm's sql database. On entity Address attribute Address1 was 50 on client and 150 on server SQL.
So i changed the lenght on the client. Look below to see how i found my way through the lenght of attributes.
Still didn't work. Now the error was more generel. Customeraddress couldn't be imported.
I forgot to check for additional attributes that mismatched the lenght in both crm server and client.
Changed postbox and everything worked.

Now, how can this error occur?

The installation on client was a Microsoft Dynamics CRM 4.0 for Outlook with offline capability.
I installed it from www.microsoft.com/downloads with the version where UR7 is included. After successful installation i installed UR9 on top of that, because that was on the server.

I would expect both database schemas to be in sync when the CRM team released new versions to both servers and clients (and srs and data migration manager and email router). But apparently the test before release does not cover all the possible combinations of clients, ur's and servers. Hope that will be better in the future.

To check the schemas for the server and client databases follow the guides from this blog: http://blogs.msdn.com/jannemattila/archive/2008/02/13/comparing-two-databases-schema-and-or-data.aspx

SBS2008: Exchange 2007 stops receiving mails due to low disk space

Resolution
Move queue and queue transaction logs to another disk drive. Description here.


The path to find the answer
First i noticed that mails stopped comming in. Users were complaining about phonecalls from mailsenders that received an administrative mail saying that mails could not be delievered to the address of the exchange server. A quick look discovered lack of disk space. Though this Small Business Server 2008 did have a 60GB partition for the OS.
So then cleaning up the WSUS to only include updates from the actual OS on the clients (aprx. 30 client computers). Then using the cleanup tool (options/cleanup from WSUS server console) freed up 2 GB, wich was enough to let the server receive e-mails again.
Well, a few days later the error occured again. No mails received.
So i digged into the folder sizes using a small console app i build, just to get a list of folder sizes in 2.nd level of folder hierachi. Found winsxs and lost my breath.
Nearly 20GB of assembly files..... Windows side by side are reffered to many places, but it seems as moving the winsxs is not an option.
Back to business: noticed that it the mail stopped comming in when the size was less then 1.5GB. Odd. 'Cause no services stopped. BUT the queues for the Edge Transport didn't have enought space to receive further mails and messages for processing.
So searching for "move queue exchange 2007" came up with the result in the beginning of this post.