since 1-2 months I have problems on some machines in my environment when I try to connect via RDP.
The environment configuration uses a Microsoft PKI (Windows Server Certificate Authority). All computers that are integrated in the domain, request and are given a certificate from:
Computer
RDP (as server)
All machines in the domain have the ROOT CA and SUBCA certificate installed.
The problem is intermittent, on the same machine it does not work, the computer is restarted and for a while it works.
The credentials with which I connect work and the user with which I connect has permissions for RDP (he is a domain administrator).
When I connect using the FQDN (pc1.mydomain.com) the window to enter credentials appears, I enter them correctly and it tells me that the credentials are invalid. I make several tests to verify that I have not made a mistake when entering the credentials. It seems to fail in the connection protection process.
When I connect using IP to the same machine as before, the certificate appears, but if checked, the certificate is valid for the FQDN indicated above, so the certificate is OK (in date, valid and has not been revoked). If I accept the certificate, it starts the connection protection and finally connects.
If I access the same machine physically or through VMWare console, it lets me login correctly.
I have gone to check the Windows event log both in system, as application, as in RDP and I do not see any error, neither in the client from which I connect, nor from the server from which I connect.
If I connect from another machine that is not Windows (Mac) using the Microsoft RDP application, if it lets me connect, even when from Windows it fails.
It happens from several clients and on several machines to which I connect via RDP.
At the Firewall level all the rules are correct, both in the Windows Firewall and in the Network Firewall.
What is the operating system of the pc/server with the issues? I have an issue with an old Windows 2008 r2 server similar to this.
currently I am working on PWA (progressive web app) that needs fully functional offline capabilities. Currently the client is hosted on Heroku and is fully functional offline, besides one key feature. The PWA is not able to connect to the local server I am running from a separate computer. I made a self-signed cert so the localhost server computer is able to connect to it's running server via HTTPS; but I am unable to connect a different computer on the LAN to the same server. I'm fairly new to certificates and how they work, and I can't seem to figure this one out.
Just needed to make a server endpoint where I could accept the certificate. This was weird initially because the application is a SPA. So currently the user would have to differ for the initial setup.
We install liferay6.2 in windows dedicated server 2008 r2. Liferay sever is working smoothly in the server but when we are trying to access it from browser then we are unable to access it. Error: server not found. In Liferay we have one portlet for video conference and it is also working fine. We can access the server through RDP(Remote Desktop) but whenever trying to access through browser fail to find the server in web.
May be this issue can be easily handle by the network admin or may be by any Liferay developer.
Does your dedicated server have a public (routed) IP address? Also, check firewalls that might block port 8080 if you have not changed the default port. As you say Liferay is running smoothly - you just can't access it - your problem is most likely rather related to the network configuration, not to Liferay itself
I've installed Web Deploy 2.1 on a Server 2008 R2 running under VMWare.
In the IIS Manager (Management Service applet) I can see that "Enable Remote Connections" is checked and the port is set to 8172. Under "IIS Manager Permissions" I've added my Windows account (CORP\ekkis) and under the "Authentication" applet (for IIS) I have enabled "Windows Authentication".
I've also turned off the firewall.
So from the command line I test the system to work like this:
C:\Program Files\IIS\Microsoft Web Deploy V2>msdeploy -verb:dump -source:contentPath=\temp,wmsvc=192.168.0.70,username=CORP\ekkis,password=MyPass,authType=Basic -allowUntrusted=True
and get this:
Info: Using ID '9b954a0f-ff07-4e77-ba2c-d27472f5fda0' for connections to the rem
ote server.
Error Code: ERROR_USER_UNAUTHORIZED
More Information: Connected to the destination computer ("192.168.0.70") using t
he Web Management Service, but could not authorize. Make sure that you are using
the correct user name and password, that the site you are connecting to exists,
and that the credentials represent a user who has permissions to access the sit
e.
Error: Object of type 'contentPath' and path '\temp' cannot be created.
Error: The remote server returned an error: (401) Unauthorized.
Error count: 1.
I've also tried deploying with Visual Studio 2010 from the host OS with the following service urls (I haven't found proper documentation on how to form this url):
https://192.168.0.70/
https://192.168.0.70:8172/
https://192.168.0.70:8172/MsDeployAgentService/
https://192.168.0.70/MsDeployAgentService/
I've tried the non-secure versions as well but just cannot get it to work. What is the correct format for the url? and what permissions am I missing?
the errors from VS have varied depending on how I attempt it but below is a sample:
Could not complete the request to remote agent URL 'http://192.168.0.70:8172//MSDEPLOYAGENTSERVICE'.
The underlying connection was closed: An unexpected error occurred on a receive.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host
Publish failed to deploy.
there really should be a guide out there to do this (yes, I've googled myself blue in the face)!
thanks - ekkis
ok, I've figured out that the correct url is:
https://192.168.0.70:8172/MsDeploy.axd
and that having the "Windows Authentication" enabled doesn't seem to make a difference. Also, having my account in the "Managers" list doesn't seem to make a difference either.
so the back end was all working fine (I've turned off the Web Deployment Agent Service). it was just the url I had wrong.
I've been trying to solve this problem for about a week now. I posted this question on Microsoft website and only received one reply, which did not solve my issue. The following is a combination of my posts on Microsoft website.
I installed and configured TFS 2010 on Window 7 PC 64-bit. When I navigate to http://localhost:8080/tfs in my browser, I get
Service Unavailable – HTTP Error 503. The service is unavailable.
Any help to solve this problem would be greatly appreciated.
Based on previous reading, I have done much work to figure this out. Following are the steps I have gone through to solve this issues. The list is fairly long, but I want to make sure all the information that may be pertinent to solving this problem is available.
I have uninstalled and reinstalled TFS many times
The application pool "Microsoft Team Foundation Server Application Pool" is running
The application pool "Microsoft Team Foundation Server Web Access Application Pool" is running
Other website in IIS that point to the "ASP.NET v4.0" app pool seem to run fine.
If I point my other sites to "Microsoft Team Foundation Server Application Pool" they
seems to run fine
The Windows user "TFS" is in the following rolls: Administrator, IIS_IUSRS, - TFS_APPTIER_SERVICE_WPG, Users
I'm able to run SQL Server Management Studio (SSMS) as the user "TFS" and access the databases "Tfs_Configuration" and "Tfs_DefaultCollection"
I have confirm the account for "TFS" is not disabled or expired
For IIS application "Team Foundation Server", I Configured "Failed Request Tracing Rules" to log status codes 401.3-999
After IIS Reset and browser refresh, no files in the "FailedReqLogFiles" directory
No log information in IIS Logs
In Team Foundation Server Administration Console, I can change account info(Update Password, Change Account, Reapply Account).
In Team Foundation Server Administration Console, when I try to changing Group Membership or Administer Security I get the error "Team Foundation services are not available from server http://localhost:8080/tfs. Technical information (for administrator): HTTP code 503: Service Unavailable"
In Event Viewer, I do not see anything that may be of value
In Sql Server Configuration Manager, confirmed "SQL Native Client 10.0 Configuration - (32bit)", "SQL Server Network Configuration", and "SQL Native Client 10 Configuration" all have the following protocols enabled (Shared Memory, TCP/IP, and Named Pipes"
In IE confirmed that that Proxy server is not enable.
I installed Team Foundation Server 2010 Power Tools. The following are the Critical Issues returned by the tool
Accessing "AuthorizationService" Web service at "/DefaultCollection/Services/v3.0/AuthorizationService3.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
Accessing "BuildService" Web service at "/DefaultCollection/Build/v3.0/BuildService.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "CommonStructureService.ListAllProjects" at "/Services/v1.0/CommonStructureService.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable."
Accessing "GroupSecurityService" Web service at "/DefaultCollection/Services/v1.0/GroupSecurityService.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
Accessing "IdentityManagementService" Web service at "/DefaultCollection/Services/v3.0/IdentityManagementService.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "Integration Services ProcessTemplate.GetTemplateName" at http://MyServer:8080/tfs/DefaultCollection/Services/v1.0/ProcessTemplate.asmx failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
Accessing "LabService" Web service at "/DefaultCollection/Lab/v3.0/LabService.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "ProcessTemplate.TemplateHeaders" at "/Services/v1.0/ProcessTemplate.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable."
Accessing "Repository" Web service at "/DefaultCollection/VersionControl/v1.0/repository.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
Accessing "SecurityService" Web service at "/DefaultCollection/Services/v3.0/SecurityService.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "TeamProjectCollection.GetDefaultCollectionId" at http://MyServer:8080/tfs/TeamFoundation/Administration/v3.0/TeamProjectCollectionService.asmx failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "VersionControl.Administration.QueryRepositoryInformation" at http://MyServer:8080/tfs/DefaultCollection/VersionControl/v1.0/administration.asmx failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "VersionControl.Administration.QueryRepositoryInformation" at http://MyServer:8080/tfs/DefaultCollection/VersionControl/v1.0/administration.asmx failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "ConfigurationSettings.ServiceGetWorkitemTrackingVersion" at http://MyServer:8080/tfs/DefaultCollection/WorkItemTracking/v1.0/ConfigurationSettingsService.asmx failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The follow are additional issues that were not critical:
SharePoint Products is not installed or integrated with Team Foundation Server.
Team Foundation Server is not configured to use the data warehouse.
Team Foundation Server is not configured to use Report Manager.
Results for rules that require access to Team Foundation Build cannot be included in the report.
Cannot validate the configuration of Visual Studio Lab Management. Results for rules that check the health of Visual Studio Lab Management will not be included in the report.
Paged pool memory on MyServer is over the warning threshold of 180 MB. This may not be a problem if a backup is currently in progress. Current value: 490 MB.
The follow are Information Items:
Computer: MyServer. Manufacturer: System manufacturer. Model: System Product Name.
The application tier connected to Team Foundation Server at 12/2/2010 9:09:49 PM.
The connection string in config file c:\Program Files\Microsoft Team Foundation Server 2010\Application Tier\Web ervices\Web.config on MyServer is: Data Source=MyServer;Initial Catalog=Tfs_Configuration;Integrated Security=True;.
The connection string stored in the Team Foundation Server registry is: Data Source=MyServer;Initial atalog=Tfs_Configuration;Integrated Security=True.
Logical disk C: on MyServer is 500 GB in size.
No Sharepoint Site is configured for this Team Project Collection "DefaultCollection".
No Sharepoint Site is configured for this Team Project Collection "DefaultCollection".
The MyServer is running the 64-bit version of Windows.
The SQL Server (MSSQLSERVER) service on MyServer is configured to run as user NT AUTHORITY\NETWORK SERVICE.
The account Identity for the Team Foundation Server application pool on MyServer is MyServer\TFS. This is the same as the Team Foundation Server service account.
The Team Foundation Server Product Version is 10.0.30319.317
The Team Foundation Server Service Level is Tfs2010.RTM.KB2135068.P#3.
The MyServer has 1 processor(s) installed.
The MyServer has 6134 MB of memory installed.
Volume C:\ on MyServer is a mount point.
I started up a Virtual Machine with Windows 7. Installed and configured TFS. Everything seems to work fine on the Virtual Machine. With an environment working, I started to compare differences between the two.
Here are some of the differences I found between the two environments:
My primary computer is 64-bit and the Virtual Machine is 32-bit.
On my primary computer, IIS "Team Foundation Server Website" has a "aspnet_client" directory. On the virtual machine, this directory does not exist
On my primary computer, in IIS Manager for "Team Foundation Server" the section ASP.NET are the same on both my primary computer and virtual machine.
On my primary computer, IIS Manager IIS Section has these additional feature that the virtual machine does not include (ASP, Authorization Rules, CGI, IP Address and Domains, and WebDav Authorization)
On my primary computer, IIS Application Pool setting has a property call "Enabled 32-Bit Application". This was set to false and I changed it to true. Understandably this feature is not available on the virtual machine.
Thanks.
My application pool had been stopped as well and when I looked into why or how, I discovered that it was running under a domain account of one of our admins who initially installed TFS (months ago).
B/C of a corporate domain policy, he was forced to recently enter a new password for his account. Then after business hours last night, an update was applied to the IIS server on which TFS runs, and the update required a reboot. B/C the password of the identity under which the app pool runs had changed, IIS could not restart the pool, as the identity was still set to the original domain account and password.
Once I had the admin enter his new password with the app pool's identity, the pool would restart. However, b/c corporate enforces password expiration like every 90 days, I ultimately changed the identity to local system account in order to avoid this problem in the future (choosing local system may not be the best choice).
Start -> Administrative Tools -> IIS
{Server name} -> Application Pools
Right Click on Microsoft Team Foundation Server Application Pool -> Advanced Settings
Identity -> Choose Custom Account -> Click Set -> Enter the username and password of the system admin
Stop then Start Microsoft Team Foundation Server Message Queue Application Pool
Stop then Start Microsoft Team Foundation Server Application Pool
I got this error as well. In the application pool there is a TFS App Pool that was stopped. Once this was started again the 503 error stopped occuring
I never got it to work. I created a VM and installed Team Foundation Server (TFS) 2010 and everything seem to work good. To conclude, I'm not sure what was wrong, but if I install it on a fresh server everything works fine
The very first thing you must do is to ensure that the application pool is running.
I just ran into this problem. Our TFS server is not part of a domain. I noticed that the HTTP log file seemed to list IPv6 addresses at times and at other times IPv4.
I turned off IPv6 and we were able to once again connect to TFS.
Uncheck Limit connection on IIS to solve this problem.
Limiting Connections (IIS 6.0)
In my case... (my problems aren't related to how TFS is setup but accessed from a workstation)
I work for a large bank and have a sophisticated firewall/proxy - suffice it to say I have had to play with clicking various options to properly connect to our TFS AND connect to the Internet (to download Visual Studio extensions). I fix my error under the proxy settings in IE under OPTIONS | Connections | LAN Settings...
I've had some 503 errors from TFS myself, if my memory serves correctly (I can't test much as my test server is currently down) I had some issues with the versions of ASP.NET the TFS website was configured to use.
Check that ASP.NET is configured to use version 4.0 in IIS (right click the site > Properties > ASP.NET). Also make sure that no other non TFS sites are in the same application pool as your TFS site (actually a virtual directory in your TFS site) and configured separately (they don't seem to play well together!).
I just checked my team foundation services from application pool through inetmgr and found my services was not running.i started it and now i am able to connect to the server.
After installing several times I got it working with installing SQL Server 2008 R2 (Developer) instead of using SQLExpress.
I encountered the same problem today.
Resolution is start installation distrib of TFS and repair product
(in my way i re-install only tfs 2010 service pack 1).
Go to Application Tier in TFS Administration Console and change account; it may fix the problem
I very recently ran into a similar issue. One of our tools sporadically failed when attempting to contact our TFS resource. Comparing the machines in our TFS VIP, only one machine had IIS errors, namely (truncated): 503 8080 QueueFull Microsoft+Team+Foundation+Server+Application+Pool. A quick comparison of app pool settings showed that the good machine had a queue length of 1000, the bad had only 10. 1000 might be excessive, but 10 was apparently too small. I am yet to verify that changing queue length from 10 to 1000 fixed my issue. Hopefully I remember to complete my post! Hope this helps someone...
If the TFS server name is longer than 15 characters it could be an issue with the netbios name being different than the servername. In our case the AppFabric Service was crashing, and we had to use the following to fix the Cache Host name:
http://www.andrewjbillings.com/long-server-name-causing-app-fabric-service-to-crash/
This resolved the TF24668: The following team project collection is stopped errors that we were getting, along with some TF400732: The request has been canceled. and TF246066: Team Foundation Server is offline. error messages
I have TFS installed on my local machine and TFS is running under custom account.
I solved 503 error by setting the App Pool credentials again (Microsoft Team Foundation Server Application Pool and Microsoft Team Foundation Server Message Queue Application Pool)
Another, pretty special reason could be, that you set "Logon as a batch job" in AD explicitly. If you do not specify this setting it defaults to "Administrators;Backup Operators". If you overwrite it e. g. to allow a custom account to schedule a task you must make to not forget adding the default values. Else exactly this problem 503 Service unavailable and a stopped app pool appears.