Vault, IIS on DHCP
Moderator: SourceGear
Vault, IIS on DHCP
hi all,
I have a vault server running in a VM on my main dev machine (laptop). To get the server to work where I work, it needs to be on DHCP which of course also makes it easier when I plug it in at home.
when at home (where I installed IIS and vault), vault works great but logged in at work on the work dhcp address vault will not work. /VaultService runs ok but the asmx returns error 80070545 in the event log. This error points to a user rights issue on the aspnet account. I have given that account full rights to the root of .net framework directory and of course it works anyway when at home so I think this is probably not the problem anyway.
IIS is set to function on any IP address so I'm stumped as to why any application won't run when this machine boots at the work environment.
Has anyone esle experienced anything like this?
I have a vault server running in a VM on my main dev machine (laptop). To get the server to work where I work, it needs to be on DHCP which of course also makes it easier when I plug it in at home.
when at home (where I installed IIS and vault), vault works great but logged in at work on the work dhcp address vault will not work. /VaultService runs ok but the asmx returns error 80070545 in the event log. This error points to a user rights issue on the aspnet account. I have given that account full rights to the root of .net framework directory and of course it works anyway when at home so I think this is probably not the problem anyway.
IIS is set to function on any IP address so I'm stumped as to why any application won't run when this machine boots at the work environment.
Has anyone esle experienced anything like this?
I'm going to need some more information.
When you are testing whether you can connect to the server on your machine or not, are you doing that right from the same machine, or are you trying it from a different machine?
Can you send me a copy of the log you mentioned and a copy of the server log? You can either sent a private message to me with that in the forum or send me an email at beth at sourcegear.com. When sending an email, reference this forum post so I don't lose you in the never-never land of the email pile.
When you are testing whether you can connect to the server on your machine or not, are you doing that right from the same machine, or are you trying it from a different machine?
Can you send me a copy of the log you mentioned and a copy of the server log? You can either sent a private message to me with that in the forum or send me an email at beth at sourcegear.com. When sending an email, reference this forum post so I don't lose you in the never-never land of the email pile.
Thanks for the reply.
I am developing on a laptop but I have a virtual machine on that laptop which runs XP, IIS, Vault (single user) and SQL2000. So to sort of answer your question, yes it's on the same machine but no it's not really as it's connecting to a VM.
The virtual machine has bridged networking so it gets it's own DHCP address and as I said, when i boot my machine at home it all works fine. Booting the laptop then the VM on it at work the http://localhost/vaultservice/vaultservice.asmx gives me 'Server application Unavailable'
The Error in the Event log is:
As I mentioned the error code in the log points to a user rights issue of the asp account but I have given it full rights to the appropriate directory and anyway, it works fine when booting at home using the same login.
Thanks
Nev
I am developing on a laptop but I have a virtual machine on that laptop which runs XP, IIS, Vault (single user) and SQL2000. So to sort of answer your question, yes it's on the same machine but no it's not really as it's connecting to a VM.
The virtual machine has bridged networking so it gets it's own DHCP address and as I said, when i boot my machine at home it all works fine. Booting the laptop then the VM on it at work the http://localhost/vaultservice/vaultservice.asmx gives me 'Server application Unavailable'
The Error in the Event log is:
Code: Select all
Event Type: Error
Event Source: ASP.NET 1.1.4322.0
Event Category: None
Event ID: 1084
Date: 8/31/2006
Time: 5:35:32 PM
User: N/A
Computer: nevin_2K_VM
Description:
aspnet_wp.exe could not be started. The error code for the failure is 80004005. This error can be caused when the worker process account has insufficient rights to read the .NET Framework files. Please ensure that the .NET Framework is correctly installed and that the ACLs on the installation directory allow access to the configured account.
Thanks
Nev
I don't believe it's necessarily the IP address coming from DHCP. Obviously, the networks are different though. So you are running your server on your VM at work. Where is the client you are connecting from?
Is your server at work on a domain? Are you connecting from a different client at home than at work? Do you have a client right on the VM Vault Server that you can try connecting with?
Is your server at work on a domain? Are you connecting from a different client at home than at work? Do you have a client right on the VM Vault Server that you can try connecting with?
There is only ever one physical machine in play at either location: my laptop. On the laptop is the VM. Both the laptop and the Virtual Machine get a dhcp address from whichever network they are connected to at any time and they both use the same login connecting either direct to the domain (at work where it doesn't work) or the cached account on the same domain when at home.
Yes there is a Vault client on my laptop, on the VM and another machine on the network, None will connect to Vault when I'm at work, it just returns 'server application unavailable'.
Thanks
Nev
Yes there is a Vault client on my laptop, on the VM and another machine on the network, None will connect to Vault when I'm at work, it just returns 'server application unavailable'.
Thanks
Nev
Ok, lots of points to cover:
1. Can you load a client onto your VMware that has the Vault Server on it. After you have done that, then try to connect with that client from both locations and let me know the result.
2. Can you tell me what OS you are running in the VMWare? I wasn't sure if you were telling me you had XP on your laptop, or on the VM machine.
3. Think of your laptop and the VM as two entirely different physical boxes, as if you are taking two laptops home with you. The important one will be the VM. I'm assuming you are connected to an ISP from home and then VPN to work. That really places you in a different network. We really don't need to worry about the actual IP address itself. That won't be an issue here. What really is the issue is explained in the error: "the worker process account has insufficient rights". It is fine on your home network, but not at work. Those are two different networks as far as your server can tell.
4. Can you send me a Vault Server Log and your install log? (vault_install.log file is located in the windows temp directory (%temp%)) Placing the server log into debug mode will provide more information. You can send it to me either through the private feature here, or email it to beth at sourcegear.com. If you send via email, please reference this forum post so I match the correct log up.
5. Also, I just noticed that you hadn't answered the domain question. I need to know if your VM server is a member of the domain at work (ip addresses still don't matter here) or if it's a standalone machine. Look in your Control Panel and go into System. Under the computer name tab look at the line just under the computer name and you will either have a domain name there or a workgroup name. It might be helpful to just do that both for the VM server and for the laptop itself.
1. Can you load a client onto your VMware that has the Vault Server on it. After you have done that, then try to connect with that client from both locations and let me know the result.
2. Can you tell me what OS you are running in the VMWare? I wasn't sure if you were telling me you had XP on your laptop, or on the VM machine.
3. Think of your laptop and the VM as two entirely different physical boxes, as if you are taking two laptops home with you. The important one will be the VM. I'm assuming you are connected to an ISP from home and then VPN to work. That really places you in a different network. We really don't need to worry about the actual IP address itself. That won't be an issue here. What really is the issue is explained in the error: "the worker process account has insufficient rights". It is fine on your home network, but not at work. Those are two different networks as far as your server can tell.
4. Can you send me a Vault Server Log and your install log? (vault_install.log file is located in the windows temp directory (%temp%)) Placing the server log into debug mode will provide more information. You can send it to me either through the private feature here, or email it to beth at sourcegear.com. If you send via email, please reference this forum post so I match the correct log up.
5. Also, I just noticed that you hadn't answered the domain question. I need to know if your VM server is a member of the domain at work (ip addresses still don't matter here) or if it's a standalone machine. Look in your Control Panel and go into System. Under the computer name tab look at the line just under the computer name and you will either have a domain name there or a workgroup name. It might be helpful to just do that both for the VM server and for the laptop itself.
1. When at work I cannot even connect using the vault admin tool but it works fine when the machine is at home. The error response when logging in is the text display of a html page titled Server Unavailable
2. Host OS is WinXP SP2 (this has the VS.NET on it). VM has Win2k server (which has IIS, vault, and SQL2000)
3. My network at home is a workgroup and this laptop and VM are not part of that. Both of them are part of the same work domain and when at home it simply works in cached mode till I connect to a VPN. Either on the VPN or not, while at home, Vault will work. It only uses the network at home for the DHCP lease and obviously piggy backing on the internet connection.
So for a login, I always use the same login (on both machines) and 'connect' to the same domain either live (when in the office) or cached when at home.
The ASP account is obviously a local machine account (on the VM) and not part of the domain which is the same across all my situations.
4. I will send the log to you as soon as I've posted this.
5. Yes the VM is in the same domain as the host (my laptop)...my work's domain.
2. Host OS is WinXP SP2 (this has the VS.NET on it). VM has Win2k server (which has IIS, vault, and SQL2000)
3. My network at home is a workgroup and this laptop and VM are not part of that. Both of them are part of the same work domain and when at home it simply works in cached mode till I connect to a VPN. Either on the VPN or not, while at home, Vault will work. It only uses the network at home for the DHCP lease and obviously piggy backing on the internet connection.
So for a login, I always use the same login (on both machines) and 'connect' to the same domain either live (when in the office) or cached when at home.
The ASP account is obviously a local machine account (on the VM) and not part of the domain which is the same across all my situations.
4. I will send the log to you as soon as I've posted this.
5. Yes the VM is in the same domain as the host (my laptop)...my work's domain.
I think I may have fixed it.
I uninstalled all the frameworks I had on the vault server (1.0 and 1.1 sp1) and reinstalled 1.1 & sp1 and it now works when I'm at work which it never did before. It always worked at home which I will try tonight to verify.
EDIT: Works from home as well so everything seems ok now.
Thanks
I uninstalled all the frameworks I had on the vault server (1.0 and 1.1 sp1) and reinstalled 1.1 & sp1 and it now works when I'm at work which it never did before. It always worked at home which I will try tonight to verify.
EDIT: Works from home as well so everything seems ok now.
Thanks