Dotnetnuke 4.9.4 on a port in IIS

So I was trying to install DNn 4.9.4 on our test server on the port 8032. Idea was that I would install it and another guy from our team would work on the skins. Well, installation is supposed to be simple, but I din't know what was in store for me untill I tried!

Ok I started by creating a database and I copied the files from install zip file. Then I created the new website in ISS on port 8032. I changed connection string values in the web.config and the site installed properly. Now I was happy, this was my first DNN installation, wow that felt nice :)

Now I clicked on the "Click here to access your portal" link and duh, nothing. It initially gave me Page not available error, then I refreshed the page a couple of times and it gave me 403 error.
It was almost 9 in the night and I was feeling hungry here. Ok I checked most of the articles that was available out here and did all what the experts suggested, but to no avail.

I found that in the PortalAlias table, it inserted "localhost/install", well that was strange. I removed and made it "localhost:8032", I was so confident it would solve the problem. But unfortunately it didn't.

Hunger took control over my thoughts to solve this issue and I called it a night. But then I thought of a similar issue a colleague had some time back. It was related to some setting called "UsePortNumber". It was commented in the config file. I uncommented and refreshed the page, it works like a charm.

Gosh, how easy it was. Just a small change. Just wanted to share my experience here!

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