Skip to main content

Hi everybody..

I recently converted a big maximizer 3.x database( > 1 Gig in total) to maximizer 6.0 peer to peer. (thanks to Gord Thompson, for his help).


I installed Maximizer server version on a NT server machine running exchange. Database files are located on the same machine. And this machine also acts as the gateway for maximizer files.

There are 9 maximizer users running Win98 Me.

The problems are:

Maximizer is very very slow after the conversion. The workstation machines on thenetwork still crash with error code 3111/3112. Sometimes users get a message box saying: database in use and maximizer is waiting to access the files.

I used regedit to increase the number of remote sessions to 60 (from 30) but that didn't help. frown


[This message has been edited by anthony1 (edited 28 March 2001).]
Original Post

Replies sorted oldest to newest

>I installed Maximizer server version on a NT server machine

Just to clarify: You ran the Maximizer 6.0 setup on the NT Server and made the following selections:

Pervasive Database Engine Setup
( ) Only this computer
(x) Multiple computers on a peer-to-peer or server-based network
( ) Multiple computers on a Pervasive Client/Server network

Maximizer Database Server Option
( ) Workstation
(x) Server


Correct? If so, then you need to pre-load the Workgroup engine so the other machines can talk to it. The most common way is to:

- set the NT Server to automatically logon when it boots, and

- add a shortcut to the Startup folder ("All Users" preferred) that runs

C:\PVSW\BIN\W3dbsmgr.exe –btrv


If it has been set up correctly you should see the Pervasive Database Engine icon (little computer with a green light) in the system tray near the clock after the machine boots.


(BTW, I've also tried using srvany.exe from the NT Server Resource Kit and that seems to work, too.)
Additional notes:

1. You must remember to run the Gateway Locator utility to specify the machine that is to serve as the workgroup's gateway. There should be a file in the address book folder called "~pvsw~.loc" with its read-only attribute set.

2. Unless Multiactive has changed its position on this, they do not support running the Workgroup Engine on an NT Server. If this setup continues to cause you grief you might consider

- installing the Client/Server version of P.SQL_2000 on the NT Server, or

- using another machine as the workgroup gateway.
>could there be something wrong with the network?

Possibly, but you'd think that other applications that use network services would complain as well.

Have you checked the Pervasive "Supported Protocols" setting on the server and the workstations to make sure that they match and that all unused protocols have been removed?

If so, then you could try fiddling with the "Application Performance" slider on the "Performance" tab of the System control panel to see if that makes any difference. It could be that the other stuff running on that machine (esp. MS Exchange) is crowding out the Workgroup engine. You could also try using Performance Monitor to gain some insight into where the bottleneck might be (memory, I/O, network, ...).

>A salesperson at Multiactive said Maximizer 6 will work on NT server.

FWIW, in my past discussions with Maximizer Support they've said that they don't support running the Workgroup Engine (or other foreground applications like MaxExchange) on NT Server because NT Server is optimized to run services, while NT Workstation is optimized to run applications.
There is a patch 2a for the workgroup engine at www.pervasive.com and multiactive has recently given the ok to patch 3 for the workgroup engine. As a test to see if it is the NT server or the network that is giving the 3111 and 3112 error try installing the WGE onto a users PC and making that the gateway. Because the data and the gateway are on different machines users may notice a increase in time to log into Maximizer.
>Just to clarify...
>
>Should I run gateway locator on gateway machine only!
>
>OR
>
>do I have to run gateway locator in every workstation machine to
>specify the gateway.

You need to run the Gateway Locator utility once per Address Book folder, preferably from the gateway machine. The point is to create the ~pvsw~.loc file in each folder that contains Maximizer address book files (mxz?.max).

Add Reply

Post
LEGAL INFO
CONTACT US
Copyright 2007-2018 Advoco Solutions Ltd. All Rights Reserved.
×
×
×
×
Link copied to your clipboard.
×