Novell. No NLM. Problems (re)create file?????? (None Specified)
At 12 AUG 1999 09:30:00AM Oystein Reigem wrote:
(Posted on both Works and plebs lists.)
I'd be very grateful for comments to/help with the following…
Case: Single user developer OI 3.61 app resides on Novell network server with Netware 3.12. No NLM. App is run from Win98 client with Novell Netware Client 3.00. App tries to delete the only index of a table, and thereafter create the index again. Since it is the only index the index table's REV?????.LK and OV files are deleted when the index is deleted, but afterwards the app is unable to create the files again.
At least that's my theory. Or the theory of a guy at the site.
Netware driver (Netdrv.exe) is NPP (as adviced on this list). But a change to Netware seemed to fix the problem.
Does this make sense?
I think perhaps the problem appeared with change from OI 3.3 to 3.61.
Also - what is the difference between IPX/Netware (LHIPX.DLL) and Netware drivers (LHNOV.DLL)?
- Oystein -
At 12 AUG 1999 12:45PM Rob Misek wrote:
Oystein–
[i]Netware driver (Netdrv.exe) is NPP (as adviced on this list). But a change to Netware seemed to fix the problem.[/i]Just to clarify, if you use the All Networks driver the problem persists? And if you change it to the Netware Multi-User Driver the process works. Is there an error message that displays when they try and reapply the index? Take a look at this Knowledge Base article. It shows where each part of the index information is stored. Check to see in this case after the index has been deleted if each of these parts of the index have really been deleted.
Also - what is the difference between IPX/Netware (LHIPX.DLL) and Netware drivers (LHNOV.DLL)?
I am not sure as to the low-level differences of the two other than the IPX/Netware Multi-User ver. 1.5 is configured to be used with the Revelation NLM as oppossed to the Netware Multi-User Driver ver. 2.0.
Rob
Revelation
At 13 AUG 1999 02:01AM Stefano Cavaglieri wrote:
Oystein,
maybe a silly question… what "Directory trustee rights" have been assigned to your login name for that directory (I'm talking about your Netware config)? Is "Create" enabled?
Stefano
At 13 AUG 1999 03:25AM Oystein Reigem wrote:
Stefano,
maybe a silly question… what "Directory trustee rights" have been assigned to your login name for that directory (I'm talking about your Netware config)? Is "Create" enabled?
Are there such things as silly questions in our line of business?
![]()
The guy I referred to in my posting claims to be very competent and experienced when it comes to Novell networks. But I'll ask him. Later, when I can get hold of him.
But wait a minute. If "Create" wasn't enabled - how come things worked when he changed driver from NPP to Netware? Wouldn't it fail with any driver then?
Thanks for helping me with this.
- Oystein -
At 13 AUG 1999 05:37AM Oystein Reigem wrote:
Rob,
]]Netware driver (Netdrv.exe) is NPP (as adviced on this list). But a change to Netware seemed to fix the problem.
]Just to clarify, if you use the All Networks driver the problem persists? And if you change it to the Netware Multi-User Driver the process works.
Yes. And now I think it's the same thing at a different site.
Is there an error message that displays when they try and reapply the index?
This index stuff is done programmatically. There's a Delete_Index( … ) followed by a Create_Index( … ). The programming is my own. Looking at it now I discover some dodgy programming, but nothing that explains the problem. What's dodgy is the way I check for errors. I must have programmed this when I knew even less about error checking and handling than today.
![]()
Here's the code:
<code> Set_Status(0) Delete_Index( ... ) if Get_Status(ErrCodes) then /* Dodgy pt 1 - error handling totally missing. */ /* At least there should be a warning issued here. */ /* (I think I had some code here that I deleted */ /* during a period with repository problems...) */ end Set_Status(0) /* Dodgy pt 2 - @FILE_ERROR cannot be trusted */ /* to contain anything useful here I think. */ /* And I don't even display the contents of */ /* @FILE_ERROR - just a general warning. */ if @FILE_ERROR '' then call msg( @Window, '*** Perhaps not able to delete the index' ) end</code>
And then the same thing with Create_Index instead of Delete_Index.
So when you ask if there's an error message displayed the only thing I can say is that sometimes @FILE_ERROR is not null. I should have been able to tell you if it was after Create_Index or Delete_Index, but I didn't ask my clients.
Take a look at this Knowledge Base article. It shows where each part of the index information is stored. Check to see in this case after the index has been deleted if each of these parts of the index have really been deleted.
Good idea.
So what you say is that a change of driver perhaps removed the original cause of the problem, but there might still be damage to the index files? That might be the case at one of the sites. When I said things work with the Netware driver that wasn't quite true. At that site things improved in general, but a couple of tables/indexes still have problems. I'll get them to mail me the contents of their data location.
]]Also - what is the difference between IPX/Netware (LHIPX.DLL) and Netware drivers (LHNOV.DLL)?
]I am not sure as to the low-level differences of the two other than the IPX/Netware Multi-User ver. 1.5 is configured to be used with the Revelation NLM as oppossed to the Netware Multi-User Driver ver. 2.0.
Aha.
Thanks a lot for helping me with this.
- Oystein -