Cannot find REVDEBUG.DLL (OpenInsight Specific)
At 05 APR 2000 05:34:56AM Oystein Reigem wrote:
A premature question, perhaps. Expect more info from my client later. But here goes, anyway:
Anybody had a problem where starting OI results in a "Cannot find REVDEBUG.DLL" message? OI version: 3.61. Workstation: NT. Server: Warp. No network product.
I did a search on "REVDEBUG.DLL". There's a posting where Cameron mentions a bug fixed in 3.7.1. But so far I might have too little info to see if the cases are similar.
- Oystein -
At 05 APR 2000 08:50AM Don Bakke wrote:
Oystein,
We've seen this before. In our situation it happened when the workstation wasn't configured correctly and the network traffic was very heavy. This is similar to the "SYS1000: Unable to load REV_LOADREC" error.
One way to confirm network traffic/configuration problems is to temporarally switch to the older Byte Range driver. This usually allows everything to work fine under these conditions. If so, then it's usually just a matter to getting the machines to be configured just right.
At 05 APR 2000 09:01AM Oystein Reigem wrote:
Don,
Thanks! I've relayed your message to my client. Whose name by coincidence is also "Thanks". But in German - "Dancke". (Have I had that lunch yet? And who is Fhopha?)
- Oystein -
At 05 APR 2000 09:30AM Matt Sorrell wrote:
Oystein,
To pick just a tiny little nit, "thanks" in German is spelled "Danke" (no "C"). So, it seems like your client is a bit of an over-achiever…
At 05 APR 2000 09:58AM Oystein Reigem wrote:
Matt,
You're right of course! And I love nitpicking! Vielen Danke!
- Oystein -
At 06 APR 2000 05:38AM Oystein Reigem wrote:
Don,
My client's back with some more information.
We've seen this before. In our situation it happened when the workstation wasn't configured correctly and the network traffic was very heavy. This is similar to the "SYS1000: Unable to load REV_LOADREC" error.
Network traffic is very light indeed - my client's mostly been alone on the network while he tried. But he suspects configuration.
One way to confirm network traffic/configuration problems is to temporarally switch to the older Byte Range driver. This usually allows everything to work fine under these conditions. If so, then it's usually just a matter to getting the machines to be configured just right.
Switching to Byte Range Locking did not help.
My client'll be back yet again with more info next week…
Thanks a lot so far!
- Oystein -
At 06 APR 2000 06:28PM Robert Lee wrote:
Oystein
We have had one site that had both the REVDEBUG.DLL and the REVLOADREC problem that Don mentioned. It was a largeish site with plenty of loading. We simulated the REVDEBUG.DLL problem by literally physically unpluging the workstation connection from one of the switches while OI was running. In other words, it seems OI detects that a problem has occured (lost touch with the server) and immediately attempts run the debugger (which it can't because it has lost touch with the server).
Basically we traced the problem to a problem either with the server itself or the fibre optic cable to the server. By installing a different server that by-passed the fibre cable (installing it next to the workstation actually), the system ran fine.
Hope this helps.
Robert
At 07 APR 2000 04:17AM Oystein Reigem wrote:
Robert,
Thank you! I'll mail your posting to my client. Hope this leads him in the right direction.
- Oystein -
At 07 APR 2000 04:27AM Oystein Reigem wrote:
Robert,
Just a thought: In your particular case you don't really know if it was the server or the connection? Were all WSs connected via that f-o cable? If not - wouldn't it be a good idea to try with the same server from a WS connected differently?
- Oystein -
At 09 APR 2000 09:44PM Robert Lee wrote:
Oystein
Thanks for the thought. Thankfully its not really our problem. We just had to prove it wasn't OI or us causing the problem. Their technical people are following it up. Its a bit like that oldie but goodie …
Q.How many programmers does it take to change a light bulb?
A.None. Its a hardware problem.
Robert
At 12 APR 2000 03:34AM Oystein Reigem wrote:
Got more info about something I aired last week - about a problem where a client of mine has problems running an OI app.
To summarize:
- Starting OI results in "Cannot find REVDEBUG.DLL" message
- OI version: 3.61
- Workstation: NT 4.0
- Server: Warp
- Network product: None
- Network driver: NPP 1.5; switching to Byte Range Locking doesn't help
- Network traffic: Very light
Now my client says it helps if he first closes Lotus Smartcenter. But even with Lotus Smartcenter closed, it's still not too stable. The app may hang after having run for a while. And sometimes there's still that error message at startup - more often the second time he starts the app than the first.
He wonders if there might be some network resource that gets exhausted.
He's tried to change the autoexec.nt and config.nt files, but I believe the settings there are for MS-DOS programs only?
Help, comments and suggestions still welcome!
- Oystein -
At 12 APR 2000 08:10PM Robert Lee wrote:
Oystein
A few extra thoughts for you as I think our experience may be applicable. We conclusively proved that faulty hardware was involved by using a "Fluke" device that we plugged into the network and which monitored the traffic. It was able to detect a very high number of Errors both before OI was loaded and also while OI was loading up.
After we installed a whole new server which avoided the F.O. cable, we were able to demonstrate with the fluke device that there were no longer any errors.
Thus, I suspect your solution will be found by checking / replacing various bits of hardware like the server, network cards, switches / hubs, cables etc. Therein I suspect your problem will hide.
The value of the fluke device cannot be understated for diagnosis and helping the customer to see it wasn't our problem. Customers find it very hard to believe that something can be going wrong in the network because the lights still flash and it works sometimes. The fluke device gives us "eyes" to actually see what exactly is happening.
One other thought. NT.4 / Service Pack 6 is a big no no. Microsoft has conceeded that they have bugs that affect Winsock applications (which include OI). We took the whole network back to service pack 5.0. There is an article in the knowledge base on this subject.
If I knew how to insert a link I would do it for you…
Robert Lee
At 13 APR 2000 03:37AM Oystein Reigem wrote:
Seems the culprit has been found. My client thinks his Lotus
Smartsenter hadn't been installed properly. When he removed it everything ran fine.
Thanks to all who tried to help us with this issue!!!
- Oystein -
At 13 APR 2000 05:19AM Oystein Reigem wrote:
Robert,
Thanks for your time and effort. If you've seen my other posting today you'll know the cause in all probability was something else.
What you say about that "Fluke" device is interesting. A colleague of mine says there's also software you can youse to check network traffic.
A problem with our clients is they're spread all over our wrinkly, oblong country, and neither of us have any budget for travelling.
- Oystein -
PS. Inserting a link became easy since some time last year. Just key or paste in the URL.
If you want a nicer looking link start with
where URL is the URL, TEXT is the text that will be blue and underlined. And then you have to surround the two html codes with square brackets! I.e, put a in front of each .