We've had a row locked by the Win2000 service for a few days - do I have to unload the service to get it to relaese the lock - or is their another way. I machine crashed while processing this row.
We have rebooted the machine and all the other machines running OI.
Thanks
Bob Watson
Bob,
I am afraid you need to restart the service. I am curious, is the service by chance using TCP/IP?Pat
We have three sites using the 2.1 Service using TCP/IP. All get problems of record locks not being released.
The site that tried using NamedPipes swapped back to TCP/IP and began getting the problem again.
We've tried replicately the problem without success, so it's pretty obscure. A site with around 10 casual users is getting around 1 dodgy lock a day.
Paul
Paul-
We have a new DLL for you to try out. It was meant to address a rare chance of the symptoms you are describibng.
Send an email to [email protected] and we'll get it to you tomorrow.
Thanks-
Mike Ruane
Great! Thanks for your help as always.
Paul
Pat
Yes it is. I will try switching to Named Pipes ] TCP/IP. Maybe this will fix the Arev Thunk Driver GPF problem.
Bob Watson
Bob,
Actually, I meant either TCP/IP direct or Named Pipe-]TCP/IP. Both type of TCP/IP connections work identically after initialization. See this announcement with regards to your original locked row problem:[url=http://www.revelation.com/THEWORKS/OIdiscuss.nsf/ef8405490de3608f85256700005245e4/1c7faa46eac1214585256c630048d4e3?OpenDocument]Locks using TCP/IP with 2.1 Service[/url]I hate to ask ;-), but what is the AREV Thunk Driver GPF problem?Pat
]
I hate to tell, but AREV GPF'ed on load , using the Thunk driver on Win 2000 service. Now it comes up with fs1019 errors after upgrading win NT with every patch available. So I don't use AREv on the live files anymore. I'm waiting for an upgrade to XP to see if that cures it. But maybe Named Pipes to TCP/IP might do it…
Bob Watson
Bob,
What is the configuration of the workstation that this happens on?Pat
Pat
]
It's Win NT service pack 6.2? (the last one anyway). It does use the Novell Client to log on but we run the Win 2000 service on our Win 2000 server.
Bob
Bob,
I am sorry, but could you give once again the current status of this workstation with regards to the AREV Thunking Driver. It is not clear from your prior message if it still crashes, or is now getting FS1019. I think you indicated that it no longer crashes, but returns the FS1019, right?I would try the following different configurations to try to trouble shoot this:
1. Does OI access these files okay?
2. Can AREV access these files using Named Pipes and the regular driver?
3. Can AREV access these files using Named Pipes and the Thunking driver?
4. With the NT Service shutdown and the ServerOnly parameter removed, can AREV access these files using the regular driver?
5. With the NT Service shutdown and the ServerOnly parameter removed, can AREV access these files using the Thunking driver?
Pat
Before I get to your other questions…
I've just switched to Named Pipes ] TCP/IP mode. OI works fine in both modes
AREV works (locks rows between OI and AREV) in this mode using the regular driver but it GPF's using the thunking driver. Does this mean I am in fact using just named pipes?. How can I verify which mode I'm using, both for OI and AREV.
Thanks
Bob Watson
Bob,
The regular AREV driver does not have the ability to do TCP/IP because there is not a standard TCP/IP api at the DOS level, so you must be using Named Pipes for the AREV access if that is the driver in use. There is a way to determine what mode the client driver is in using the LH2 Stats facility that is currently in development.I forgot about OI16 versus OI32. OI16 also has a regular and a thunking driver that might provide more information if we know what combinations of it work.I just ran AREV with the thunking driver using a pure TCP/IP protocol on my Win2000 workstation and it ran perfect for me. Your Novell Client log on has me wondering if that has something to do with your GPF. Do you have other "cleaner" workstations to test against?Another item is creating a LH2.LOG file to see how far along the thunking driver is getting.You are going to have to help me here by isolating what is causing your machine to fail, whereas all of the machines we have testing against work.Pat
Pat
So you are saying that AREV will use Named Pipes only even though I set up the server to use Named Pipes ] TCP/IP? (I did stop and start the service after editing the registry by the way). If so is it ok to have AREV using named Pipes and OI using Named Pipes ] TCP/IP accessing the same files? Id this a 'yes' then I need to verify that OI32 is using Named Pipes ] TCP/IP. We don't need to use TCP/IP in AREV - I use to as a glorified editor for OI these days - you can't beat it.
After I changed the mode to Named Pipes ] TCP/IP I tryed to load OI32 again - it GPF'ed. Then I took out the line in the revparam file which set the port number for TCP/IP - OI then worked fine.
I realise I'm not answering your questions but I'll get to them!
Bob Watson
Pat
So you are saying that AREV will use Named Pipes only even though I set up the server to use Named Pipes ] TCP/IP? (I did stop and start the service after editing the registry by the way). If so is it ok to have AREV using named Pipes and OI using Named Pipes ] TCP/IP accessing the same files? If this is a 'yes' then I need to verify that OI32 is using Named Pipes ] TCP/IP.
We don't need to use TCP/IP in AREV - I use it as a glorified editor for OI these days - you can't beat it.
After I changed the mode to Named Pipes ] TCP/IP I tryed to load OI32 again - it GPF'ed. Then I took out the line in the revparam file which set the port number for TCP/IP - OI then worked fine.
I realise I'm not answering your questions but I'll get to them!
Bob,
So you are saying that AREV will use Named Pipes only even though I set up the server to use Named Pipes ] TCP/IP?
Yes, it will. OI also will if run on the same machine because Named Pipes are much faster than TCP/IP when communicating between processes on the same physical machine.
If so is it ok to have AREV using named Pipes and OI using Named Pipes ] TCP/IP accessing the same files? If this is a 'yes' then I need to verify that OI32 is using Named Pipes ] TCP/IP.
Yes, this is okay, the NT Service can operate against both types of connections at the same time just fine.
We don't need to use TCP/IP in AREV - I use it as a glorified editor for OI these days - you can't beat it.
Great! Then just use Named Pipes.
After I changed the mode to Named Pipes ] TCP/IP I tryed to load OI32 again - it GPF'ed. Then I took out the line in the revparam file which set the port number for TCP/IP - OI then worked fine.
There seems to be something strange about that machine and TCP/IP. I am still wondering if the Novell Client software installed has messed up the TCP/IP stack somehow and is causing your GPF'es. Again, all of the machines we have tested this on work just fine.
Pat
Pat
Thanks for your responses - At least I have a working configuration now.
I'm assuming that OI is using Named Pipes ] TCP/IP but I will wait for the tool that you mentioned to verify this.
Thanks again
Bob Watson