cannot log in to monitor

[MacolaHelp]

psql200i/sp4 w/hot fixes, win2k sp4 server, clients are win2003 terminal, xp, win2k, win98. I have a Pervasive_admin group set up w/rights to the pvsw directory & share, rights to the registry keys on ts2003. The only way I can run pvsw monitor from a workstation is to be logged on as domain admin. I have reviewed & tried all docs at pervasive knowledge base, including doing the active directory permissions. Nothing allows me to get to monitor except as a member of domain admin or higher. Suggestions?

 

[TomKane]

When you say logged in as domain admin do you mean that the PC has to be logged in that way or that you have to log into monitor that way.

 

[MacolaHelp]

I must log in to the pervasive monitor as a user who is a domain admin. I can be logged into the network pc as anyone, domain admin or not.

 

[Chipsta]

Have tried during non production hours to start and stop the relational engines?(pervasive.sql 2000(relational)) This will force the server to update itself and reconnect.

I have had similar issues and the fix was to start and stop the services. A hard reboot doesn't always work, sometimes , the service start and start trick does not work and you have to Use the Kill command .
Kill ntbtrv.exe and w3sqlmgr.exe . Restart Both engines thru services and you should be up and going.

Hope this helps

Chip

 

[TomKane]

I saw this in my P.SQL8 manual:

If you are trying to create a new database on the server, to use Monitor against the remote server engine, or to use Configuration against the remote server engine, you must have administrative rights on the server, or be a member of Pervasive_Admin. A simple drive-mapping or shared-file read will not tell you whether you have administrative rights. This means you may be able to connect to the file server, but you still may not be able to connect to the database engine with Configuration, Monitor, or Create Database Wizard.

 

[BtrieveBill]

In short, you have two options:
1) Log in as an administrative user on the box. This can be a Domain Admin, or possibly a local admin account as well. The account MUST have administrative rights AND have the "Log On Locally" right assigned to it. With this solution, your account must have full access rights to everything.

2) If you don't want the DBA to have full access, then do this: Create a local group called Pervasive_Admin on this server. Add user accounts to this group. Be sure the accounts have the "Log On Locally" right. (No other rights are needed, however).

Either way will work...


Bill Bach
Goldstar Software Inc.

http://www.goldstarsoftware.com

 

[MacolaHelp]

Is the group name case sensitive? I have Pervasive_admin. Should it be Pervasive_Admin? In active directory it is a security group-domain local. On the group properties the Pervasive_admin group has full permissions on the security tab. Under local security settings\local policies\user rights assignment\local on locally is enabled for Pervasive_admin but effective setting is not. What I am missing here?