I've got some strange Errors with Client 4.9 SP1.
We're currently using Client 4.83 SP2 with no error...
The Error is appearing as followed:
We've got a AXIS StorPoint CD E100/IDE (CD-Tower, caches CD's and DVD's to
make them accessible in the network). We've cached the MS Encarta2004 DVD.
I've created a MSI-Snappshot to distribute the App. With Client 4.83 SP2,
everything works fine.
With Client 4.9 SP1, I get an MSI Error 1603 (which means a file could not
be found). After this Error everything seems buggy...there are different
mapped drives that stop working, on some network-drives I get Errors that
the Server isn't supporting Long Names (but it does!) ending in BlueScreen
trying to copy down/up files.
Also accessing the AXIS StorPoint isn't working anymore.
With Client 4.83 SP2, I've never seen this error and also cannot reproduce
it.
It seems that in the beginnig of distributing Encarta, something goes
wrong, so the client is hanging itself up. A reboot is the only thing that
get the client back working.
I've installed the latest firmware on the Axis StorPoint, I've tried to
recache the DVD a few times, burned a copy and cached it...also tried to
tweak the client settings (burst mode, file caching, timeouts, ...), but
without success...
Any Ideas what to do or what to try?
Thanks a lot
Raffael
There are a lot of similar reports in this forum. CD towers (AFAIK)
all emulate NW 3.x (or earlier), and the 4.9 client doesn't work well
with them. Stick with 4.83SP2e.
Donald Albury
Novell Product Support Volunteer SysOp
Sorry, no replies to e-mail responses
I would also try installing both 4.9SP1 and the latest beta nwfs.sys
posted on Friday.
Donald Albury wrote:
--
Craig Wilson
CNE3, 4, 5 - MCSE - CCNA
NSC Sysop (http://support.novell.com/forums/)
Tech Writer - http://www.ithowto.com
(I Peter 4:10)
You're my Hero for the Day!
Firmware was already the latest installed!
But Beta NWFS.SYS fixed the Bug!!!!!
Thanks for your hint, Graig!
Raffael
I'm still having file access problems with my NW51 SP6 servers. Looks like
I'm going to have to back off all my clients to 4.83 SP2.
Anyone have a better suggestion?
....Gregg Nicholas
Give us some details about your environment.
IP, IPX or both bound to the client? NSS or traditional volumes? What name
resolvers (ie. protocol components) are active in the client?
--
Tony Pedretti
TransUnion LLC