falklandtim
asked on
Virtual Server management Website https port busy
Hi Experts,
I'm having a bit of a problem with Microsoft Virtual Server. I have a MS Server 2003 standard which is running IIS6 and Virtual Server 2005 R2.
I have configured the managment website for the virtual server to be connected to via https, originally on port 1025. This in its self was simple to setup and work perfectly well until I shut down the box for the weekend. On returning the following monday, started the server and tried to log on to the management webpage I was presented with a "page cannot be displayed" error. After checking that I was infact typing the url correctly I checked IIS website for virtual server managment and found that it was not running. On restarting the webserver I was presented with the error "The process cannot access the file because it was being used by another process"
After much head scratching I ended up changing the https port number configured in IIS to 1026. On trying a restart of the webserver everything started to work as normal again.
The following weekend of course I shut the computer down. Monday arrived and yet again the same thing, when trying to access the virtual server management website i'm faced with an error.
On checking the IIS I see that the website is not working and again will not restart giving the same error "The process cannot find file..........". I then try changing the https port back to 1025, same message. Again I change the port back to 1026 and I still get the same error. I finally changed the port to 1027 and heypresto the webserver started.
Has anybody else out there seen this error and could you please help me with a fix, as i can't keep changing port numbers each time I restart the server.
Thanks guys, look forward to hearing your replies,
regards,
Tim
I'm having a bit of a problem with Microsoft Virtual Server. I have a MS Server 2003 standard which is running IIS6 and Virtual Server 2005 R2.
I have configured the managment website for the virtual server to be connected to via https, originally on port 1025. This in its self was simple to setup and work perfectly well until I shut down the box for the weekend. On returning the following monday, started the server and tried to log on to the management webpage I was presented with a "page cannot be displayed" error. After checking that I was infact typing the url correctly I checked IIS website for virtual server managment and found that it was not running. On restarting the webserver I was presented with the error "The process cannot access the file because it was being used by another process"
After much head scratching I ended up changing the https port number configured in IIS to 1026. On trying a restart of the webserver everything started to work as normal again.
The following weekend of course I shut the computer down. Monday arrived and yet again the same thing, when trying to access the virtual server management website i'm faced with an error.
On checking the IIS I see that the website is not working and again will not restart giving the same error "The process cannot find file..........". I then try changing the https port back to 1025, same message. Again I change the port back to 1026 and I still get the same error. I finally changed the port to 1027 and heypresto the webserver started.
Has anybody else out there seen this error and could you please help me with a fix, as i can't keep changing port numbers each time I restart the server.
Thanks guys, look forward to hearing your replies,
regards,
Tim
JjcampNR
Are you running anything else on IIS? It seems like you may have a few sites running over the same port. What else is on that machine?
ASKER
This is the only website on ISS and no other web server software.
If I disable the Virtual Server Web Server, create a new web server using https ports 1025 or 1026 all works fine. As soon as I change the web server home directory to the Virtual Server Web managment folder I'm faced with the same problem. There seems to be something in the Virtual Server Management website that is ties up these two ports.
Its really quite puzzling.
If I disable the Virtual Server Web Server, create a new web server using https ports 1025 or 1026 all works fine. As soon as I change the web server home directory to the Virtual Server Web managment folder I'm faced with the same problem. There seems to be something in the Virtual Server Management website that is ties up these two ports.
Its really quite puzzling.
Why are you changing the home directory to the Virtual Server folder? Did you decide to have the site run as the local system account or as the authenticated user account?
ASKER
I think you may be missing my point a little. I created the new site temporaraly to see if the problem was with IIS or Virtual Server. I changed the new sites home directory to the Virtual Server Management web directory to see if I would get the same problem with the ports 1025 & 1026. As the problem persisted with the temporary website I deducted that the problem was probably with Virtual Server and not IIS. I have since removed the temporary web server from IIS and enable the original IIS Virtual Server management web server again.
I'm haven't looked permissions for this website as it was created when the Virtual Server software was installed, I will have a look now though for interest sake.
Sorry for confusing the issue with the temp web server.
I'm haven't looked permissions for this website as it was created when the Virtual Server software was installed, I will have a look now though for interest sake.
Sorry for confusing the issue with the temp web server.
ASKER
Hi Administrators,
This question can now be closed.
regards,
Tim
This question can now be closed.
regards,
Tim
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.