Re: [Deployment Server Recovery - Help Needed]

b_gilmore

Well Known Member
Re: [Deployment Server Recovery - Help Needed]

I would copy off the existing B7333 folder on the deployment server.

Get out CD 1 of the deployment server installation and reinstall 1 path code
(for speed). Once complete, rename the B7333 off and put the original B7333
folder back.

There are some other things like ESU ODBC DSNs that you'd have to manually
recreate to get sync'd back up.



jde_cnc <[email protected]> wrote:
deployment server to a known Win2K registry-write error. We were able to
reinstall Win2k without disturbing the existing program files, but receive
numerous errors when trying to log into OW. Some background:1) No backups were
being made of the deployment server2) No custom objects were ever created3)
All components of JDE seem to be in place, but there are clearly some
disconnects after Win2K was reinstalled, specifically the registry and jde.ini
files.Any thoughts on how to recover this? Also, any thoughts on our ability
to simply reinstall OW on the deployment server, and manually recreate server
identities, etc? What else would be required to restore the DS as a valid
server?Again, this is a very small and simple install with only a couple of
fat clients. The primary database is still 100% intact.All suggestions are
greatly appreciated.
 
Re: [Deployment Server Recovery - Help Needed]

Usually the DSN's can be copied off a fat client in your Deployment server environment. Export the registry entries for ODBC and import it on the DS.

What is the error message/condition that is being displayed?
 
Back
Top