GP Crashes when opening Email setup

After designing a Word Template for a client of ours, they were trying to set up the Email Messages and Sales Email Settings.

Dynamics GP kept crashing with the following message:

Microsoft Dynamics GP has stopped working

This particular client is using Dynamics GP 2010 SP3, Office 2010 and Office 365 with a Terminal Server. The crash was happening for all users so I had a horrible feeling that this was due to Office 365 and knew that this is not supported by Microsoft.

My first step was to test using an IMAP account that I had created using my own host and this worked.

I had a ponder about what the difference between my account and their accounts was… both of our accounts were hosted off site.

Once of the differences that I could think of was that my account would not be using an Outlook Data File… maybe it was something to do with that? I decided to remove my IMAP account and set the o365 account back up again. While doing this I had a bit of a flashback from my time on our service desk.

What about Cached Exchange Mode?

I turned Cached Exchange Mode on for this account in the Mail options from Control Panel and tried again and the screens now open in Dynamics GP!

The main difference with cached exchange mode is that, if turned on, the users will have an OST file on the server which will potentially increase in size depending on the users mailbox size. I had a chat with the clients IT provider who is happy for Cached Exchange Mode to be enabled.

Find more information about Cached Exchange Mode here.

Share on Social Media:

Resetting a windows password on Hyper-V

I had created a Virtual Machine using Hyper-V and afterwards found that the password wasn’t working. I’m positive I hadn’t forgotten it, but either way I needed in to that virtual machine!

After doing a bit of a looking around, I found that there is a bit of an exploit that allows you to change the Accessibility button on the login screen to open a command prompt. This allows you to open this and use the ‘net user’ commands to create users, change passwords etc.

To do this, you need to boot into the windows recovery options (command prompt) from a windows CD.

You then rename utilman.exe and copy cmd.exe as utilman.exe – clever in this case but something to be aware of as this makes it pretty easy for other people to get into your systems.

You can read the original tutorial here!

Remember to change the utilman.exe back when you’re done.

Share on Social Media: