Make sure your networker remote exec service on bigbeast is running a user that can get administrative access to the snapserver.
At standard Networker installation the service runs as "local system".
Restart the service after the effective user change.
You do not need the bigerbeast...
Stephan,
If this client is a Compaq and has a Gbit card you may have a driver problem.
Assuming the above is true search the forum for fixes:
1. a change in the registry
2. a new driver version
Hope this helps,
Itzik
You will have to install components 2,3,4 to have snapimage operational.
As regarding to changing files, it should not be harmfull...
To be on the safe side you can make a copy of both files prior to the install and make a diff between the original ones and the new/updated ones.
As for...
The saveset field (as many others) are limited in their length. The limit is around 1k.
The effective limit might be even shorter as the savefs command including all the savesets list should be less than 1024 characters.
I would follow the following steps:
1. Shutdon Networker - To sto any JB activity
2. Erase all *.lck files in .../nsr/tmp
3. Restart networker.
4. Reset the jukebox with "nsrjb -HEvvvvv"
5. Re-inventory the jukebox with "nsrjb -Ivvvvv"
6. You should be ready to go.
This may have to do with the level of the server/client you are running.
I think that this feature has been added at 5.1 or maybe just 5.5.
Both the server and the client have to be above this version to have (record) the information in the client definition.
When you do a "savegrop -pvvvvc...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.