Help me about application package install problem.Thank you so much.

[jeff526]

Hello, Everybody:
I have a problem need your help.

Right now I have finished my project and made a setup package.

When I installed in the user computer(whatever in workstation or server), I got error 168 message:” Setup has encountered a problem updating your system registry.” Is it means something was missed in my setup package?

Thank you for your help.

Jeff

 

[edderic]

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

During Visual Basic setup, the following error may be received while the system registry is being updated:

Setup error 168 : Setup encountered an error updating your registry
This problem occurs on Windows 2000, Windows NT 4.0, Windows 95, Windows 98, and Windows Me.



CAUSE
On Windows NT or Windows 2000, this problem frequently occurs when a user attempts to install or use Visual Basic without having the necessary access rights.

On Windows 95, Windows 98, and Windows Me, this problem frequently occurs when registry keys being updated are locked, are used by another application, or have exceeded their size limits. See the MORE INFORMATION section to follow.



RESOLUTION
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).

This article provides workarounds for Windows 2000, Windows NT 4.0, Windows 95, Windows 98, and Windows Me.


Resolution for Windows 2000 and Windows NT 4.0
NOTE: The procedures shown here must be performed by a person with Administrator rights for the machine.

Step-by-Step Example
From the Windows Start menu, choose Run.


Type in the path to the Registry Editor (for example, C:\WINNT\SYSTEM32\Regedt32.exe), and then click OK.


From the HKEY_LOCAL_MACHINE on Local Machine window, select the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools registry key.


Choose Permissions from the Security menu.


From the Registry Key Permissions dialog box, click Replace Permission on Existing Subkeys.


From the Name text box, select Everyone, and then choose Full Control from the Type of Access combo box.


Click OK.


From the HKEY_LOCAL_MACHINE on Local Machine window, highlight the HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib registry key.


Repeat steps 4 through 7.


From the HKEY_CLASSES_ROOT on Local Machine window, highlight the HKEY_CLASSES_ROOT\TypeLib registry key.


Repeat steps 4 through 7.


Try to reinstall Visual Basic.




Resolutions for Windows 95, Windows 98, or Windows Me
NOTE: Five possible resolutions for Windows 95, Windows 98, or Windows Me are provided here.

Resolution 1
Run RegClean.exe to clean the registry

For additional information how to obtain and use RegClean, click the article number below to view the article in the Microsoft Knowledge Base:
Q147769 RegClean 4.1a Description and General Issues


Resolution 2
Remove erroneous entries from the SharedDLLs registry key

Step-by-Step Example
From the Windows Start menu, choose Run.


Type the path to the Registry Editor (for example, C:\WINDOWS\Regedit.exe), and then click OK to open the Registry Editor.


Locate the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs


Examine the SharedDLLs key entries to see if any files with extensions such as .c, .cpp, or .rc are registered. Note that you should use this key when registering only DLL files. Delete any file entries from the SharedDLLs registry key that contain extensions other than .dll or .exe.


Install Visual Basic again.


Resolution 3
Replace the existing SharedDLLs registry key

Step-by-Step Example
From the Windows Start menu, choose Run.


Type in the path to the Registry Editor (for example, C:\WINDOWS\Regedit.exe), and then click OK to open the Registry Editor.


Locate the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs


From the Registry menu, choose Export Registry File to save the existing registry key.


Name the exported registry key file and save it in a temporary directory (for example, C:\Temp\OldKey.dat).


Delete the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs


Install Visual Basic again.

NOTE: Whether installation is successful or unsuccessful, perform steps 1-2 above again, then continue to step 8.


Save the new SharedDLLs registry key as described in steps 4-5, assigning it a new name (for example, C:\Temp\NewKey.dat).


From the Registry menu, choose Import Registry File. Enter the name of the original registry key (in our example, C:\Temp\OldKey.dat), then click Open. This important step restores SharedDLLs registry key information that would otherwise be lost.


If the installation in step 7 was successful, import the second saved registry file (in our example, C:\Temp\NewKey.dat) in the event that importing OldKey.dat wrote over some key values. See step 9 for this procedure.

If the installation in Step 7 was unsuccessful, it may be because you have exceeded the size limit of the Registry. See Resolutions 4 and 5 for workarounds for this problem.


Resolution 4
Reduce registry size by temporarily deleting fonts

Step-by-Step Example
From the Windows Control Panel, select Fonts.


Check the number of fonts loaded on the machine: the number of fonts appears at the bottom of the Fonts window. If you have more than 800 fonts on your system, move some fonts from the Windows\Fonts folder to a temporary location.


Install Visual Basic again.


Move the fonts back after Visual Basic has been successfully installed.


Resolution 5
Reduce path size to allow for more registry entries

Step-by-Step Example
Examine the directory structure into which you have loaded applications on your system. The full directory path for DLLs is entered into the SharedDLLs registry key and the number of characters in the path reduces the number of entries in a registry key.


In order to allow for more Registry entries, you may wish to uninstall particular applications and then reinstall the applications closer to the root directory.


Install Visual Basic again.





STATUS
Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.



MORE INFORMATION
This problem occurs on Windows 2000, Windows NT 4.0, Windows 98, and Windows 95. This article provides additional information and workarounds for all platforms.



Windows 2000 or NT 4.0
If you do not have Administrator rights on a Windows 2000 or Windows NT machine and try to install Visual Basic as a regular user, you will get error 168 while the system registry is being updated.


If you do have Administrator rights and some of the subkeys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools are owned by someone else or do not have an owner (they appear dimmed), you will also get error 168.


If you don't have access to HKLM\Software\Microsoft\Shared Tools and HKCR and HKLM\Software\Classes\TypeLib subkeys, you will get "Unexpected error quitting" when you try to start Visual Basic. This usually happens when you are a regular user and the administrator did not grant you access rights.


Windows 95, Windows 98, or Windows Me
Windows 95 and Windows 98 appear to have a registry key size limit beyond which it will not respond to the RegistrySizeLimit value. If this size limit is exceeded, Visual Basic may not be able to update the registry and complete setup.


Eric De Decker
vbg.be@vbgroup.nl

License And Copy Protection AxtiveX.

Download Demo version on my Site:

http://www.createsoftware2000.com

 

[jeff526]

Hi, Eric:

First thank you so much.

I have read your solution. Right now I know where is the problem. But I can’t solve like this. You know the network administrator will not allow me try this. I must negotiate with admin to get better solution.

What do you think if I make application development package in the NT4.0 on PDC using administrator permission it’s can work or not?

Thanks again
Jeff

 

[reghakr]

Jeff,

Truthfully, I think this is all you need:

From the HKEY_LOCAL_MACHINE on Local Machine window, select the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools registry key

Export it, then delete it, then increment the values using Notepad and re-import it.

reghakr