ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
GetNearestPackageServerInfo.aspx does not return the NS as a package server after a package server is added to a separate site
Article ID: 170337
GetNearestPackageServerInfo.aspx does not return the NS as a package server after a package server is added to a separate site.
The NS is not returned as a package server for the first site
When the site server in the second site was made a package server, the 'getnearestpackageserver' call no longer recognizes the NS as a package server because it technically isn't a package server. It just acts like one.
ITMS 7.x thru 8.x
Site one has the NS acting as a package server; site two has a site server acting as a package server.
Add the package server services explicitly to the NS via Site Services. The downside to this is that your packages will be doubled on the NS as the files will be copied from the NS directories to the package server directories
Install another package server in the site where the NS is located.