There was a problem sending the command to the program

[qasimali84]

Hi



I have issue on few client's machines where Network printer is installed and selected as Default Printer. When user power on his workstation and try to open MS Word document. He received the error message "There was a problem sending the command to the program"

In event viewer following error is logged

Category: Microsoft Office 12 Session

Error Code: 7003

Error Description: ID:0 Application Name: Microsoft Office word, App Version 12............. This session was terminated unexpectedly



It has been experienced that if user wait for 1-2 minutes after desktop loading and try to open word document, it work fine. But application (MS Word) crashes when he open with out wait.



I have following infrastructure

Operating System on client machine: Windows 7 Professional

Office on client machine: Office 2007 Professional

eDraw component installed on client machine used in web based application

Active Directory: Windows Server 2008 Ent SP1
Print Server: Windows Server 2008 Ent SP1
Juniper Firewall

Waiting for reply please

[macropod]

There are numerous possible causes for that error message.

The first thing to try is repairing the Office installation (via Windows Control Panel > Programs > Programs & Features > Microsoft Office (version) > Change > Repair).

You might also run the System File Checker, via:
sfc /scannow
as an Administrator from a Command prompt to validate your system files.

If that doesn't correct the problem, it might be caused by a faulty Addin. In that case, try stating Word in Safe Mode (i.e. hold down the Ctrl key while starting Word). If that corrects the problem, the issue is due to a faulty Office addin. Re-start Word normally, then disable all Addins. Log out then log in again and re-start Word normally. If the problem disappears, it was due to a faulty Addin. Re-enable one Addin, then log out, log in again and re-start Word normally. If the problem doesn't occur, re-enable another Addin. Keep doing this until the problem recurs; when it does, the last-enabled addin is the likely culprit. Permanently disable that Addin or replace it with the latest version.