Need help on LNS..anyone?

[poochz]

I'm not new to LNS, but this problem has me stumped big time..Echelon isn't any help right now.

The cause: I was accessing the LNS database from a workstation, with the LNS DB located on a network server, and the server was rebooted (what are the odds?!), breaking the connection to the LNS tool. After the server came back up, I now get a "The operation cannot complete because an object required is in use - NS #39" error.

I've tried creating a new DB, copying the files over. Using Validation tool, LNSObjectbrowser, LONMaker, copying the db to a new folder etc..nothing will open up this database anymore. It's like one of the db files never closed properly, but I can't figure out which folder or how to fix it.

Any help would be appreciated. I have a report to Echelon, and waiting a response, but I can't hold my breath...they only respond fast when you spend 245$ per tech support call.

Thanks,
Pooch

[amigo]

I'm not new to LNS, but this problem has me stumped big time..Echelon isn't any help right now.

The cause: I was accessing the LNS database from a workstation, with the LNS DB located on a network server, and the server was rebooted (what are the odds?!), breaking the connection to the LNS tool. After the server came back up, I now get a "The operation cannot complete because an object required is in use - NS #39" error.

I've tried creating a new DB, copying the files over. Using Validation tool, LNSObjectbrowser, LONMaker, copying the db to a new folder etc..nothing will open up this database anymore. It's like one of the db files never closed properly, but I can't figure out which folder or how to fix it.

I am no expert, but I would guess this is related to a database corruption related to network interface portion of the database.

I have seen similar issues before with dialup connections when the line drops unexpectedly.

I hope you have a backup copy of db before this happened. Echelon told me that they can fix the db if I sent it to them, but I can not verify this.
If all fails, you can take a chance and delete all traces of NI in the corrupted database using the browser and see if you can revive it. If I remember correctly, I had some success doing this, but this is risky.

good luck.

lcaErrNsObjectInUse 39

A requested operation can't complete because the object involved in the operation is in use. For example, you may not be able to delete a node because that node is still included in connections.

[lontshooter]

The error refers to the process of the DB is in use.
OPen Task Manger on the server and stop the following process if they are running: LCAMON.EXE, this is the primary one to look for, they may be other LNS process running, they need to be stop also, after you have stop the process then you need to restart the server.
Then open the original database, make sure that you check the following box "Show all network option dialogs". When the database opens back up go thru each screen and make sure you have write access the DB.
This should clear you issue.

Lontshooter

[sysint]

It's like it thinks the DB is still connected. Open up LNS utilities and select close all networks.

[poochz]

Oh well...
I've tried the suggestions (thanks), but no avail. I've actually tried on 3 seperate PC workstations, so nothing was running. The LNS Utilities won't even open the db. I've resorted to a previous backup and am reediting...live and learn, backup often with LNS! Echelon is famous for corrupt databases and now this..maybe 2.0 will actually work without sending the dbs to Echelon.

Thanks for the responses..
pooch

[crab master]

I had a problem just backing up and I tried following the known issues and workarounds but that just made things worse. I can tech support and Echelon's tech support was great. They logged into my PC and spent about 4 hours going through it and fixing the issues at no charge.