Results 1 to 10 of 10

Thread: Build/Deploy fails after server move

  1. #1

    Build/Deploy fails after server move

    We are on JDE E1 9.0, tools 9.1.4.7.

    This weekend, our IT team moved our JDE non production servers (enterprise server and web server) to another location. IP addresses changed in the process. After the server move, testing our non production systems seem to go ok. We could not find anything that referenced the servers by IP address so we though we'd be ok.

    However, the problem we have found is on our deployment server (JDEDEPLOY). When I try to build and deploy a package to test after the server move, it fails. The build appears to function ok, but the deploy ends in error with a message that 'File not found'.

    In the logs, for both the build and the deploy, we are getting errors that our non prod enterprise server, JDEENTD, can't be found.

    So it appears that somewhere on the deployment server, JDEENTD is referenced by IP address, but we can't find it.

    Any advice on how to find the reference that might need to be changed, we would appreciate any assistance.

  2. #2
    Senior Member craig_welton's Avatar
    Join Date
    Oct 2000
    Location
    Litchfield, CT
    Posts
    1,012
    Do you have an entry for JDEENTD in the hosts file of the deployment server?
    Craig Welton
    PatWel Group Inc.
    http://www.patwel.com
    Home of the FREE JDE Object Browser, JDETrace, NERDup and BusBuild+ Tools

    E1 9.0 8.98.4.2 Wintel SQL 2008
    E1 9.2 9.2.1.4 iSeries

  3. #3
    Thanks Craig, but what is the table name or menu name to look at the hosts file. I'm not familiar with it.

  4. #4
    It's an OS level thing, file is located here c:\windows\system32\drivers\etc\hosts Make sure you don't have JDEENTD hard coded to its original IP address.

  5. #5
    Senior Member craig_welton's Avatar
    Join Date
    Oct 2000
    Location
    Litchfield, CT
    Posts
    1,012
    It's not a JDE table, it's an operating system configuration file. Look in C:\Windows\System32\drivers\etc for a file called hosts. That is where you can connect a machine name to an IP address manually (not using a name server)
    Craig Welton
    PatWel Group Inc.
    http://www.patwel.com
    Home of the FREE JDE Object Browser, JDETrace, NERDup and BusBuild+ Tools

    E1 9.0 8.98.4.2 Wintel SQL 2008
    E1 9.2 9.2.1.4 iSeries

  6. #6
    Yes, I found the hosts file at C:\Windows\System32\drivers\etc. Don't see anything though that would help us. I've been told by the IT team that they server move would change the IP address for JDEENTD from 10.12.3.142 to 173.something. So we are thinking somewhere we will find this 10.12.3.142 reference or JDEENTD reference.
    Attached Files Attached Files

  7. #7
    Senior Member craig_welton's Avatar
    Join Date
    Oct 2000
    Location
    Litchfield, CT
    Posts
    1,012
    From a command prompt, on the deployment server, type this: nslookup JDEENTD
    Craig Welton
    PatWel Group Inc.
    http://www.patwel.com
    Home of the FREE JDE Object Browser, JDETrace, NERDup and BusBuild+ Tools

    E1 9.0 8.98.4.2 Wintel SQL 2008
    E1 9.2 9.2.1.4 iSeries

  8. #8
    Here is the results for my nslookup. Looks like its referencing the new IP address 172.17.3.124, but the old one too somehow 10.12.3.124.
    Attached Files Attached Files

  9. #9
    Senior Member craig_welton's Avatar
    Join Date
    Oct 2000
    Location
    Litchfield, CT
    Posts
    1,012
    I would share that with the CNC, IT group.
    Craig Welton
    PatWel Group Inc.
    http://www.patwel.com
    Home of the FREE JDE Object Browser, JDETrace, NERDup and BusBuild+ Tools

    E1 9.0 8.98.4.2 Wintel SQL 2008
    E1 9.2 9.2.1.4 iSeries

  10. #10
    Quote Originally Posted by James Monroe View Post
    We are on JDE E1 9.0, tools 9.1.4.7.

    This weekend, our IT team moved our JDE non production servers (enterprise server and web server) to another location. IP addresses changed in the process. After the server move, testing our non production systems seem to go ok. We could not find anything that referenced the servers by IP address so we though we'd be ok.

    However, the problem we have found is on our deployment server (JDEDEPLOY). When I try to build and deploy a package to test after the server move, it fails. The build appears to function ok, but the deploy ends in error with a message that 'File not found'.

    In the logs, for both the build and the deploy, we are getting errors that our non prod enterprise server, JDEENTD, can't be found.

    So it appears that somewhere on the deployment server, JDEENTD is referenced by IP address, but we can't find it.

    Any advice on how to find the reference that might need to be changed, we would appreciate any assistance.
    Ask your network guys what the DNS TTL is. If DNS still has not updated the new IP address your name lookup will return the old IP address.

    Also, do ipconfig /flushdns on the Deployment server.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.