Hotfix for 0xc0000006 Unable to Initialize Application KB 818528 Doesn't apply to 2003, but the registry entry is not in 2003

Is this fixed in 2003?

There is a registry entry that is necessary in Server 2000 when Terminal
Services accesses applications from a Network Share, that requires a hotfix
per the following:

http://support.microsoft.com/kb/818528/


The Windows 2000 network redirector maintains the data structures per
computer, and therefore if two users on the same terminal server access the
same file over the network, they share the same data structures internally.
When the first user closes the file, the redirector also closes the file for
other users

2003 is not referenced, however the exact same registry entry needs to be
added to address a network redirector issue for Server 2003 via KB913835.

I asked the Indians that helped me about both of these hotfixes but they
were not able to answer whether the registry entry was needed for 2003 for
the first issue.

Does anyone know the answer?

Thanks

Regarding the issue described in 818528 (also described in many
other previous articles and revisions of same), my experience is that
it is fixed in 2003. No reg entry needed.

I am very familiar with the issue--I created a bulletproof workaround
to avoid using the hotfix back in 1999-2000 time frame, plus I tested
several versions of the hotfixes developed to solve the issue over
the years since.

I have no experience with the issue described in 913835 so I will
leave that to you to test and analyze.

-TP

contributor wrote:
> Is this fixed in 2003?
>
> There is a registry entry that is necessary in Server 2000 when
> Terminal Services accesses applications from a Network Share, that
> requires a hotfix per the following:
>
> http://support.microsoft.com/kb/818528/
>
>
> The Windows 2000 network redirector maintains the data structures per
> computer, and therefore if two users on the same terminal server
> access the same file over the network, they share the same data
> structures internally. When the first user closes the file, the
> redirector also closes the file for other users
>
> 2003 is not referenced, however the exact same registry entry needs
> to be added to address a network redirector issue for Server 2003 via
> KB913835.
>
> I asked the Indians that helped me about both of these hotfixes but
> they were not able to answer whether the registry entry was needed
> for 2003 for the first issue.
>
> Does anyone know the answer?
>
> Thanks

I have not experienced it with 2003 either, but whenever that is the case,
and there is a need for the exact same registry entry for a different
problem, I am suspicious.

Can you tell me if the application you hosted was a VFP app as is the case
for me?

"TP" <(E-Mail Removed)> wrote in message
news:%23$(E-Mail Removed)...
> Regarding the issue described in 818528 (also described in many other
> previous articles and revisions of same), my experience is that it is
> fixed in 2003. No reg entry needed.
>
> I am very familiar with the issue--I created a bulletproof workaround to
> avoid using the hotfix back in 1999-2000 time frame, plus I tested several
> versions of the hotfixes developed to solve the issue over the years
> since.
>
> I have no experience with the issue described in 913835 so I will leave
> that to you to test and analyze.
>
> -TP
>
> contributor wrote:
>> Is this fixed in 2003?
>>
>> There is a registry entry that is necessary in Server 2000 when
>> Terminal Services accesses applications from a Network Share, that
>> requires a hotfix per the following:
>>
>> http://support.microsoft.com/kb/818528/
>>
>>
>> The Windows 2000 network redirector maintains the data structures per
>> computer, and therefore if two users on the same terminal server
>> access the same file over the network, they share the same data
>> structures internally. When the first user closes the file, the
>> redirector also closes the file for other users
>>
>> 2003 is not referenced, however the exact same registry entry needs
>> to be added to address a network redirector issue for Server 2003 via
>> KB913835. I asked the Indians that helped me about both of these hotfixes
>> but
>> they were not able to answer whether the registry entry was needed
>> for 2003 for the first issue.
>>
>> Does anyone know the answer?
>>
>> Thanks

No, not foxpro, but other similar like paradox, access, btrieve, etc.

I wrote a small app years ago to demonstrate the problem. You
can test yourself by using the handle search capability of Process
Explorer. Logon two sessions and open the exact same network
file within each, then check to make sure they each have a unique
handle using Process Explorer.

-TP

contributor wrote:
> I have not experienced it with 2003 either, but whenever that is the
> case, and there is a need for the exact same registry entry for a
> different problem, I am suspicious.
>
> Can you tell me if the application you hosted was a VFP app as is the
> case for me?

Do you know if the steps to reproduce this with VFP are available?

That is something MS usually puts on their MSDN site but I don't see them.

I am getting ready to migrate customers from 2000 to 2003 and I need to test
it before we do so.

Because the problem on 2000 was somewhat random, it is hard to know what to
look for.

I will say that adding the registry entry has completely resolved it with
2000.


"TP" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> No, not foxpro, but other similar like paradox, access, btrieve, etc.
>
> I wrote a small app years ago to demonstrate the problem. You can test
> yourself by using the handle search capability of Process Explorer. Logon
> two sessions and open the exact same network file within each, then check
> to make sure they each have a unique handle using Process Explorer.
>
> -TP
>
> contributor wrote:
>> I have not experienced it with 2003 either, but whenever that is the
>> case, and there is a need for the exact same registry entry for a
>> different problem, I am suspicious.
>>
>> Can you tell me if the application you hosted was a VFP app as is the
>> case for me?

I don't know if there are any vfp-specific steps. There were generic
steps listed in the articles in the past.

You could write a test program in vfp in a relatively short amount
of time and then run your own tests.

-TP

contributor wrote:
> Do you know if the steps to reproduce this with VFP are available?
>
> That is something MS usually puts on their MSDN site but I don't see
> them.
>
> I am getting ready to migrate customers from 2000 to 2003 and I need
> to test it before we do so.
>
> Because the problem on 2000 was somewhat random, it is hard to know
> what to look for.
>
> I will say that adding the registry entry has completely resolved it
> with 2000.