Packages with buisness functions fail on deployment server after rename

We are running EnterpriseOne version 8.10.

Last week we renamed our deployment server using the "How to change out a deployment server" document from peoplesoft's web site.

Since then, any packages that we create in the DEP810 environment on the deployment server fails to be able to build the business functions.

Here is what I know:

Update packages containing BSFNs from a FAT Client work.

If I create the package on the deployment server and then log on to a FAT client and just click, "Submit Build", it works.

If I build a package on a FAT client and just click "Submit Build" on the deployment server, the BSFNs still fail.

Nothing in the debug.log that leads me to the problem.

Here is the only error in the builderror.log:

6/1/2005 13:47:54 0 Call BUSBUILD to build the business functions.
6/1/2005 13:48:29 0 ERROR: At least one parent DLL was not built correctly. Check buildlog.txt in the work directory for details.
6/1/2005 13:48:30 0 Final size of spec files: count 34 size 77334.
6/1/2005 13:48:30 0 Check for compression Records.
6/1/2005 13:48:30 0 Update Parent Package, DVFL040905.


Here is the buildlog.txt:


BUILD LOG
Package: DEPTEST4
Date: Wed Jun 01 13:48:08 2005
Build Machine: NA1CRDEP01
Path Code: DV810
Source Path: \\NA1CRDEP01\E810\DV810\package\DEPTEST4
Foundation Path: \\NA1CRDEP01\E810\system
Destination Path: \\NA1CRDEP01\E810\DV810\package\DEPTEST4
Build Business Functions: DEBUG

Generating source for NER and TER...

CALLBSFN : BSFN: N0000146...

Wed Jun 01 13:48:14 2005




D:\PeopleSoft\E810\PLANNER\BusObj is deleted before recreation.

Copying \\NA1CRDEP01\E810\DV810\package\DVFL040905\lib32\sCALLBSF.lib to \\NA1CRDEP01\E810\DV810\package\DEPTEST4\lib32\sCALLBSF.lib
Copying \\NA1CRDEP01\E810\DV810\package\DVFL040905\work\jdertdll.c to \\NA1CRDEP01\E810\DV810\package\DEPTEST4\work\jdertdll.c
Generating Makefile: D:\PeopleSoft\E810\PLANNER\obj\CALLBSFN.mak
.Makefile generated.

Building business functions.

************CALLBSFN************

N0000146.c
jdertdll.c

Option selected to discontinue build on errors. Build stopped.
Wed Jun 01 13:48:26 2005

************Build Finished************

CALLBSFN.dll - 0 error(s), 0 warning(s): Build failed. Restored previous dll.


This is just for one business function for testing...

I'm not sure where else to go with this....have any of you run accross anything like this before?

THANKS!!!

sd

Since noone responded I'll go ahead and post the fix for this. It seems that when we renamed the Deployment server (Running Windows 2003) the Microsoft felt the need to put some code in there that replaced every environment variable that points to Microsoft Visual C++ to point to the wrong drive - it is installed on the C: drive and it changed all of the environment variables that reference it to the D: drive. We didn't physically switch out the box and we didn't change MSVCPP in any way so I'm not sure why renaming the server and adding it to a domain would change these variables....wonderful Microsoft.