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

[TKovacs]

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

 

[Vera Noest [MVP]]

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@discussions.microsoft.com> 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

 

[TKovacs]

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

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

Vena -- Thanks, but no luck so far.

Before I respond, I should also add what else I have figured out. I thought
the problem was on all non-admin accounts. As it turns out, newly created
non-admin accounts are fine. The error only occurs for pre-existing
non-admin accounts. We do use roaming TS profiles. On the old server, the
USERPROFILE path was on the C: drive, and on the new server it is on the D:
drive.

I've got a suspecion that Word is trying to create a temp file in a folder
on C:\Documents and Settings\<userprofile> (which does not exist on C when
it should instead be in Documents and Settings on the D: drive. But, I'll be
damned if I can figure out where the problem is. Obviously it is not a
system environment variable. User environment variables match on both
working and non-working accounts, so thats out. It must be a setting
somewhere in HKLM contained within the users TS profile. I'd hate to have to
re-do everyones profile from scratch just because of this.

- I tried deleting the data subkey and letting Word recreate it
- HKCU\....\User Shell Folders\Cache looks good
- Yes, it was in install mode.

Ted


"Vera Noest [MVP]" wrote:

> 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@discussions.microsoft.com> 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
>

 

[Vera Noest [MVP]]

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

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

If you start Word as one of the users who does have the problem,
and then go to Tools - Options - File locations, is the path
correct there?

_________________________________________________________
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@discussions.microsoft.com> wrote
on 23 jan 2008 in microsoft.public.windows.terminal_services:

> Vena -- Thanks, but no luck so far.
>
> Before I respond, I should also add what else I have figured
> out. I thought the problem was on all non-admin accounts. As
> it turns out, newly created non-admin accounts are fine. The
> error only occurs for pre-existing non-admin accounts. We do
> use roaming TS profiles. On the old server, the USERPROFILE
> path was on the C: drive, and on the new server it is on the D:
> drive.
>
> I've got a suspecion that Word is trying to create a temp file
> in a folder on C:\Documents and Settings\<userprofile> (which
> does not exist on C when it should instead be in Documents
> and Settings on the D: drive. But, I'll be damned if I can
> figure out where the problem is. Obviously it is not a system
> environment variable. User environment variables match on both
> working and non-working accounts, so thats out. It must be a
> setting somewhere in HKLM contained within the users TS profile.
> I'd hate to have to re-do everyones profile from scratch just
> because of this.
>
> - I tried deleting the data subkey and letting Word recreate it
> - HKCU\....\User Shell Folders\Cache looks good
> - Yes, it was in install mode.
>
> Ted
>
>
> "Vera Noest [MVP]" wrote:
>
>> 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@discussions.microsoft.com>
>> 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

 

[TKovacs]

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

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

Yes. All those paths are correct. Also, all paths listed when using the SET
command at a command prompt are also correct.

Ted

"Vera Noest [MVP]" wrote:

> If you start Word as one of the users who does have the problem,
> and then go to Tools - Options - File locations, is the path
> correct there?
>
> _________________________________________________________
> 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@discussions.microsoft.com> wrote
> on 23 jan 2008 in microsoft.public.windows.terminal_services:
>
> > Vena -- Thanks, but no luck so far.
> >
> > Before I respond, I should also add what else I have figured
> > out. I thought the problem was on all non-admin accounts. As
> > it turns out, newly created non-admin accounts are fine. The
> > error only occurs for pre-existing non-admin accounts. We do
> > use roaming TS profiles. On the old server, the USERPROFILE
> > path was on the C: drive, and on the new server it is on the D:
> > drive.
> >
> > I've got a suspecion that Word is trying to create a temp file
> > in a folder on C:\Documents and Settings\<userprofile> (which
> > does not exist on C when it should instead be in Documents
> > and Settings on the D: drive. But, I'll be damned if I can
> > figure out where the problem is. Obviously it is not a system
> > environment variable. User environment variables match on both
> > working and non-working accounts, so thats out. It must be a
> > setting somewhere in HKLM contained within the users TS profile.
> > I'd hate to have to re-do everyones profile from scratch just
> > because of this.
> >
> > - I tried deleting the data subkey and letting Word recreate it
> > - HKCU\....\User Shell Folders\Cache looks good
> > - Yes, it was in install mode.
> >
> > Ted
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> 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@discussions.microsoft.com>
> >> 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
>

 

[Vera Noest [MVP]]

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

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

Then I would use ProcessMonitor. Start it on the TS as
administrator (when no other users are logged on, then let one of
the users with the problem logon and start Word. ProcessMonitor
should show you every registry key and file that Word tries to
open. You can filter the output on ACCESS DENIED and PATH NOT FOUND
errors.

Download here:
http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/p
rocessmonitor.mspx

_________________________________________________________
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@discussions.microsoft.com> wrote
on 23 jan 2008 in microsoft.public.windows.terminal_services:

> Yes. All those paths are correct. Also, all paths listed when
> using the SET command at a command prompt are also correct.
>
> Ted
>
> "Vera Noest [MVP]" wrote:
>
>> If you start Word as one of the users who does have the
>> problem, and then go to Tools - Options - File locations, is
>> the path correct there?
>>
>> _________________________________________________________
>> 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@discussions.microsoft.com>
>> wrote on 23 jan 2008 in
>> microsoft.public.windows.terminal_services:
>>
>> > Vena -- Thanks, but no luck so far.
>> >
>> > Before I respond, I should also add what else I have figured
>> > out. I thought the problem was on all non-admin accounts.
>> > As it turns out, newly created non-admin accounts are fine.
>> > The error only occurs for pre-existing non-admin accounts.
>> > We do use roaming TS profiles. On the old server, the
>> > USERPROFILE path was on the C: drive, and on the new server
>> > it is on the D: drive.
>> >
>> > I've got a suspecion that Word is trying to create a temp
>> > file in a folder on C:\Documents and Settings\<userprofile>
>> > (which does not exist on C when it should instead be in
>> > Documents and Settings on the D: drive. But, I'll be damned
>> > if I can figure out where the problem is. Obviously it is
>> > not a system environment variable. User environment
>> > variables match on both working and non-working accounts, so
>> > thats out. It must be a setting somewhere in HKLM contained
>> > within the users TS profile.
>> > I'd hate to have to re-do everyones profile from scratch
>> > just
>> > because of this.
>> >
>> > - I tried deleting the data subkey and letting Word recreate
>> > it - HKCU\....\User Shell Folders\Cache looks good
>> > - Yes, it was in install mode.
>> >
>> > Ted
>> >
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> 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@discussions.microsoft.com>
>> >> 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

 

[TKovacs]

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

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

Thanks. I'll try that. I did try filemon and regmon thinking that would be
the ticket, but the copies I have of those apps wouldn't function on the
Win2003 R2 x64 server.

"Vera Noest [MVP]" wrote:

> Then I would use ProcessMonitor. Start it on the TS as
> administrator (when no other users are logged on, then let one of
> the users with the problem logon and start Word. ProcessMonitor
> should show you every registry key and file that Word tries to
> open. You can filter the output on ACCESS DENIED and PATH NOT FOUND
> errors.
>
> Download here:
> http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/p
> rocessmonitor.mspx
>
> _________________________________________________________
> 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@discussions.microsoft.com> wrote
> on 23 jan 2008 in microsoft.public.windows.terminal_services:
>
> > Yes. All those paths are correct. Also, all paths listed when
> > using the SET command at a command prompt are also correct.
> >
> > Ted
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> If you start Word as one of the users who does have the
> >> problem, and then go to Tools - Options - File locations, is
> >> the path correct there?
> >>
> >> _________________________________________________________
> >> 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@discussions.microsoft.com>
> >> wrote on 23 jan 2008 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > Vena -- Thanks, but no luck so far.
> >> >
> >> > Before I respond, I should also add what else I have figured
> >> > out. I thought the problem was on all non-admin accounts.
> >> > As it turns out, newly created non-admin accounts are fine.
> >> > The error only occurs for pre-existing non-admin accounts.
> >> > We do use roaming TS profiles. On the old server, the
> >> > USERPROFILE path was on the C: drive, and on the new server
> >> > it is on the D: drive.
> >> >
> >> > I've got a suspecion that Word is trying to create a temp
> >> > file in a folder on C:\Documents and Settings\<userprofile>
> >> > (which does not exist on C when it should instead be in
> >> > Documents and Settings on the D: drive. But, I'll be damned
> >> > if I can figure out where the problem is. Obviously it is
> >> > not a system environment variable. User environment
> >> > variables match on both working and non-working accounts, so
> >> > thats out. It must be a setting somewhere in HKLM contained
> >> > within the users TS profile.
> >> > I'd hate to have to re-do everyones profile from scratch
> >> > just
> >> > because of this.
> >> >
> >> > - I tried deleting the data subkey and letting Word recreate
> >> > it - HKCU\....\User Shell Folders\Cache looks good
> >> > - Yes, it was in install mode.
> >> >
> >> > Ted
> >> >
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> 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@discussions.microsoft.com>
> >> >> 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
>

 

[TKovacs]

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

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

Ok... Found something interesting with ProcessMonitor. ACCESS DENIED on
operation CreateFile in C:\WINDOWS\Temporary Internet Files\Content.Word\.
When I temporarily enabled full control for Users on this folder, the problem
goes away. Then I set security back to orignal, and the problem returns. So
I could adjust the security on the folder, but that still wouldn't answer why
the affected exiting users have this issue and why new users do not.
Apparently, whatever file is being created for new users is being created
somewhere else, presumable within their UserProfile folder. Any thoughts
Vera?

"Vera Noest [MVP]" wrote:

> Then I would use ProcessMonitor. Start it on the TS as
> administrator (when no other users are logged on, then let one of
> the users with the problem logon and start Word. ProcessMonitor
> should show you every registry key and file that Word tries to
> open. You can filter the output on ACCESS DENIED and PATH NOT FOUND
> errors.
>
> Download here:
> http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/p
> rocessmonitor.mspx
>
> _________________________________________________________
> 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@discussions.microsoft.com> wrote
> on 23 jan 2008 in microsoft.public.windows.terminal_services:
>
> > Yes. All those paths are correct. Also, all paths listed when
> > using the SET command at a command prompt are also correct.
> >
> > Ted
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> If you start Word as one of the users who does have the
> >> problem, and then go to Tools - Options - File locations, is
> >> the path correct there?
> >>
> >> _________________________________________________________
> >> 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@discussions.microsoft.com>
> >> wrote on 23 jan 2008 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > Vena -- Thanks, but no luck so far.
> >> >
> >> > Before I respond, I should also add what else I have figured
> >> > out. I thought the problem was on all non-admin accounts.
> >> > As it turns out, newly created non-admin accounts are fine.
> >> > The error only occurs for pre-existing non-admin accounts.
> >> > We do use roaming TS profiles. On the old server, the
> >> > USERPROFILE path was on the C: drive, and on the new server
> >> > it is on the D: drive.
> >> >
> >> > I've got a suspecion that Word is trying to create a temp
> >> > file in a folder on C:\Documents and Settings\<userprofile>
> >> > (which does not exist on C when it should instead be in
> >> > Documents and Settings on the D: drive. But, I'll be damned
> >> > if I can figure out where the problem is. Obviously it is
> >> > not a system environment variable. User environment
> >> > variables match on both working and non-working accounts, so
> >> > thats out. It must be a setting somewhere in HKLM contained
> >> > within the users TS profile.
> >> > I'd hate to have to re-do everyones profile from scratch
> >> > just
> >> > because of this.
> >> >
> >> > - I tried deleting the data subkey and letting Word recreate
> >> > it - HKCU\....\User Shell Folders\Cache looks good
> >> > - Yes, it was in install mode.
> >> >
> >> > Ted
> >> >
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> 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@discussions.microsoft.com>
> >> >> 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
>

 

[Vera Noest [MVP]]

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

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

I haven't the faintest idea, but this seems weird.
I find it strange that Word tries to save temporary data in a
\Temporary Internet Files\Content folder, and I find it starnge
that the Temporary Internet Files folder is stored in C:\WINDOWS.

This makes me wonder if there is not a bigger problem going on with
your user profiles. And that leads me to the question: how did you
configure the server to store the user profiles on the D: drive?
The only supported way to do that is through an unattended
installation of Windows 2003, with an answer file. Is that how you
did it? Or did you change the location of the Documents and
Settings folder from C: to D: after installation of the OS, by
making changes in the registry?

_________________________________________________________
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@discussions.microsoft.com> wrote
on 24 jan 2008 in microsoft.public.windows.terminal_services:

> Ok... Found something interesting with ProcessMonitor. ACCESS
> DENIED on operation CreateFile in C:\WINDOWS\Temporary Internet
> Files\Content.Word\. When I temporarily enabled full control
> for Users on this folder, the problem goes away. Then I set
> security back to orignal, and the problem returns. So I could
> adjust the security on the folder, but that still wouldn't
> answer why the affected exiting users have this issue and why
> new users do not. Apparently, whatever file is being created
> for new users is being created somewhere else, presumable within
> their UserProfile folder. Any thoughts Vera?
>
> "Vera Noest [MVP]" wrote:
>
>> Then I would use ProcessMonitor. Start it on the TS as
>> administrator (when no other users are logged on, then let one
>> of the users with the problem logon and start Word.
>> ProcessMonitor should show you every registry key and file that
>> Word tries to open. You can filter the output on ACCESS DENIED
>> and PATH NOT FOUND errors.
>>
>> Download here:
>> http://www.microsoft.com/technet/sysinternals/ProcessesAndThread
>> s/p rocessmonitor.mspx
>>
>> _________________________________________________________
>> 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@discussions.microsoft.com>
>> wrote on 23 jan 2008 in
>> microsoft.public.windows.terminal_services:
>>
>> > Yes. All those paths are correct. Also, all paths listed
>> > when using the SET command at a command prompt are also
>> > correct.
>> >
>> > Ted
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> If you start Word as one of the users who does have the
>> >> problem, and then go to Tools - Options - File locations, is
>> >> the path correct there?
>> >>
>> >> _________________________________________________________
>> >> 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@discussions.microsoft.com>
>> >> wrote on 23 jan 2008 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > Vena -- Thanks, but no luck so far.
>> >> >
>> >> > Before I respond, I should also add what else I have
>> >> > figured out. I thought the problem was on all non-admin
>> >> > accounts. As it turns out, newly created non-admin
>> >> > accounts are fine. The error only occurs for pre-existing
>> >> > non-admin accounts. We do use roaming TS profiles. On the
>> >> > old server, the USERPROFILE path was on the C: drive, and
>> >> > on the new server it is on the D: drive.
>> >> >
>> >> > I've got a suspecion that Word is trying to create a temp
>> >> > file in a folder on C:\Documents and
>> >> > Settings\<userprofile> (which does not exist on C when
>> >> > it should instead be in Documents and Settings on the D:
>> >> > drive. But, I'll be damned if I can figure out where the
>> >> > problem is. Obviously it is not a system environment
>> >> > variable. User environment variables match on both
>> >> > working and non-working accounts, so thats out. It must
>> >> > be a setting somewhere in HKLM contained within the users
>> >> > TS profile.
>> >> > I'd hate to have to re-do everyones profile from scratch
>> >> > just
>> >> > because of this.
>> >> >
>> >> > - I tried deleting the data subkey and letting Word
>> >> > recreate it - HKCU\....\User Shell Folders\Cache looks
>> >> > good - Yes, it was in install mode.
>> >> >
>> >> > Ted
>> >> >
>> >> >
>> >> > "Vera Noest [MVP]" wrote:
>> >> >
>> >> >> 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@discussions.microsoft.com> 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

 

[Marcus]

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

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

Hi,

I had the same problem when when running terminal services on windows server
2003. The reason for this was IE7. When I uninstalled IE7 the problem went
away.
Can anyone tell me why?

"Vera Noest [MVP]" wrote:

> I haven't the faintest idea, but this seems weird.
> I find it strange that Word tries to save temporary data in a
> \Temporary Internet Files\Content folder, and I find it starnge
> that the Temporary Internet Files folder is stored in C:\WINDOWS.
>
> This makes me wonder if there is not a bigger problem going on with
> your user profiles. And that leads me to the question: how did you
> configure the server to store the user profiles on the D: drive?
> The only supported way to do that is through an unattended
> installation of Windows 2003, with an answer file. Is that how you
> did it? Or did you change the location of the Documents and
> Settings folder from C: to D: after installation of the OS, by
> making changes in the registry?
>
> _________________________________________________________
> 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@discussions.microsoft.com> wrote
> on 24 jan 2008 in microsoft.public.windows.terminal_services:
>
> > Ok... Found something interesting with ProcessMonitor. ACCESS
> > DENIED on operation CreateFile in C:\WINDOWS\Temporary Internet
> > Files\Content.Word\. When I temporarily enabled full control
> > for Users on this folder, the problem goes away. Then I set
> > security back to orignal, and the problem returns. So I could
> > adjust the security on the folder, but that still wouldn't
> > answer why the affected exiting users have this issue and why
> > new users do not. Apparently, whatever file is being created
> > for new users is being created somewhere else, presumable within
> > their UserProfile folder. Any thoughts Vera?
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Then I would use ProcessMonitor. Start it on the TS as
> >> administrator (when no other users are logged on, then let one
> >> of the users with the problem logon and start Word.
> >> ProcessMonitor should show you every registry key and file that
> >> Word tries to open. You can filter the output on ACCESS DENIED
> >> and PATH NOT FOUND errors.
> >>
> >> Download here:
> >> http://www.microsoft.com/technet/sysinternals/ProcessesAndThread
> >> s/p rocessmonitor.mspx
> >>
> >> _________________________________________________________
> >> 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@discussions.microsoft.com>
> >> wrote on 23 jan 2008 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > Yes. All those paths are correct. Also, all paths listed
> >> > when using the SET command at a command prompt are also
> >> > correct.
> >> >
> >> > Ted
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> If you start Word as one of the users who does have the
> >> >> problem, and then go to Tools - Options - File locations, is
> >> >> the path correct there?
> >> >>
> >> >> _________________________________________________________
> >> >> 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@discussions.microsoft.com>
> >> >> wrote on 23 jan 2008 in
> >> >> microsoft.public.windows.terminal_services:
> >> >>
> >> >> > Vena -- Thanks, but no luck so far.
> >> >> >
> >> >> > Before I respond, I should also add what else I have
> >> >> > figured out. I thought the problem was on all non-admin
> >> >> > accounts. As it turns out, newly created non-admin
> >> >> > accounts are fine. The error only occurs for pre-existing
> >> >> > non-admin accounts. We do use roaming TS profiles. On the
> >> >> > old server, the USERPROFILE path was on the C: drive, and
> >> >> > on the new server it is on the D: drive.
> >> >> >
> >> >> > I've got a suspecion that Word is trying to create a temp
> >> >> > file in a folder on C:\Documents and
> >> >> > Settings\<userprofile> (which does not exist on C when
> >> >> > it should instead be in Documents and Settings on the D:
> >> >> > drive. But, I'll be damned if I can figure out where the
> >> >> > problem is. Obviously it is not a system environment
> >> >> > variable. User environment variables match on both
> >> >> > working and non-working accounts, so thats out. It must
> >> >> > be a setting somewhere in HKLM contained within the users
> >> >> > TS profile.
> >> >> > I'd hate to have to re-do everyones profile from scratch
> >> >> > just
> >> >> > because of this.
> >> >> >
> >> >> > - I tried deleting the data subkey and letting Word
> >> >> > recreate it - HKCU\....\User Shell Folders\Cache looks
> >> >> > good - Yes, it was in install mode.
> >> >> >
> >> >> > Ted
> >> >> >
> >> >> >
> >> >> > "Vera Noest [MVP]" wrote:
> >> >> >
> >> >> >> 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@discussions.microsoft.com> 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
>

 

[Marcus]

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

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

Hi Vera,

I had the same problem with outlook and word. It was IE7 that was the
problem. When I uninstalled IE7 the problem went away. can anyone tell me why
this is?

//Marcus

"Vera Noest [MVP]" wrote:

> I haven't the faintest idea, but this seems weird.
> I find it strange that Word tries to save temporary data in a
> \Temporary Internet Files\Content folder, and I find it starnge
> that the Temporary Internet Files folder is stored in C:\WINDOWS.
>
> This makes me wonder if there is not a bigger problem going on with
> your user profiles. And that leads me to the question: how did you
> configure the server to store the user profiles on the D: drive?
> The only supported way to do that is through an unattended
> installation of Windows 2003, with an answer file. Is that how you
> did it? Or did you change the location of the Documents and
> Settings folder from C: to D: after installation of the OS, by
> making changes in the registry?
>
> _________________________________________________________
> 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@discussions.microsoft.com> wrote
> on 24 jan 2008 in microsoft.public.windows.terminal_services:
>
> > Ok... Found something interesting with ProcessMonitor. ACCESS
> > DENIED on operation CreateFile in C:\WINDOWS\Temporary Internet
> > Files\Content.Word\. When I temporarily enabled full control
> > for Users on this folder, the problem goes away. Then I set
> > security back to orignal, and the problem returns. So I could
> > adjust the security on the folder, but that still wouldn't
> > answer why the affected exiting users have this issue and why
> > new users do not. Apparently, whatever file is being created
> > for new users is being created somewhere else, presumable within
> > their UserProfile folder. Any thoughts Vera?
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Then I would use ProcessMonitor. Start it on the TS as
> >> administrator (when no other users are logged on, then let one
> >> of the users with the problem logon and start Word.
> >> ProcessMonitor should show you every registry key and file that
> >> Word tries to open. You can filter the output on ACCESS DENIED
> >> and PATH NOT FOUND errors.
> >>
> >> Download here:
> >> http://www.microsoft.com/technet/sysinternals/ProcessesAndThread
> >> s/p rocessmonitor.mspx
> >>
> >> _________________________________________________________
> >> 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@discussions.microsoft.com>
> >> wrote on 23 jan 2008 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > Yes. All those paths are correct. Also, all paths listed
> >> > when using the SET command at a command prompt are also
> >> > correct.
> >> >
> >> > Ted
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> If you start Word as one of the users who does have the
> >> >> problem, and then go to Tools - Options - File locations, is
> >> >> the path correct there?
> >> >>
> >> >> _________________________________________________________
> >> >> 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@discussions.microsoft.com>
> >> >> wrote on 23 jan 2008 in
> >> >> microsoft.public.windows.terminal_services:
> >> >>
> >> >> > Vena -- Thanks, but no luck so far.
> >> >> >
> >> >> > Before I respond, I should also add what else I have
> >> >> > figured out. I thought the problem was on all non-admin
> >> >> > accounts. As it turns out, newly created non-admin
> >> >> > accounts are fine. The error only occurs for pre-existing
> >> >> > non-admin accounts. We do use roaming TS profiles. On the
> >> >> > old server, the USERPROFILE path was on the C: drive, and
> >> >> > on the new server it is on the D: drive.
> >> >> >
> >> >> > I've got a suspecion that Word is trying to create a temp
> >> >> > file in a folder on C:\Documents and
> >> >> > Settings\<userprofile> (which does not exist on C when
> >> >> > it should instead be in Documents and Settings on the D:
> >> >> > drive. But, I'll be damned if I can figure out where the
> >> >> > problem is. Obviously it is not a system environment
> >> >> > variable. User environment variables match on both
> >> >> > working and non-working accounts, so thats out. It must
> >> >> > be a setting somewhere in HKLM contained within the users
> >> >> > TS profile.
> >> >> > I'd hate to have to re-do everyones profile from scratch
> >> >> > just
> >> >> > because of this.
> >> >> >
> >> >> > - I tried deleting the data subkey and letting Word
> >> >> > recreate it - HKCU\....\User Shell Folders\Cache looks
> >> >> > good - Yes, it was in install mode.
> >> >> >
> >> >> > Ted
> >> >> >
> >> >> >
> >> >> > "Vera Noest [MVP]" wrote:
> >> >> >
> >> >> >> 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@discussions.microsoft.com> 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
>