Max 6 in Windows 2000 administrator works, standard users dont?

Just to put a bit more info here:

The db is located on a server share over the network.

The same user from 98 can log on and access the DB fine.

So basically ONLY the administrator on the domain can log into the DB and open max.

The standard user does get prompted for the username and password for max over the domain so its not a share issue and as stated the exact same user can do everything fine from windows 98.

I tried accessing it from a standard user that has NO group policies on the domain and get the same thing:

1. max splash
2. pervasive icon in task bar
3. logon box for the max db on the server
4. after user and pass is in .. it sits.. tries to open it .. the buttons splash up for a second and boom im sitting at my desktop.

No errors what so ever .. just a clean .. buh bye to max. Pervasive icon stays going in the taskbar.

Is there some right / permission im missing here? I at a loss.

Thanks

Trent

This error message typically occurs to a Domain User working with Windows 2000 or XP, its biggest implication being user rights to the HKEY_LOCAL_MACHINE in the registry.

A Domain user needs full control rights via Regedt32 to;

HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software
HKEY_LOCAL_MACHINE\SOFTWARE\MultiAtive Software

Go to Start>Run and type 'regedt32' for win2k and 'regedit' for XP

This error can also occur if a User has restricted rights across the network, can they create and delete a simple text file in the shared database folder? If not then they need to be given the rights to do this, because whilst using Maximizer you theoretically continually updating the contents of this folder.

In some extreme circumstances this error has occurred when an Address Book has been assigned a password unintentionally. Check this in;

File>Preferences>Security>Folder Password (or in the case of Maximizer 7, load the ‘Administrator’ program and go to File>Preferences)

Regards
CABC Support

>Is there some domain group (tried power user and it doesnt work)

Just for the record:

"Power Users" is a local group, not a global group. Adding users to the "Power Users" group on a server does not make them "Power Users" on every machine in the domain - it only boosts their privileges on the server itself (which is not helpful because they almost certainly don't log onto the server anyway).

In my experience, adding the appropriate users (or group of users) to the "Power Users" group on each Win2K workstation has worked in circumstances such as you have described.

Thank you .. the registry perms and power user info worked like a charm.

Thnx for helping a fellow CDN Gord