Gateway time out Error

I was creating a new web application on a WSS 3.0 server for hosting BPM application webparts. This new site had to be accessible from Internet. While creating the new web application I provided a host header which was already set up in the DNS server and it had an IP address too. Next I created a site collection.

After creating this web application I provided this IP address on the properties tab in ISS for this website. It was created on port 80. I had also provided the IP address in the "Advanced TCP/IP Settings" of this server. Now when I tried to access this new web application, I got the error "Gateway time out".

I had no clue as to what was causing this error. Then a colleague pointed me to a Microsoft fix for this issue: http://support.microsoft.com/kb/896861

After applying this I had to restart the server and now there was another error. It said "File not found". I edited the web.config of this web application so that I get a detailed error. I changed callstack to "true" and customerror to "Off". The issue was related to some dlls for this BPM webparts. I checked the solution management section in Central Administration - Operations and found that wsp for this BPM application was deployed locally for another web app and not globally. Then I deployed this wsp for my new web application and error vanished. Things are sorted out now.

For more information on the Loopback issue Check this blog

Comments

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker: ...

Difference between the architectures of SSPs and SharePoint Service Application

SharePoint 2010 has some new features and components, which help to overcome difficulties such as redundancy and service-sharing that we faced while using SharePoint 2007. Services in MOSS 2007 were implemented with the help of Shared Service Providers or SSPs. But we cannot use the services of one SSP for another SSP. So each SSP has to have its own set of services and applications, which increases redundant data in the farm. For example, different managers in the same organization use a SharePoint site to maintain official data associated with an SSP. This SSP is associated with different services, such as Search service, BDC service, and a user profile service. A project manager in this organization requests an exclusive user profile service to maintain project data security. To provide this, we first need to create a separate SSP for the project manager and then a separate service called user profile service - project name. Next, we need to associate the SSP with ...

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.

My IT Experiences

Search This Blog