Hi folks. Except for remote administration, we've never used terminal
services very much, but now we have a VP that wants to make a custom-built
app available on our Windows 2000 terminal server, and I'm running into a
couple of snags, and I'm hoping that you can provide a bit of guidance.

First, when attempting to install his app (written in VB6), I get a dialog
box stating:

"Setup cannot continue because some system files are out of date on your
system. Click OK if you would like setup to update these files for you now.
You will need to restart Windows before you can run setup again. Click
cancel to exit setup without updating system files."

If I choose OK and let the system reboot, the next time I run setup again, I
get the same dialog box. If I click Cancel, the installation just ends.

Any ideas on this?

Thanks,
Mike

Hi Mike,

1. Does this issue only occur when you are on the client side and remote to
the terminal server?

2. What is the result if you install the application on the server locally?

Based on my research, actually this issue is most related to the VB
application. This occurred because the package was attempting to install a
newer version of MSVCRT.dll on the Windows 2000 computer. However,
MSVCRT.dll is under system file protection and Windows will not allow it to
be replaced. Since it could never be replaced, the Setup program detected
it needed to copy the newer version again and this cycle continued
repeatedly.

Please remove MSVCRT.dll from the Setup.lst file so that the setup program
would not attempt to install it.

Oleaut32.dll file is also protected by the OS and cannot be replace if the
application setup try to replace it, so the system files are always out of
date.

Install SP5 and rebuild the Package. This way it will pick up the files
from the Redist folder instead of the live system files. By default this
folder is locates at: C:\Program Files\Microsoft Visual
Studio\VB98\Wizards\PDWizard\Redist

Before rebuilding the package make sure the Reference to ADO is for at
least 2.5, then recompile and retest. When building the Package make sure
it includes MDAC_TYP.EXE and does not include Msado25.tlb nor MSWORD.OLB.
(You should never deploy *.OLB files.) This new Package should work well,
but let me know if you have problems with it.

You can get the latest service pack for Visual Basic 6.0 from
<http://msdn.microsoft.com/vstudio/downloads/updates/sp/vs6/sp5/default.asp>

Hi Rebecca,

A1. No, it occurs when attempting to install locally, too.
A2. Same results.

I removed the references to MSVCRT.dll and OLEAUT32.dll from setup.lst,
reordered the remaining list and attempted to install again, but the results
were the same. I just removed references to COMDLG32.ocx and MFC42.dll, but
I'm rebooting the machine before I attempt to install it again.

I'll download SP5 and give it to the program's developer (one of our VPs).

Thanks,
Mike

"Rebecca Chen [MSFT]" <v-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Mike,
>
> 1. Does this issue only occur when you are on the client side and remote
> to
> the terminal server?
>
> 2. What is the result if you install the application on the server
> locally?
>
> Based on my research, actually this issue is most related to the VB
> application. This occurred because the package was attempting to install a
> newer version of MSVCRT.dll on the Windows 2000 computer. However,
> MSVCRT.dll is under system file protection and Windows will not allow it
> to
> be replaced. Since it could never be replaced, the Setup program detected
> it needed to copy the newer version again and this cycle continued
> repeatedly.
>
> Please remove MSVCRT.dll from the Setup.lst file so that the setup program
> would not attempt to install it.
>
> Oleaut32.dll file is also protected by the OS and cannot be replace if the
> application setup try to replace it, so the system files are always out of
> date.
>
> Install SP5 and rebuild the Package. This way it will pick up the files
> from the Redist folder instead of the live system files. By default this
> folder is locates at: C:\Program Files\Microsoft Visual
> Studio\VB98\Wizards\PDWizard\Redist
>
> Before rebuilding the package make sure the Reference to ADO is for at
> least 2.5, then recompile and retest. When building the Package make sure
> it includes MDAC_TYP.EXE and does not include Msado25.tlb nor MSWORD.OLB.
> (You should never deploy *.OLB files.) This new Package should work well,
> but let me know if you have problems with it.
>
> You can get the latest service pack for Visual Basic 6.0 from
> <http://msdn.microsoft.com/vstudio/downloads/updates/sp/vs6/sp5/default.asp>

Hi Rebecca,

The installation completed successfully once I removed the references to
comdlg32.ocs and mfc42.dll.

Now, on to the next problem. The program runs just fine for me (admin), but
for anyone else (non-admins) an error dialog appears: "Run-time error '339':
Component 'FPSPR70.ocx' or one of its dependencies not correctly registered:
a file is missing or invalid"

I can't make every user an admin. Is there a way to fix this problem?

Thanks,
Mike


"Mike Koch" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Rebecca,
>
> A1. No, it occurs when attempting to install locally, too.
> A2. Same results.
>
> I removed the references to MSVCRT.dll and OLEAUT32.dll from setup.lst,
> reordered the remaining list and attempted to install again, but the
> results were the same. I just removed references to COMDLG32.ocx and
> MFC42.dll, but I'm rebooting the machine before I attempt to install it
> again.
>
> I'll download SP5 and give it to the program's developer (one of our VPs).
>
> Thanks,
> Mike
>
> "Rebecca Chen [MSFT]" <v-(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi Mike,
>>
>> 1. Does this issue only occur when you are on the client side and remote
>> to
>> the terminal server?
>>
>> 2. What is the result if you install the application on the server
>> locally?
>>
>> Based on my research, actually this issue is most related to the VB
>> application. This occurred because the package was attempting to install
>> a
>> newer version of MSVCRT.dll on the Windows 2000 computer. However,
>> MSVCRT.dll is under system file protection and Windows will not allow it
>> to
>> be replaced. Since it could never be replaced, the Setup program detected
>> it needed to copy the newer version again and this cycle continued
>> repeatedly.
>>
>> Please remove MSVCRT.dll from the Setup.lst file so that the setup
>> program
>> would not attempt to install it.
>>
>> Oleaut32.dll file is also protected by the OS and cannot be replace if
>> the
>> application setup try to replace it, so the system files are always out
>> of
>> date.
>>
>> Install SP5 and rebuild the Package. This way it will pick up the files
>> from the Redist folder instead of the live system files. By default this
>> folder is locates at: C:\Program Files\Microsoft Visual
>> Studio\VB98\Wizards\PDWizard\Redist
>>
>> Before rebuilding the package make sure the Reference to ADO is for at
>> least 2.5, then recompile and retest. When building the Package make sure
>> it includes MDAC_TYP.EXE and does not include Msado25.tlb nor MSWORD.OLB.
>> (You should never deploy *.OLB files.) This new Package should work well,
>> but let me know if you have problems with it.
>>
>> You can get the latest service pack for Visual Basic 6.0 from
>> <http://msdn.microsoft.com/vstudio/downloads/updates/sp/vs6/sp5/default.asp>
>
>

Did you perform the installation while the Terminal Server was in
"install" mode?

You could download FileMon and RegMon from
http://www.sysinternals.com/. Run them as administrator, start a TS
session as a normal user and try to run the application.

FileMon and RegMon will show you all "access denied" errors that
occur. You might need to give your users extra permissions on
system files or a registry key.
In the worsed case, you might have to import a registry key into
every users hive in your logon script.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"Mike Koch" <(E-Mail Removed)> wrote on 15 feb 2005 in
microsoft.public.win2000.termserv.apps:

> Hi Rebecca,
>
> The installation completed successfully once I removed the
> references to comdlg32.ocs and mfc42.dll.
>
> Now, on to the next problem. The program runs just fine for me
> (admin), but for anyone else (non-admins) an error dialog
> appears: "Run-time error '339': Component 'FPSPR70.ocx' or one
> of its dependencies not correctly registered: a file is missing
> or invalid"
>
> I can't make every user an admin. Is there a way to fix this
> problem?
>
> Thanks,
> Mike
>
>
> "Mike Koch" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi Rebecca,
>>
>> A1. No, it occurs when attempting to install locally, too.
>> A2. Same results.
>>
>> I removed the references to MSVCRT.dll and OLEAUT32.dll from
>> setup.lst, reordered the remaining list and attempted to
>> install again, but the results were the same. I just removed
>> references to COMDLG32.ocx and MFC42.dll, but I'm rebooting the
>> machine before I attempt to install it again.
>>
>> I'll download SP5 and give it to the program's developer (one
>> of our VPs).
>>
>> Thanks,
>> Mike
>>
>> "Rebecca Chen [MSFT]" <v-(E-Mail Removed)> wrote in
>> message news:(E-Mail Removed)...
>>> Hi Mike,
>>>
>>> 1. Does this issue only occur when you are on the client side
>>> and remote to
>>> the terminal server?
>>>
>>> 2. What is the result if you install the application on the
>>> server locally?
>>>
>>> Based on my research, actually this issue is most related to
>>> the VB application. This occurred because the package was
>>> attempting to install a
>>> newer version of MSVCRT.dll on the Windows 2000 computer.
>>> However, MSVCRT.dll is under system file protection and
>>> Windows will not allow it to
>>> be replaced. Since it could never be replaced, the Setup
>>> program detected it needed to copy the newer version again and
>>> this cycle continued repeatedly.
>>>
>>> Please remove MSVCRT.dll from the Setup.lst file so that the
>>> setup program
>>> would not attempt to install it.
>>>
>>> Oleaut32.dll file is also protected by the OS and cannot be
>>> replace if the
>>> application setup try to replace it, so the system files are
>>> always out of
>>> date.
>>>
>>> Install SP5 and rebuild the Package. This way it will pick up
>>> the files from the Redist folder instead of the live system
>>> files. By default this folder is locates at: C:\Program
>>> Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist
>>>
>>> Before rebuilding the package make sure the Reference to ADO
>>> is for at least 2.5, then recompile and retest. When building
>>> the Package make sure it includes MDAC_TYP.EXE and does not
>>> include Msado25.tlb nor MSWORD.OLB. (You should never deploy
>>> *.OLB files.) This new Package should work well, but let me
>>> know if you have problems with it.
>>>
>>> You can get the latest service pack for Visual Basic 6.0 from
>>> <http://msdn.microsoft.com/vstudio/do...tes/sp/vs6/sp5
>>> /default.asp>

Hi Mike,


Based on your description, we have already isolated this issue to the
compatibility between the server and the VB application since this issue
does not only occur on a terminal server, it occurs even if you install it
locally and it can successfully been installed after patched VB SP5.

Frankly, I am not a develop expert and just have limited knowledge about
VB. I suggest you post this issue to the Microsoft.public.vb newsgroup to
get more information about this issue.

In addition, I have seen the error has pointed to the FPSPR70.ocx and its
dependencies have not been correctly registered, you may consult with the
developer to see if the non-administrator has the permission to register
(and how to register) the FPSPR70.ocx control file.

HTH!

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA


Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks, Vera, filemon did the trick. The fpspr70.ocx is in the system32
folder, which the normal users don't have access to. I modified the
permissions on that file, giving "domain users" read access, and now the
application works for everyone.


"Vera Noest [MVP]" <(E-Mail Removed)> wrote in message
news:Xns95FEE1952759Averanoesthemutforsse@207.46.248.16...
> You could download FileMon and RegMon from
> http://www.sysinternals.com/. Run them as administrator, start a TS
> session as a normal user and try to run the application.
>
> FileMon and RegMon will show you all "access denied" errors that
> occur. You might need to give your users extra permissions on
> system files or a registry key.
> In the worsed case, you might have to import a registry key into
> every users hive in your logon script.
> --
>
> "Mike Koch" <(E-Mail Removed)> wrote on 15 feb 2005 in
> microsoft.public.win2000.termserv.apps:
>
>> Now, on to the next problem. The program runs just fine for me
>> (admin), but for anyone else (non-admins) an error dialog
>> appears: "Run-time error '339': Component 'FPSPR70.ocx' or one
>> of its dependencies not correctly registered: a file is missing
>> or invalid"

[shijobaby]

http://vbprogrammingerrors.blogspot....f-date-vb.html