Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 28 AUG 2006 03:09:26AM Tony Lillyman wrote:

I have a client who migrated a 2000 server installation of AREV 2.12

to a 2003 Server installation.

I access it via a Citrix connection

This morning I was able to login fine no errors no changes to

Network Driver (that I am aware of)

Not when I start AREV (with no parameters OR with parameters)

I received the following message

All Networks Driver 2.1.0.0

Unable to access linear hash files

Error=FS231
 File=1

Any assistance greatly appreciated!

Tony


At 28 AUG 2006 08:13AM Kevin Ruane wrote:

Tony,

They have no problem accessing it locally?

When you get an FS231 with either the 1.5 Service or the 2.1 Service it usually points to some sort of mapping or pathing issue with the client.


At 28 AUG 2006 11:36PM Tony Lillyman wrote:

All other users on the Network can start AREV fine.

It's just me. As an "outsider" (coming in via Citrix)

via a remote desktop.

What should I tell them to look for ??

How can I check that I have access to the NT Service ??

Thanks

Tony


At 29 AUG 2006 12:59AM Warren Auyong wrote:

Where is Citrix running? It should not be on the same server as the LH service. Make sure the Citrix server has access rights to the 2003 server and that the ARev application definition is mapping the same drive letter as the regular users. You may need to create a working shortcut to ARev on the Citrix server's desktop and point the application definition to that.


At 29 AUG 2006 01:33AM Tony Lillyman wrote:

Warren

IT Guy at the client tells me they only upgraded the Citrix

server to 2003Server.

The main network server is still W2000Server.

They utilise Active Directory so it GOT to be related to what

I'M able to see/do/read/write etc on the server.

Yesterday I could do stuff - like normal

Today - zip!

I can see AREV in the folder, create/delete/modify txt files

etc but AREV.EXE can't communicate with the LH Service on the 2000

box when I starting AREV. Oddly enough neither can the IT Manager

when logged in on his "normal" username.

When logged in with Administrator Rights - no problems

NOW the solution …

I re-mapped the Drive L: which AREV run from using NET USE

ie NET USE L: /DEL

then NET USE L: \\Server2000\ApplicationFolder

and then it works ?!!!?

Anyway it works

Tony


At 29 AUG 2006 12:18PM Warren Auyong wrote:

FWIW I have a mapped drive on my XP pro station that I have to reconnect manually each time I restart the station despite clicking the 'reconnect at login' setting. I haven't figured it out yet because all the other mapped drives connect without intervention.

Glad you got it working…


At 04 SEP 2006 05:46AM [email protected] wrote:

My guess is that the original mappings have a different set of access logic. You can probably set up a login script to do that automatically, but you'd be better off setting the correct credentials initially.

[email protected]

The Sprezzatura Group Web Site

World Leaders in all things RevSoft


At 04 SEP 2006 05:48AM [email protected] wrote:

I use the loopback adapter to map some local shares to a network drive, mostly out of historical habit going back ages. tcp/ip apps (mozilla, gaim, sam spade, etc) go on H, Revelation products on X, client systems on S. For some reason, X doesn't always reconnect, though the others are always fine. If I ever work that out, I'll let you know.

[email protected]

The Sprezzatura Group Web Site

World Leaders in all things RevSoft


At 05 SEP 2006 10:38PM Barry Stevens wrote:

This is very timely.

I have to move an Arev2.1 system to W2003 server with some workstations using terminal services.

Is there an issue with record locking with work station ids.

Do they have to be faked by running prog on startup, or was this just a terminal services version issue.

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/e9cc162147cc0029852571d800275136.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1