Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Error 20 when opening file in W2K PC with user right 2
- Thread starter FAM
- Start date
-
2
- #2
You have two options. 1) You need to look up information on the compatibility patch for Windows 2000 to allow older software to update the registry.
Or I found this info regarding the same issue.
Windows 2000 changes the default permissions for Users (that is,
restricted users) in HKEY_LOCAL_MACHINE registry branch from Read/Write
to Read only. To solve it, registry entries for BTRieve Technologies
need to be expanded.
Here is the general install procedure, with additional steps explained:
- after the installation, invoke 'regedt32' via Start Menu:Run option.
- find the key HKEY_LOCAL_MACHINE\Software\Btrieve Technologies.
- click on 'Security' option on menu bar select Permissions option.
- when the dialog comes up, click on 'Advanced' button.
- select the 'Users' group (or the appropriate user group for
your setup).
- IMPORTANT: in addition to the default permissions of:
Query Value, Enumerate Subkeys, Notify and Read Control
add:
Set Value, Create Subkey and Delete.
This will be displayed in the entries list as a separate line with
'Special' Permissions.
In addition, if the boot disk is NTFS, go to WINNT directory and locate
BTrieve log files mkdewe.trn and mkdemsg.log. Change the permissions for
these files to allow access for all (i.e. tick all the checkboxes on
'Security' tab).
Gil
Or I found this info regarding the same issue.
Windows 2000 changes the default permissions for Users (that is,
restricted users) in HKEY_LOCAL_MACHINE registry branch from Read/Write
to Read only. To solve it, registry entries for BTRieve Technologies
need to be expanded.
Here is the general install procedure, with additional steps explained:
- after the installation, invoke 'regedt32' via Start Menu:Run option.
- find the key HKEY_LOCAL_MACHINE\Software\Btrieve Technologies.
- click on 'Security' option on menu bar select Permissions option.
- when the dialog comes up, click on 'Advanced' button.
- select the 'Users' group (or the appropriate user group for
your setup).
- IMPORTANT: in addition to the default permissions of:
Query Value, Enumerate Subkeys, Notify and Read Control
add:
Set Value, Create Subkey and Delete.
This will be displayed in the entries list as a separate line with
'Special' Permissions.
In addition, if the boot disk is NTFS, go to WINNT directory and locate
BTrieve log files mkdewe.trn and mkdemsg.log. Change the permissions for
these files to allow access for all (i.e. tick all the checkboxes on
'Security' tab).
Gil
Or you can use regedt32/local machine on local machine/software/highlight Btrieve Technologies, go to security/permissions, highlight user, give full control, click on advanced, and give permissions to child objects. Remember also that Btrieve sometimes uses a HOME directory which defaults to Winnt. Users do not have permissions to that directory. You will have to run the W32MKSET utility, and change the home directory to a folder that the user has full permission to. Of course it all depends what Btrieve is running.
Guest_imported
New member
- Jan 1, 1970
- 0
This is a known issue as my software manufacturer had provided this cure. Excuse my lack of knowledge but the
"compatibility patch for Windows 2000" is this part of 2000 or where do you obtain it
If I add new users to the network is the long term cure
up to the software manufacturer to develop a registry update file, one that will change the necessary keys for the BTREIVE entry.
"compatibility patch for Windows 2000" is this part of 2000 or where do you obtain it
If I add new users to the network is the long term cure
up to the software manufacturer to develop a registry update file, one that will change the necessary keys for the BTREIVE entry.
Here is additional information from Pervasive's site. If you upgrade to the latest version and service pack then it is supposed to have resovlved the issue.
At the end of this is a Microsoft article about it. Notice at the very end it talks about he compatibility template. You will have to locate it on MS site.
The reason for this is that Windows 2000 changed the default permissions for Users in the HKEY_LOCAL_MACHINE branch from read\write to read-only. The Pervasive requester dll's fail when attempting to write to this branch.
Solution:
Pervasive.SQL 2000 Service Pack 2 provided a fix for this by moving some of the keys to the HKEY_CURRENT_USER branch.
A workaround for Pervasive.SQL 7.0 or 2000 Pre-Service Pack 2 users is to add additional permissions to the Pervasive registry key for those users.
You can add the permissions to the entire Pervasive subkey which will allow the users to change and use non-default settings listed in the local setup or configuration utility.
At a minimum, users will need to have read\write\modify access to the
HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Communications Requester\Version 7.00\Settings
subkey.
WARNING: Please take extreme caution while editing registry. Editing your registry is dangerous and can disable your operating system causing you to have to reinstall all your software. Pervasive Software Inc. will not be responsible for any mishap due to registry changes.
Run Regedt32
Browse to
HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Communications Requester\Version 7.00\Settings
Go to Security - Permissions, and select the Advanced button.
Select the Users group or the appropriate group for your Pervasive users.
In addition to the default permissions of
Query Value, Enumerate Subkeys, Notify, and Read Control,
add
Set Value, Create Subkey, and Delete.
This will show in the Entries list as a separate value with Special permissions.
Windows 2000 includes a set of text-based security template files that you can use to apply uniform security settings on computers within an enterprise.
You can apply these templates to group policy objects using the Group Policy Editor snap-in in Microsoft Management Console (MMC), or you can apply them directly to a specific computer using the Security Configuration and Analysis MMC snap-in.
The templates modify security settings incrementally and do not include the default security settings. The assumption is that the templates are to be applied to Windows 2000-based computers that have been installed cleanly, (that is, not upgraded from Microsoft Windows NT 4.0 or an earlier version of Windows). Computers that are upgraded from Windows NT do not use the default Windows 2000 security settings, but instead use whatever security settings were in place prior to the upgrade.
More Information
The security templates are:
Basic: Basicwk.inf (Windows 2000 Professional), Basicsv.inf (Windows 2000 Server), and Basicdc.inf (domain controller)
The Basic templates specify default security settings for all security areas, with the exception of user rights and group membership.
Secure: Securews.inf (Windows 2000 Professional)and Securedc.inf (domain controller)
The Secure templates provide increased security for areas of the operating system that are not covered by permissions, including: increased security settings for the account policy, increased settings for auditing, and increased security settings for some well-known security-relevant registry keys. Access Control Lists (ACLs) are not modified by this template, because the assumption is that default Windows 2000 security settings are in effect.
Highly Secure: Hisecws.inf (Windows 2000 Professional) and Hisecdc.inf (domain controller)
The Highly Secure templates are provided for Windows 2000-based computers that operate in native Windows 2000 environments only. Requires that all network communications be digitally signed and encrypted at a level that can only be provided by Windows 2000. Computers configured with this template cannot communicate with downlevel Windows clients.
Compatible: Compatws.inf (Windows 2000 Professional)
The Compatible template opens up the default permissions for the Local Users group so that legacy programs are more likely to run. This configuration is not considered a secure environment.
First Published: Jun 10 1999 8:07AM
Keywords: kbtool kbinfo
Gil
At the end of this is a Microsoft article about it. Notice at the very end it talks about he compatibility template. You will have to locate it on MS site.
The reason for this is that Windows 2000 changed the default permissions for Users in the HKEY_LOCAL_MACHINE branch from read\write to read-only. The Pervasive requester dll's fail when attempting to write to this branch.
Solution:
Pervasive.SQL 2000 Service Pack 2 provided a fix for this by moving some of the keys to the HKEY_CURRENT_USER branch.
A workaround for Pervasive.SQL 7.0 or 2000 Pre-Service Pack 2 users is to add additional permissions to the Pervasive registry key for those users.
You can add the permissions to the entire Pervasive subkey which will allow the users to change and use non-default settings listed in the local setup or configuration utility.
At a minimum, users will need to have read\write\modify access to the
HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Communications Requester\Version 7.00\Settings
subkey.
WARNING: Please take extreme caution while editing registry. Editing your registry is dangerous and can disable your operating system causing you to have to reinstall all your software. Pervasive Software Inc. will not be responsible for any mishap due to registry changes.
Run Regedt32
Browse to
HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Communications Requester\Version 7.00\Settings
Go to Security - Permissions, and select the Advanced button.
Select the Users group or the appropriate group for your Pervasive users.
In addition to the default permissions of
Query Value, Enumerate Subkeys, Notify, and Read Control,
add
Set Value, Create Subkey, and Delete.
This will show in the Entries list as a separate value with Special permissions.
Windows 2000 includes a set of text-based security template files that you can use to apply uniform security settings on computers within an enterprise.
You can apply these templates to group policy objects using the Group Policy Editor snap-in in Microsoft Management Console (MMC), or you can apply them directly to a specific computer using the Security Configuration and Analysis MMC snap-in.
The templates modify security settings incrementally and do not include the default security settings. The assumption is that the templates are to be applied to Windows 2000-based computers that have been installed cleanly, (that is, not upgraded from Microsoft Windows NT 4.0 or an earlier version of Windows). Computers that are upgraded from Windows NT do not use the default Windows 2000 security settings, but instead use whatever security settings were in place prior to the upgrade.
More Information
The security templates are:
Basic: Basicwk.inf (Windows 2000 Professional), Basicsv.inf (Windows 2000 Server), and Basicdc.inf (domain controller)
The Basic templates specify default security settings for all security areas, with the exception of user rights and group membership.
Secure: Securews.inf (Windows 2000 Professional)and Securedc.inf (domain controller)
The Secure templates provide increased security for areas of the operating system that are not covered by permissions, including: increased security settings for the account policy, increased settings for auditing, and increased security settings for some well-known security-relevant registry keys. Access Control Lists (ACLs) are not modified by this template, because the assumption is that default Windows 2000 security settings are in effect.
Highly Secure: Hisecws.inf (Windows 2000 Professional) and Hisecdc.inf (domain controller)
The Highly Secure templates are provided for Windows 2000-based computers that operate in native Windows 2000 environments only. Requires that all network communications be digitally signed and encrypted at a level that can only be provided by Windows 2000. Computers configured with this template cannot communicate with downlevel Windows clients.
Compatible: Compatws.inf (Windows 2000 Professional)
The Compatible template opens up the default permissions for the Local Users group so that legacy programs are more likely to run. This configuration is not considered a secure environment.
First Published: Jun 10 1999 8:07AM
Keywords: kbtool kbinfo
Gil
- Thread starter
- #6
Hi Gil,
Are you saying that I can use W2k security template to automate the process of adding extra security for normal user?
Can you please give me the template that add Set Value, create subkey and delete to Btrieve Technologies?
Thanks a lot!
Are you saying that I can use W2k security template to automate the process of adding extra security for normal user?
Can you please give me the template that add Set Value, create subkey and delete to Btrieve Technologies?
Thanks a lot!
The security template opens up the registry so that that Btrieve can write to the registry. It does not add additional security for normal users it actually removes some security that Win2K places on the registry. Our MCSE is the one who tracked it down and does the installs. I will see what details I can get from them, but you may also be able to get the answer from which is Microsoft's site where you can search regarding the templates. Gil
- Thread starter
- #8
Here is a document from Pervasive about the Windows 2000 security issue that provides a different approch.
The user had insufficient rights to create a registry key on Windows 2000 server.
Problem Description:
The user had insufficient rights to create a registry key on Windows 2000 server.
Running the Setup Win32 utility locally on an NT server errors with "The user had insufficient rights to create a registry key"
Problem Environment:
Pervasive.SQL v7
Microsoft Windows 2000
Solution:
Run Regedt32 (not Regedit).
Browse to highlight the Hkey_Local_Machine\Software\Pervasive Software key.
From the Menu - Go to Security - Permissions
Click Add
Select SYSTEM from the list of users and click Add, and then OK.
On the security screen that comes up next, highlight the SYSTEM user, and check the Full Control box under the Allow column.
Before clicking Apply, click the Advanced button and check the box
"Reset permissions on all child objects and enable propagation of inheritable permissions"
Click Apply and say OK.
NOTE:
Editing your registry is dangerous and can disable your operating system causing you to reinstall your software. Pervasive Software will not be responsible for any mishap due to registry changes.
Gil
The user had insufficient rights to create a registry key on Windows 2000 server.
Problem Description:
The user had insufficient rights to create a registry key on Windows 2000 server.
Running the Setup Win32 utility locally on an NT server errors with "The user had insufficient rights to create a registry key"
Problem Environment:
Pervasive.SQL v7
Microsoft Windows 2000
Solution:
Run Regedt32 (not Regedit).
Browse to highlight the Hkey_Local_Machine\Software\Pervasive Software key.
From the Menu - Go to Security - Permissions
Click Add
Select SYSTEM from the list of users and click Add, and then OK.
On the security screen that comes up next, highlight the SYSTEM user, and check the Full Control box under the Allow column.
Before clicking Apply, click the Advanced button and check the box
"Reset permissions on all child objects and enable propagation of inheritable permissions"
Click Apply and say OK.
NOTE:
Editing your registry is dangerous and can disable your operating system causing you to reinstall your software. Pervasive Software will not be responsible for any mishap due to registry changes.
Gil
- Status