Unfortunately I don't have a lot of technical information to give you but I will give as thorough a description as I can.
I have done a fresh install of Windows Server 2003 Enterprise (SP1). Performed all the updates including SP2 and installed McAfee Enterprise 8.7. Once I've completed doing this I open up the Windows Components installation and check "Application Server" which should install the base IIS installation.
The install runs fine and I reboot just for good measure. When I go into services I see IIS Admin started. Pulling up the IIS Manager reveals that the DefaultAppPool and the Default Web Site are both stopped. Attempting to start the Default Web Site results in no failure message and no entries in the Event Log. This doesn't surprise me terribly as it depends on the DefaultAppPool. When I try to start the DefaultAppPool after a few seconds I get an error "The service did not respond to the start or control request in a timely fashion." and there is still no messages written to the event log.
I've tried this exact installation procedure twice now with identical results. Any suggestions would be greatly appreciated.
I found a work around if not a complete solution. I installed and configured IIS before updating or installing McAfee. IIS worked fine. Since I got it working I didn't want to go back and do a fresh installation but now that I think about it I might have just needed to run updates one more time after installing IIS. The order I installed it did allow me to get it to working so good luck to anyone else that has this issue. I hope this helps.
Related
Okay, here goes: Our developers are running VS 2012 on Win 7 boxes. I am running TFS 11 on my Win Server 2008 R2 box with IIS 7.5. It runs fine. My gating unit tests fail however. While I am not completely certain what the issue is, I seem to be unable to get the default Web Site or our application that I have installed under it to run. The default web site won't even return a test.htm file choosing instead to return a 503. To date I have tried...
Setting up WCF with access to the test cert installed on the box
Changing the app pool and giving it access to the dir in question
Burning a small offering to the gods of oblique IIS issues
Various other things I can't recall at the moment
I would take Sean Walsh's advice at the end of this post: http://forums.iis.net/t/1183179.aspx/2/10 but I need SQL reporting services for my TFS to work properly.
Thoughts? Thanks in advance.
Sean Walsh had it nailed. This turned out to be due to the fact that SQL server reporting services were using the port at the behest of TFS. I was able to step around this problem by setting up a dedicated build box on a VM.
I have done some research, based on the problem that my single server gives me when I try to open a document library in windows explorer from the ribbon menu item "Open in Windows Explorer".
The same problem occurs when I try to map sharepoint to a folder in windows explorer too.
The error is:
Your client does not support opening this list with Windows Explorer
From the net, suggestions are:
(Since I'm trying this operation from server itself) enable Desktop Experience
Install the KB907306 update.
Enable IIS webDav service (Some say, it's just for additional functions from the MS Whitepaper)
(Edit) Started webClient service
I've already done them. Nothing changed. Proper machine restart and iis too have done.
Need some serious advice.
Thanks in advance.
Not sure if we are having exactly the same problem BUT I have had similar problem while accessing SP via Windows Explorer in Windows Server 2k8.
What I done to fix it is following:
Install new server feature called Desktop Experience (it comes with WebDAV redirector, which allows you to connect to WebDAV) - Note: Server will need to be restarted.
In Services start WebClient service (go to properties and make sure it starts automatically)
You will now be able to access your sharepoint via entering network path such as \sharepointhost\application\myawesomeapplication\ etc.
Hope that helps.
If you are trying to do this from the server, test it from a server which is not on the SharePoint farm (or better yet, a client machine). Ensure all of your testing is done from machines which are not on the farm.
Do NOT enable the IIS WebDAV service, as SharePoint provides its own WebDAV service and the IIS one overrides it in the pipeline. Enabling this service is a sure path to breaking WebDAV.
If you have SSL enabled, you may be in for a rough time getting it to work. Start by understanding how to use the 'net use' command, and the #SSL suffix.
make sure your webdav is installed as feature
make the following registry fix (http://support.microsoft.com/kb/841215) :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
Add a new DWORD "BasicAuthLevel" and change this to "2"
Restart your machine (and make sure it is enabled in IIS)
Make sure that WebClient windows service is running in the server. This shall appear in client operating systems like Windows 7, windows 8 however, on the server operating systems like Windows Server 2008, it shall be installed by enabling the server feature "Desktop experience" using Server Manager
This issue nearly killed me. I found that I was using a 64 bit version of my browser and that is'nt supported. I changed over to the 32 bit and it works.
I am getting the following error when I run web deploy:
>C:\Program Files\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets (3588): Web deployment task failed.
((3/25/2011 4:41:36 PM) An error occurred when the request was processed on the remote computer.)
(3/25/2011 4:41:36 PM) An error occurred when the request was processed on the remote computer. The entry type 'Unknown' was not expected at this time. The serialization stream may be corrupted.
I have successfully done this on other IIS6 machines with no issues so I don't understand what is going on. The Remote Deployment Service is running and just to see if it mattered I started the service under an administrative group. That did not help.
Any help would be great.
I found that the 2008 server with IIS 7 did not have all of the components installed. Even though Web Deployment 2.0 seemed to have been installed by the Web Platform Installer, there were components that were incomplete due to communication issues with the MS servers. In order to resolve this, I had to download the installation files on a separate machine, copy them to the server and then reinstall everything. Very vague error for such an odd issue.
I'm trying to uninstall SQL Server from my machine so that I can install SQL Server 2005 Developer Edition.
I'm getting the following error message.
the setup failed to read IIsMimeMap
table. The error code is -2147023550
Thank in advance.
The solution is to stop IIS
c:> NET STOP "World Wide Web Publishing Service"
Stopping IIS/IIS Admin didn't help me, nor did searching for the error code. However, Microsoft has a solution. From the KB article:
Cause
This issue occurs because the uninstall program cannot run correctly
if the virtual directories for SQL Server 2005 Reporting Services are
not present.
Workaround
To work around this issue, re-create the virtual directories for SQL
Server 2005 Reporting Services by using the Reporting Services
Configuration tool. After you re-create the virtual directories, you
can uninstall or repair the installation of SQL Server 2005 Reporting
Services successfully.
I had a bad Website in IIS. I removed it, used the tool to recreate both of the required Virtual Directories, and then uninstalled successfully.
We installed SP1 on our Team Foundation Server 2008 server. Everything seems fine after the install, except there is a red X on the Reports folder in the Team Explorer in Visual Studio. If we attempt to access the Reporting Services web site, we get a message that says that the "report server is unavailable". There were no errors during the installation.
The Reporting Services service started up fine and left no errors in the event log. We looked at the Reporting Services Configuration Tool and everything shows as OK. We tried restarting the RS service and rebooting the machine. Again, no errors but still no report availability.
The SQL Server instance where our data lives is up and running fine and we can query the OLAP cube and the relational side with no problem. All of our developer machines are already at VSTS 2008 SP1. Visual Studio is not installed on the server.
We looked at the logs files in the RS folder and the only errors that show are the ones that we get when we try to access the web site from IE, but that don't seem to contain any more info about the root cause.
Any help would be greatly appreciated. I'll post any updates on other things we try here.
UPDATE: There is a login error showing up the ReportServer(timestamp).log file. The login on the reporting services service is not the login that is showing up in this error, so I'm not yet sure what process is actually trying to make the connection to the db.
We got this resolved. It appears that the TFS 2008 SP1 install process decided to change the identity setting of application pool for the Reporting Services web site. To resolve we needed to:
Open Internet Information Server Manager
Go into Application Pools
Right click on the Reporting Services application pool
Click on the Identity tab
Change the account from NetworkService to our TFS domain account
Edit the rsreportserver.config located in "\Program Files\Microsoft SQL Server\MSSQL.1\Reporting
Change the "NT Authority\NetworkService" to "OurDomain\TFSDomainAccount"
Restart IIS
Hope this saves someone else some time.
Check the IIS application pools. My feeling is that reporting services doesn't play nice with other web applications (usually I've fixed this in the past by setting a seperate pool for the other applications).