Office 2003 and Windows 2008 Terminal Server

try to reinstall MS Offie on that machine.
Check logs for error details

I have already done this and did not help. Is Office 2003 compatable with 2008 server running terminal services?

You should be able to see some error logs in the even viewer, please post them here for further details on this.

The problem is primarly happening to user ktuggle
Below are three of the errors

Faulting application name: OUTLOOK.EXE, version: 11.0.8326.0, time stamp: 0x4c1c2372
Faulting module name: windowscodecs.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba3a
Exception code: 0xc0000005
Fault offset: 0x00001f9d
Faulting process id: 0x1750
Faulting application start time: 0x01cd83002f077084
Faulting application path: C:\PROGRA~2\MICROS~2\OFFICE11\OUTLOOK.EXE
Faulting module path: C:\Windows\system32\windowscodecs.dll
Report Id: 6e789e64-eef3-11e1-b8bd-bc305be92914

Fault bucket 1811371536, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: OUTLOOK.EXE
P2: 11.0.8326.0
P3: 4c1c2372
P4: windowscodecs.dll
P5: 6.1.7601.17514
P6: 4ce7ba3a
P7: 00001e01
P8: c0000005
P9: 00000008
P10:

Attached files:
C:\Users\ktuggle\AppData\Local\Temp\3\34001369.cvr
C:\Users\ktuggle\AppData\Local\Temp\3\WERD275.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\ktuggle\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_OUTLOOK.EXE_e8d5cf25f1dd9118aa14df884e8abffa43d7386_1d6ee5f5

Analysis symbol:
Rechecking for solution: 0
Report Id: 67b84174-eef3-11e1-b8bd-bc305be92914
Report Status: 0

Faulting application name: OUTLOOK.EXE, version: 11.0.8326.0, time stamp: 0x4c1c2372
Faulting module name: windowscodecs.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba3a
Exception code: 0xc0000005
Fault offset: 0x00001e01
Faulting process id: 0x1438
Faulting application start time: 0x01cd830026a28b54
Faulting application path: C:\PROGRA~2\MICROS~2\OFFICE11\OUTLOOK.EXE
Faulting module path: C:\Windows\system32\windowscodecs.dll
Report Id: 67b84174-eef3-11e1-b8bd-bc305be92914

Try  turning off Data Execution Prevention (DEP). to do so:
Go to Control Panel > System > Advanced System Settings > Performance:Settings button > Data Execution Prevention tab
Select the first option: Turn on DEP for essential Windows programs and services only
Changing the setting won't require a reboot, from memory, but you might want to anyway just to be safe, as a lot of things will already be loaded and running.

I will give this a try and see what happens. Since it does not happen everyday I will go ahead and accept as a solution and reopen if it does not work.  Thank you very much

I've requested that this question be closed as follows:

Accepted answer: 0 points for Ron-mds's comment #a38336536

for the following reason:

Great response

@Rod.
You are closing the question! You could try my suggestion first and if it didn't work you can close the question.

Thank you

Switching off DEP can be a temporary workaround, but is a bad idea to leave it that way. If DEP prevents execution of code, the code is failing - nowadays no code is allowed to change its own code segment (memory area) while running, or execute code stored in (volatile) data segments, for security reasons.

Instead of fiddling with DEP, we should look into the real issue - WindowsCodecs.DLL is faulting, which means decoding MIME parts of mails. This is often caused by corrupted system files. Try if   sfc /scannow   will repair something. If not, there might be particular mail contents causing the crash, and it is a bug needing a hotfix (something only MS will know).

It was not my my intent to close without awarding points. I will also try the scan mentioned about. If I need to reopen to award points please advise

Looking at the above, turning off DEP is not going to help since its not available in outlook 2003

I see you have an office 2007 compatibility pack installed?
Is this the one provided by microsoft or another vendor?

usually when you get this error, it due to a Faulty add in in Outlook
Not becuase of outlook

You can test this simply by opening outlook using
Start>Run>Outlook.exe /safe

If you dont get the error we then know its an add in

Close outlook

We can then go to the Registry at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins

Note the add ins and their current behavior
Once done set one of the behaviors to 0

Now open outlook and test
Do you still get the error?

If you do, repeat untill you have disabled the faulting add in

ONce you have located the faulting add in
Set the other add ins back to their origianl behaviors

You can leave the faulting add in diabled, or look to the vendor or supplier for an update

Qlemo, the code execution is failing because of comparability issue between windows and outlook application.

@moh10ly -
If there is a compatibility problem between a Microsoft product and a Microsoft OS, I don't think turning off one of the protection features is a proper solution. Much better to simply add outlook.exe to the DEP "exception" list.

Do you have a source for your suggestion to disable DEP? I would like to read more about this problem.

@apache09 -
Data Execution Prevention (DEP) is a function of the Windows OS (since XP, SP2), not the Microsoft applications, such as Outlook 2003, etc.

@Younghv
There are some comparability issues which has been resolved after SP3. Adding outlook.exe is an option as well.

http://support.citrix.com/article/CTX124653

I forgot to mention if the user has latest patches installed for Office. Installing latest updates will probably solve the problem.

@moh10ly -
The link you provide refers to the Citrix "XenApp" function. I don't see any indication that this asker is running that - and it says nothing about disabling the DEP.

We are running SP3 and I have turned DEP back on but excluded Outlook. Now we wait to see if it fails again

I was just pointing to the comparability between the Office and Windows OS 2008 not the DEP.

The DEP recommendation is made by one of the contributes to Microsoft forums about a comparability issue between VB6 and OS 2008.

Google it if ur so eager to know where did I get the link.

This is a very odd problem an only happens occasionally. I found some odd programs that had been installed on the server and have removed them. Hopefully this will solve the problem. I assume another option would be to purchase Outlook 2010 and install on the 2008
terminal server. The client does not want to purchase a complete Office 2010 version due to the cost.

moh10ly -
Let's discuss this further - off-line and in private.
https://www.experts-exchange.com/PD/541.html

When choosing the above like I get a Permission Denied messge

@Ron-mds -

When choosing the above like I get a Permission Denied messge

I don't know what you are saying there.
===========

I tend to agree with your customer about not upgrading. Even though I have free licenses to all MS products, I'm still running Office 2003 on all my systems.

Some day I will upgrade, but can't be bothered with the learning curve right now - and Office 2003 works on all the OS's I run.

I hope the exception rule solves this for you - and please take a look at the comments from Qlemo (http:#a38338923) for a more thorough examination of the problem.

@Ron-mds

Could you please tell when does the outlook stop working? Is it when you navigate pictures within e-mails ?

Windowscodecs.dll library seems to be involved in image data mostly so I would suppose the problem is related to Image attachments within some of your e-mails ?