Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"object could not be read

Status
Not open for further replies.

andyrne

Technical User
Feb 15, 2001
43
GB
Myself and the support staff sometimes get "Object Could not be read" errors (110:-150)when attempting to administer nds (nw4.11) on winnt machines. Hard reset of pc sometimes fixes this. Errors only occur when using nwadmn32 (not nwadmnnt). Any Ideas? (This happens when trying to view props for some (random) objects)
 
Tyr copying the entire WIN32 folder to your hard drive..run NWADMIN from your hard drive..you will get a couple of dynamic errors when it first starts up..but it works for NT as well as 2000 DVannoy
A+,Network+,CNA
dvannoy@onyxes.com
 
Thanks, but the problem turned out to be with the server that had zen running on it (we had some zen profile-related problems also). A look at the cache stats, and later some console errors we started getting, told us we had a memory leak problem. A retart of the server fixed everything.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top