Outlook failed to start correctly last time. – and it goes on forever!!

I had this problem a about half a year ago where Outlook 2003 on terminal server would come up with a safe mode message for every user everytime they started it. At the time i solved the problem however a few weeks ago it came back and I couldn’t for the life of me remember how to fix it.

One of the uses of my blog is to document any bits of obscure IT related problems and their solutions so that if they happen to me again in the future i can just look up the solution without having to trawl google and waste time sifting through all the crap. Kinda like an IT helpdesk knowledgebase but for me.

So here goes:

When using Outlook 2003 on a Windows 2000 terminal server, you may receive the following error:

Outlook failed to start correctly last time. Starting Outlook in safe mode will help you correct or isolate a startup problem in order to successfully start the program. Some functionality may be disabled in this mode.

Do you want to start Outlook in safe mode?

No matter what you click Outlook opens – Yay.

No! The next time you launch Outlook you get the prompt again. And so on….

This is because when Outlook 2003 crashes or fails to load, the program generates this error message when you restart it. Safe Mode is a special operating mode that disables several of Outlook’s features but at least lets the program load so you can see existing emails and access other elements of the software.

What is happening here is that the program is not clearing the entry in the computer’s registry so it continues to display the error message.

To fix the problem you need to go into the registry on the server and do a search for “Resiliency” there will be quite a few entries (dependant on the number of terminal server users), you need to delete every entry that referrs to Outlook it should be something along the lines of:

HKLM\Software\Microsoft\Windows NT\Current Version\Terminal Server\Install\Software\Microsoft\Office\11.0\Outlook\Resiliency

and

HK_USERS\S-x-xxxx….\…..\Software\Microsoft\Office\11.0\Outlook\Resiliency

Once these keys have been deleted the message should go away.

Terminal Server protocol error

Sometimes we have a problem with Windows Update and Terminal server that messes with the protocol causing the following error:

The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator.

To fix this simply do the following:

  1. On the client, navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.
  2. Click MSLicensing.
  3. On the Registry menu, click Export Registry File.
  4. In the File name box, type mslicensingbackup, and then click Save.
  5. If you need to restore this registry key in the future, double-click mslicensingbackup.reg.
  6. On the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey.
  7. Close Registry Editor, and then restart the computer.

When the client is restarted, the missing registry key is rebuilt.

Reccurring DNS Error

I have had a reccuring DNS error on our SBS server for quite some time now. I’m not too sure how it came about but i suspect it was something to do with removing a member server that was acting as a second domain controller. The error was:

Event Type:    Error
Event Source:    DNS
Event Category:    None
Event ID:    4000
Date:     18/07/2008
Time:     06:38:39
User:    N/A
Computer:Â Â Â SBS01
Description:
The DNS server was unable to open Active Directory. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code.

Long story short, i had a duplicate zone in my dns server that was empty – all i needed to do was remove it and restart a few service an hey! no error.

the zone was _msdcs under mydomain.com – it was greyed out with nothing inside it. I had another copy of thiszone above it called _msdcs.mydomain.com which had all the right data in it.

  1. So i deleted the empty _msdcs entry
  2. at a command propmt ran: net stop netlogon
  3. then: ipconfig /flushdns
  4. then restart the DNS server
  5. then run: net start netlogon
  6. and finish with: ipconfig /registerdns

No more error in 6 easy steps! 🙂

Terminals

There is something quite satisfying about using command line to resolve an issue on a remote machine instead of logging into a remote desktop session. Might have to start playing with Linux again…
—————-
Now playing: Brand New – Degausser
via FoxyTunes

Adding new file associations to terminal server 2000

I had an issue with TIF images not opening in the correct application on our 2000 Terminal Server. Simple fix: Right Click on the file, go to properties a Click the change button next to Opens with: text.

TSE File Association 01

Except it’s not there!! Don’t panic, this is on purpose!

A quick google and i found the solution:

On computers running Windows 2000 Terminal Services in Application Server mode, the UI may be locked down so that no one can change file type associations (not even administrators). This is done so that you can only edit the entries programmatically or by using MSI-based applications. This ensures that an inadvertent change in the UI does not effect the global file type associations across the computer running Terminal Services and all of its users. When this policy is enabled, the New, Delete, Change, and Advanced buttons are unavailable on the File Types tab of the Folder Options tool in Control Panel. You can enable this functionality by changing the following registry entry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer] “NoFileAssociate”=dword:00000000

One thing i would suggest is that you set the dword back to 1 after you have made your changes to keep things safe.

164 Memory Error

Just a quick note about something that has just cropped up: I was upgrading one of the really old machines at work with some PC133 SIMMS i found in another dead machine.

After upgrading the memory, it came up with an 164 Memory Error and wouldn’t boot no further!

Don’t panic though, it is just a bios message that tells you that the memory configuration has changed. All you need to do is restart that machine a few times and it will become happy with it’s new memory!

You can find a list of codes here:

http://www-304.ibm.com/…

—————-
Now playing: Incubus – Leech
via FoxyTunes

Developing an Extranet

One of our clients has been doing a little bit of reading and now wants a web 2.0 site with all the buzz words under the sun!

The original request was something like “Company Extranet/Blog with AJAX driven dynamic content on an open source platform!!” – I suppose a little knowledge IS dangerous. Lol

—————-
Now playing: Incubus – Megalomaniac
via FoxyTunes

Google Maps Mobile

Just got my new PDA for work and was messing around with it and came across this little article about using google maps with it’s built in sat nav. Have to say it works a treat – just need to work out a way to cache all the maps on a memory card so that i can use it in areas with low data transfer rates.

http://googlesystem.blogspot.com/2007/11/google-maps-for-mobile-shows-your.htm

google maps mobile

might post a review of the pda compared to my old one later…

—————-
Now playing: Audioslave – Set It Off
via FoxyTunes