Saved for later reference » quick

“Microsoft Dynamics CRM for Outlook with Offline Access has already been configured for a user on this computer. Only one use can be configured per computer for Microsoft CRM for Outlook with Offline Access.”

Lars Erik Jordet — Fri, 03 Sep 2010 11:46:57 +0000

If you try to swap users on a laptop, with Dynamics CRM installed in Offline Access mode, it will give the error above; searching gave me this page from the Chinese Dynamics CRM team, so I’m just going to repeat it here:

1
2
3
4

C:\>osql –E –S localhost\CRM
1> drop database mscrm_msde
2> go
1> quit

Basically, you connect to the SQL Server on the local computer, and delete the Offline Access database, allowing you to reconfigure as normal. Note that this won’t let you reconfigure the user as “online only” – the new configuration will automatically be Offline Access.

Secondly, this works even if the user is not Local Administrator on the computer.

Script to add a network printer automatically in Windows

Lars Erik Jordet — Tue, 24 Aug 2010 08:47:04 +0000

I recently had to replace a defective printer with a similar model, but different enough to need a new driver. This meant it would have a new name on the print server, and I had to figure out a way to replace the installed printer on each computer quickly. After some searching, I ended up with the following script:

1
2
3
4
5
6

@echo off
set OLDPRINTER="\\printserver\Xerox Phaser 8560N"
set NEWPRINTER="\\printserver\Xerox Phaser 8560DN PS"
rundll32 printui.dll,PrintUIEntry /q /dn /n%OLDPRINTER%
rundll32 printui.dll,PrintUIEntry /in /n%NEWPRINTER% /q
rundll32 printui.dll,PrintUIEntry /y /n%NEWPRINTER%

The first rundll32 line quietly (/q) deletes (/dn) the printer named (/n) %OLDPRINTER%, while the second line installs (/in) the new printer %NEWPRINTER%, and the final line sets the new printer as default (/y)

Active Directory user GUID

Lars Erik Jordet — Tue, 06 Jul 2010 13:26:36 +0000

I found this page which contains an old oneliner to get a user GUID in PowerShell – but sadly it doesn’t work anymore.

After some tricking around, I found the following to work:

1	(new-object Guid(,(([directoryservices.directorysearcher] "(samaccountname=theuser)").findall())[0].properties["objectguid"][0])).ToString()

MS Dynamics CRM installation: ASP.NET 2.0 is not installed

Lars Erik Jordet — Mon, 05 Jul 2010 12:46:22 +0000

I got this error message on a server while installing Dynamics. At first I thought the problem was that my IIS is running 64 bit .NET 2.0 (I’ve had problems with that in the past), but it turns out that the actual problem is that .NET 4.0 was installed.

This guy figured out what the problem is: The installer checks for a specific filter in the IIS settings, which doesn’t exist when .NET 4.0 has been installed.

I’ll repeat the fix here, hopefully making this a bit more “discoverable” by search engines (searching the exact error message gave me nothing helpful, just tips about running aspnet_regiis.exe -i repeatedly):

In IIS Manager, right click Web Sites, and select Properties.

Under ISAPI Filters, Add a new filter you call ASP.NET_2.0.50727, pointing to C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_filter.dll (assuming 64 bit server, otherwise substitute Framework for Framework64).

Dynamics should now install without issue.

“Couldn’t generate the upgrade script.” for version C.0.8.40 of MS SQL Reporting Services

Lars Erik Jordet — Mon, 05 Jul 2010 08:51:42 +0000

The error message “Couldn’t generate the upgrade script” pops up during configuration of Reporting Services for MS SQL Server 2005, if you install reporting services after installing a service pack – in my case Reporting Services was installed as SP1, while the main SQL Server 2005 install was updated to SP3.

Reinstalling SQL Server 2005 SP3 fixed it.