• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 354
  • Last Modified:

Netware Deployment Manager - Fatal Error

I have been given the go ahead to continue my Netware 5.1 to 6.5 migration. I have the pre-migration server to a point where I am trying to add it to the existing tree, and it is telling me to run the deployment manager. I stick the cd into my trusty workstation and run the thing. When I try to click on View and Update NDS, it tells me a fatal error has occured and shows me the location of a log. The log says the following:




*** Open log 08/25/2004 15:12:38 CDT ***

______
Driver
Informational: Beginning installation.
______
Driver
Informational: Input response file is: ..\DATA\UPDATENDS.IN
______
Driver
Informational: Input response file was UPDATENDS.IN found in location
    file:/C:\Program Files\Common Files\Novell\NIS30\data\..\DATA
______
Driver
Informational: NIS Record-Manager v1.0
______
Driver
Fatal: Could not initialize the Shipping Profile in
    driver.initShippingProfile().
______
Driver
Fatal: (java.lang.ClassNotFoundException)
    com.novell.application.install.updatends.UpdateNDSProduct
______
Driver
Fatal: java.lang.ClassNotFoundException: com.novell.application.install.updatends.UpdateNDSProduct
      at java.net.URLClassLoader$1.run(Unknown Source)
      at java.security.AccessController.doPrivileged(Native Method)
      at java.net.URLClassLoader.findClass(Unknown Source)
      at java.lang.ClassLoader.loadClass(Unknown Source)
      at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
      at java.lang.ClassLoader.loadClass(Unknown Source)
      at java.lang.ClassLoader.loadClassInternal(Unknown Source)
      at java.lang.Class.forName0(Native Method)
      at java.lang.Class.forName(Unknown Source)
      at java.io.ObjectInputStream.resolveClass(Unknown Source)
      at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
      at java.io.ObjectInputStream.readClassDesc(Unknown Source)
      at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
      at java.io.ObjectInputStream.readObject0(Unknown Source)
      at java.io.ObjectInputStream.readObject(Unknown Source)
      at java.util.Hashtable.readObject(Unknown Source)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at java.io.ObjectStreamClass.invokeReadObject(Unknown Source)
      at java.io.ObjectInputStream.readSerialData(Unknown Source)
      at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
      at java.io.ObjectInputStream.readObject0(Unknown Source)
      at java.io.ObjectInputStream.readObject(Unknown Source)
      at com.novell.application.install.Profile.<init>(Profile.java:117)
      at com.novell.application.install.Profile.scanForProfiles(Profile.java:1642)
      at com.novell.application.install.Driver.initShippingProfile(Driver.java:2075)
      at com.novell.application.install.Driver.work(Driver.java:1018)
      at com.novell.application.install.Driver.run(Driver.java:861)
      at java.lang.Thread.run(Unknown Source)

______
Fatal errors           3
Recoverable errors     0
Unknown errors         0
Warnings               0
Informational messages 4
Total logged messages  7
*** Close log 08/25/2004 15:12:49 CDT ***

*** LOG END MARKER, DO NOT REMOVE ***

I cannot continue. I just went to java.com and installed java on this machine. Then, I restarted my browser/deployment manager...but that did not help.

Any ideas?
0
eidson
Asked:
eidson
  • 3
  • 2
1 Solution
 
ShineOnCommented:
Are you manually adding the pre-migration server to your existing tree before running the Migration Wizard?

If so, don't.  It should be in its own temporary tree, and when the Migration Wizard is done,  it will rename the new server with the old server's identity and reboot,  and remove DS from the old server and shut it down.
0
 
eidsonAuthor Commented:
Just to veryify what you are telling me:

I should install it to it's own temporary tree.

I had already done this. Then I was told by someone at Novell that I would have to add it to the existing tree so that both servers could see each other and that would be the only way for me to 'migrate' everything.

So that is wrong. I should install it to it's own tree? Just want to make sure as I've been given until noon tomorrow to migrate the server and and let all the school's users log into the new server.

BTW, thanks for the quick response!

Eidson
0
 
eidsonAuthor Commented:
One more thing...

Does the new dDirectory tree need to be named the same as the other tree or something new? I was under the impression it needed a different name.
0
 
ShineOnCommented:
No, you have to have them both on the same network segment so both servers can see and be seen by the Migration Workstation, and you have to be able to log in as Admin on both servers.   I don't know who at Novell would have told you to add a pre-migration server to your production tree in order to do the migration.

Go ahead and follow the directions that come with the Migration Wizard.  Make sure you download the most recent one from the Novell support website.

The temporary tree that the pre-migration install is set up in should be different from the production tree.  You don't have to rename the production tree.  I usually use "TEMP" for the tree name when doing the pre-migration install.

The temporary tree name goes away when the Migration Wizard transfers DS and the old server's identity to the new box.
0
 
eidsonAuthor Commented:
Thank you. I still am not sure whether or not this will fix the error I was receiving while trying to run the deployment manager... however, you have definately set me on the correct path again.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now