We help IT Professionals succeed at work.
Get Started

Office 2003 automation Problem with Access/Word 2003, running via Terminal Services, on a Windows 2008 Server OS, intermittently the instance of WinWord is not terminating when Word is exited.

892 Views
Last Modified: 2012-05-09
A user’s workstation has icon to log on, via Terminal Services, to a Terminal Services Windows 2008 Standard Server OS session.

The MS-Access application creates an instance of Word and populates the Word document.    The user may print the document then exit Word.

Most of the time the instance of WinWord terminates, verified by using task manager, when the Word document has been exited.

However, there are intermittent times the instance of WinWord does not terminate AND the document has already been exited.

When the instance of WinWord is still running, and the code gets to the statement    set WordObj = nothing     Access appears to lock up or waiting on the WinWord application (described below).    

------------------------------------------------
Below are code snippets of setting the WordObj, where the code seems to stop


------------------------------------------------
Definition
------------------------------------------------
   Global WordObj As Word.Application


------------------------------------------------
Clearing and setting the WordObj
------------------------------------------------
   Set WordObj = Nothing   <<- the statement executing (found by logging each line of code)

   Set WordObj = CreateObject("Word.Application")


------------------------------------------------
The error information from Terminal Server/Windows 2008 Server received after using Task Manager to terminate one of the Access Forms.
------------------------------------------------

*******************************************************
Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name:      AppHangXProcB1
  Application Name:      MSACCESS.EXE
  Application Version:      11.0.5614.0
  Application Timestamp:      3f3c8e3c
  Hang Signature:      c395
  Hang Type:      6208
  Waiting on Application Name:      WINWORD.EXE
  Waiting on Application Version:      11.0.5604.0
  OS Version:      6.0.6001.2.1.0.16.7
  Locale ID:      1033
  Additional Hang Signature 1:      754e06a0835a2392471709b960293e34
  Additional Hang Signature 2:      edcc
  Additional Hang Signature 3:      2d4ef58a582a9d5f527a5b6561729810
  Additional Hang Signature 4:      c395
  Additional Hang Signature 5:      754e06a0835a2392471709b960293e34
  Additional Hang Signature 6:      edcc
  Additional Hang Signature 7:      2d4ef58a582a9d5f527a5b6561729810

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
***********************************************************



Does any of this have to do with using Office 2003 automation on a Windows 2008 Server?


Comment
Watch Question
This problem has been solved!
Unlock 2 Answers and 18 Comments.
See Answers
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE