Selecting a template from the list (DOC0200) and clicking OK then the process just hangs. On the application server a winword.exe process gets started but nothing happens, no document is created. If you terminate the winword process on the app server then an error appears in DOC0120. Otherwise you have to crash out of the application and the winword process continues to run on the server. Post resolving above, template did not display either see solution below for fix too.
The main issue with the winword.exe process not completing and eating up processor and all available disk space is resolved by creating two directories. The actual issue is with MS Office Automation on Windows Server 2008. The issue is due to the Microsoft word installed on 2008 r2 server 64 bit server does not create the required directory for system user and due to that winword.exe hangs as runtime user does not have permission to create directory in 64 bit install location.
Creating both directories on application server box resolves this issue. The 64 bit version of Word uses the 32 bit directory and vice versa, so create both directories irrespective of 32 or 64 bit version of Word using to make sure. With this fix I had templates working with 32 and 64 bit version of Word with both directories in place on the application serverC:\windows\system32\config\systemprofile\DesktopC:\Windows\SysWOW64\config\systemprofile\Desktop
This enables the Word process to complete on the application server when invoked through a template association.
Amended an option that appeared on startup of Word to open automatically.
In the application where you see the date field displayed there is a calender icon. Clicking on it displays user preferences HIG1840. Clicked on the user option tab click on document manager, working folder. Populated WORKFOLDER user option to be d:\temp ( a directory on the application server used by webconfig.util)
After Template association took place, selecting Display document did not work.
Looked at the exor.conf file to get to apache aliases.
Noticed that in DOC0118 Document Locations and Media Types the Display URL had a physical directory setting on the application server and not the apache alias. So it couldn't display the associated document in a window. Amended the display URL to reflect the alias in exor.conf file. Also the final slash at the end needed to be a \ not a / (forward slash not a backslash). Once this was done the url worked and document displayed.
You now need to go through all the locations to check set up correctly in live and test systems.
Product TechNotes and FAQs
Bentley Technical Support KnowledgeBase
Bentley LEARN Server
Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!