I have a scenario that I can't seem to find a good solution to. I have two servers in my SharePoint farm, one of them is the legitimate web front end that external users connect to, the other is not publicly accessible and holds the databases and SQL reporting services integration.
The issue that I have is that on the first server the IIS web application directories were set up on the D drive, while on the second server the IIS directories are on the C drive. Normally this does not cause any issue at all, however when I try to deploy a custom solution it fails with the error:
SQLSERVER : https://mainapp : MainApp : Error: The web.config is invalid on this IIS Web Site: D:\inetpub\wwwroot\wss\VirtualDirectories\443\web.config
Where SQLSERVER is the second server in this deployment, which has the web config on the C drive. Because of the way this was set up, and the bureaucracy involved in changing it, this cannot be changed; and as it stand now, I cannot deploy solutions to the farm because they always fail with this error. It is evident that SharePoint looks in the same place for the web config on every server that extends that web application.
Given this scenario, I have two questions:
1) Is it possible either through AAMs or another mechanism to tell SharePoint to look in different places on each server for the web config?
- or -
2) Is it possible to selectively retract the web application from individual servers in the farm?
Thanks in advance!