I just installed the NT Service 1.5 onto a new NT file server, Intel server with 2 450 Pentium III processors. My client is using AReve 3.0. Using Arev at the file server operates at lighting speed. Great.

On one of my workstations, Areve operated extremely slow. On three other w/s, the operation was about 75% of the speed at the file server – which I suspect is probably expected. The next day, 2 of these fast w/s slowed down to a crawl, similar to the original w/s.

I've installed the NT service, it is active. Full rights are assigned to the SYSTEM user.

I don't understand the problem with the slowness of th w/s, particularly since the NT Service supposed to allow processing at the file server – not at the w/s.

Any suggestions or reasons for this would be appreciated.

Regards,

Frank S. Adamo

I'm having a similar problem with ARev 2.03 and NT Service v1.5.

So far I haven't come up with anything.

It's been suggested that you create a Revelation user with the NT Service. To do this, create an NT user account called Revelation and assign it the required rights to all LH files. On the Service window, set up the LH service so it logs in using this Revelation user. Although I have not tried it, it supposedly works.

[email protected]

Sprezzatura Group

Then what is the difference between creating a user called SYSTEM and a user called REVELATION.

Also, does that mean every user (my client has 15 Arev users) need to log into the NT server with as REVELATION? Also, any reason why Rev Tech doesn't know about this?

Aaron:

Thanks, I'll pass this on to the client's NT person and give it a shot.

Regards,

Warren

You don't create the system user. It's a part of NT, it's the system! There are two things going on here. One is that the service logs into NT as user SYSTEM. Since that's the default for any service, you have to make sure that the SYSTEM user has access to the NT files. Remember, this default is for all services, not just for LH. It's how NT works. The Revelation user is just a secondary user. Most services allow you to log on as a specific user instead of the default.

The way it was explained to me (I haven't actually done the research into this level of NT) is that when NT logs in a service as the system user, it has to share this user with all the other services, which is pretty much everything in NT. By creating the Revelation user, you're setting up a memory block just for the LH service.

As for why Revelation didn't tell you this, all I can say, is that's where I heard all this from.

[email protected]

Sprezzatura Group

Warren,

Are all your w/s config for a TCP/IP protocol? I know that Rev Tech said to remove the IPX protocol, but I didn't use the TCP protocol. Each new w/s I installed was configured automatically with IPX protocol. Removing the IPX protocol and inserting the Microsoft TCP/IP protocol cured the problem. Apparently talking to another tech (not that the first tech was not helpful), but he repeated what the first tech said about the IPX protocol. Also, he said that a Revelation User was not necessary anymore.

Now, I have only my w/s that is running fast, but not as fast as the others. I might just exchange mine with one of the employees.

Regards,

Frank

I have been given to understand that you should not run Arev on the NT file server, because it cannot access the NT service, but will write directly to the files. If another user is then accessing the files via the NT service, a GFE may result.

mailto:[email protected]

View this thread on the forum...