Re: Word 2007 on term session - "Word could not create the work file"

Was the TS in install mode during installation of Office?

Here's a KB article that describes your problem, albeit for Word
2000:

WD2000: "Word Cannot Create the Work File" Error Message When You
Open a File
http://support.microsoft.com/?kbid=302629

I would have a hard look at the Data subkey in the registry.
The location of the Data subkey for an individual user should be:
HKCU\Software\Microsoft\Office\x.0\Word\Data

If you find that this key is wrong or missing for all users, you
might have to update/add the shadow key in the Terminal Services
section of the HKLM part of the registry, i.e. in
HKEY_LOCAL_MACHINE\Software
\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install
\Software

Do this by starting Word as administrator while you're in install
mode and making some changes on the Tools - Options menu.
Since you thereby update the timestamp on the shadow key, all
users will get a fresh copy of the shadow key into their HKCU part
of the registry, so you won't have to modify/add all individual
\Data subkeys.

And while you're at it, also check the value of
HKCU\Software\Microsoft\Windows\Current Version\Explorer\User Shell
Folders\Cache

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?VEtvdmFjcw==?= <TKovacs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 23 jan 2008 in microsoft.public.windows.terminal_services:

I have a fresh install of Win2003 R2 x64 and MS Office 2007.
Non-administrative users who open Word get an error that reads
"Word could not create the work file. Check the temp environment
variable."

User environment variables:
TEMP = %USERPROFILE%\Local Settings\Temp
TMP = %USERPROFILE%\Local Settings\Temp

System environment variables:
TEMP = (was) %systemroot%\temp (now changed to) C:\TEMP
TMP = (was) %systemroot%\temp (now changed to) C:\TEMP

I've checked the temp environment variable until I am blue in
the face. I've googled for answers and found nothing helpful.
In desparation I even attempted to call Micro$oft, who dispite
this software being purchased as part of a $40K eopen volume
license with SA, still wants another $250 to explain why this
POS will not work correctly on a clean install. Joe blow with a
single copy of Office at least gets 90 days of no-charge
support. Really tees me off......

Anyone have this problem and figured out how to solve it?

Thanks

Ted
.

Relevant Pages

  • RE: Client login on TS triggers msiexec.exe problem
    ... I do not understand why the shadow key section in these 2 TS should be at ... in using the same account on the TS, meaning I'm loading up the same HKCU ... You could also logon as a new administrative account, go into install mode ... Do I need to put the TS in install mode before I run for example Microsoft ...
    (microsoft.public.windows.terminal_services)
  • RE: Client login on TS triggers msiexec.exe problem
    ... The shadow key is NOT a requirement, ... Virtual Client Solutions ... Do I need to put the TS in install mode before I run for example Microsoft ...
    (microsoft.public.windows.terminal_services)
  • Re: Warp Rogue - SDL help wanted
    ... and the JRE isn't trivialy sized either. ... install those wierd things". ... environment variables, ... GodMode: Boolean = False; ...
    (rec.games.roguelike.development)
  • Re: BlackIce security questions
    ... the BlackIce ccd release thread. ... Re-apply power to the PC and install in regular ... Install Mode will stay in memory for 3 minutes. ... the baseline to include the files that have been created or modified. ...
    (comp.security.firewalls)
  • RE: Environment issues Please help
    ... install an MSI if not installed ... This is becourse the vbscript doen't expands the new installed windows ... It will: 1- wright to registry ... To add and to ACTIVATE new environment variables you need a thirdparty tool ...
    (microsoft.public.scripting.vbscript)