Windows Server 2008 / IIS 7...
I am trying to setup and CI environment using TeamCity 4. So far so good, VisualSVN Server / Subversion repository is all set, TeamCity is monitoring it, and firing off the build. I can use the TeamCity Webapp via http:localhost:8080 with no problem. My issue is that I can't access the TeamCity webapp remotely from my development machine. I feel like this is problem with the Apache / Tomcat configs, but don't even know where to begin. Anyone have any thoughts?
I installed TeamCity 3.2.x on a Windows 2008 server and didn't run into any problems hitting it remotely, but you may want to check the firewall to see if it's open on port 8080. Windows Firewall > Inbound Rules > sort by port, and see if you have a rule defined for local port of 8080. If not, add it.
IIS Manager might be worth looking into too... (Start > type IIS Manager) And look at the site settings for TeamCity
It's also possible that if IIS is running properly, you'll be able to hit the machine locally on port 80, just to confirm general connectivity.
Related
I'm currently running into an issue that is occurs when my Visual Studio TFS Server deploys a test agent to a remote server. According to documentation:
You will need a minimum of two machines - a target server or virtual
machine to deploy to, and an agent machine that drives the
deployment. [Check]
You should use an agent machine that is in the same domain and
network as the target server(s). Communication from the agent to Team
Services or TFS is over HTTP/HTTPS, while communication from the
agent to target server(s) is uses the WinRM protocol. [Partial Check
Our TFS server is located on domain Awhile our target server is ondomain B.]
This is according to the documentation for deploying ASP.NET apps to domain-joined machines using WinRM.
To limit the scope closer to the actual issue I'm having is that the deploy process seems to fail once configuration begins for the test agent. More specifically TestAgentConfiguration.ps1 PowerShell script that is ran on the TFS Server when being deployed to the target server. The requirements for this specific script as described on the github page is:
.NET 4.5 on Windows7 SP1 or Windows 2K8R2 [Check]
Test machines should have PSRemoting enabled (run 'Enable-PSRemoting'
on Windows Powershell) ###WinRM setup This task uses the Windows
Remote Management (WinRM) to access domain-joined or workgroup,
on-premises physical or virtual machines. [Check - This command seems
to only run once the machine has the firewall turned off (after a
reboot). Our domain group policy disables Windows Firewall by
default, so when running the above PowerShell command it works.
However, if we enable the firewall (which seems to fix my issue) for
the initial configuration of the TestAgent then the command no longer
works both with and without the firewall. This is only fixed once
rebooting the server]
We have followed documentation based off what is presented on the Support Additional Help pages. However, I'm still confused on why the working solution for this deployment process requires Windows Firewall to be enable for any part of the configuration as on the Pre-Requisites says "There is no inbound communication from Team Services or TFS to the agent, or from the target server to the agent. This means that you do not need to open any firewall ports on the agent machine, but you do need to open the WinRM port on the target server(s)."
I'm under the impression that since our environment is on two separate domains (A & B) where domain B trusts domain A there are some additional steps that are checked with the firewall. However, with the configuration step failing during deployment when the Firewall is disabled, it will pass with the Firewall Enabled. Any further consecutive runs/deployments with the Firewall then disabled still pass making the initial Firewall check useless.
I have each step's "TestAgentConfig.log" described in the summary which is saved on the target server for each step in the attempts that I made, however due to my post I'm limited to a certain limit of characters.
Summary:
Fresh reboot of target server, kicked off a build with the Windows
Firewall Turned Off --> Build Fails
On that same server without a reboot, turned on Windows Firewall
--> Build Successful
On that same server without a reboot, turned off Windows
Firewall --> Build Successful
I wonder if anyone has encountered the above issue:
I was able to install the server successfully but when it comes to run the utility that configures the octopus settings, I get the following error
One or more windows features need to be enabled before continuing.
and then I get this afterwards:
"DISM.exe /Online /Enable-Feature /FeatureName:IIS-ASPNET
/FeatureName:IIS-NetFxExtensibility /ALL"
In order to enable the missing feature.
This has now been done successfully. But everytime i try to run Octopus deploy administrative tool I keeping getting the same error.
Is there something I'm missing regarding components I need to have on to the 2012 windows server.
I have never encountered the errors you are mentioning. That said, have you performed a full GUI install of Octopus Deploy, or just the server core? To make it work properly on Windows Server 2012 you need to do a full GUI install.
This must be quite an old version of Octopus - only the 1.x versions required IIS to install the Octopus server (and I don't think it supported Server Core).
The 2.x and 3.x versions don't use IIS (we are a self-hosted NancyFX service).
I built a signalR service that my WPF application uses and in development everything worked fine (since its running locally).
When it came to test environment, when I published it (on remote windows server 2008 r2 as windows service) I had error connecting.
The service runs on port 8080 and when I tried to run it on port 80 (I had to remove IIS for that) it worked fine so I assume its firewall problems.
I need an explanation of how to make it work (I had in mind that maybe because its duplex connection things work different) and since its for intranet app i'll have to ask my IT manager for opening these ports,
As the question says, I have a problem running the web app on local IIS.
Here is my situation:
WIndows over Oracle VM VirtualBox running on Linux Ubuntu.
Bridged Adapter so that Windows box gets local IP from my router.
Visual Studio 2010 + sp
WCF REST Service application plugin for project template
The application runs when using visual studio development server (on localhost).
Target framework is v4.0
What I need is that the application runs on IP instead on localhost (so I can consume it on remote computer in LAN), so I configured IIS7.
Here is IIS configuration:
I created a website with target framework v.4.0
I binded the site to my local IP on port 80
Path to the site is /inetpub/wwwroot iisstart.htm as default document
IIS runs ok. If I open "http://my_local_ip" I get the welcome logo.
The problem is in visual studio.
When I go to project properties "Web" section and select local IIS over vsd server is where I get lost. If I set "Project URL" to "http://my_local_ip/some_name" visual studio complains that it cannot find IIS server and so it was unable to create the virtual directory. I tried manually adding virtual directory in IIS manager, but no effect. If I use "http://localhost/some_name" as the "Project URL" the virtual directory gets created, but it makes no sense does it?
Could some one please enlighten me?
If I use "http://localhost/some_name" as the "Project URL" the virtual directory gets created, but it makes no sense does it?
I think you are mixing two different things here. When you ask VS to use localhost as the IIS Server for your project, it will connect to the local IIS to perform configuration tasks. If you ask VS to use "my_local_ip" you are telling VS that you IIS Server is remote, and therefore VS will use remote administration to configure IIS (VS can't know that my_local_ip is the local computer).
But remote IIS admin isn't enabled on a default WinServer box. Furthermore, it would require some additionnal network config. You should therefore tell vs to use the local server.
In fact, IIS site bindings and VS deployment parameters are too completely different things. So, deploy your site on http://localhost/your_site.
However, I don't really like the prospect of using VS debugging deploy to deploy a real app. The directory will contain all your project files... You should:
create your site on IIS manager and setup a virtual directory.
Either
ask VS to publish the site to a directory (your virtual directory)
ask VS to publish a WebDeploy package, then ask IIS manager to import the package.
I have a VM on my Win 7 machine running Server 2008. My website can't run properly unless it's running on the server due to COM+, other website integration and environment variables. Currently, I have VS2008 installed on the Windows Server 2008 and I develop there (which is dumb, I know) instead on in my Win 7 workstation. I hate this setup.
My question is, how can I developer on my workstation and then EASILY push and test th websites on the VM Server?
Access files across the network so the actual changes are made on the VM Server?
Make changes locally and publish to VM Server?
Can I set up VS2008 so that if I when I Run the application in VS2008 it pushes everything over and opens a web browser that points to the VMServer's IIS Website?
Of course, the VM is a server on your network. Exactly like any other server on your network, virtual or otherwise.
For debugging you can setup VS2008 to remote debug but I think you'd have to publish the site, start it and then hook up the debugging but I'm happy to learn that there's an easier way... anyone?