PDSWSS
asked on
Why do I get the attached duplicate error when I attempt to create a Sharepoint Site?
We are running Sharepoint Foundation 2010 on Windows Server 2008 R2with a MS SQL 2008 R2 Backend. I deleted our Sharepoint site and then attempted to recreate it in Sharepoint Admin. No matter what URL or port # I use, I get the attached duplicate error. Any idea how to fix this? Thanks
Picture-1.jpg
Picture-1.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Discovered that the issue was that the site is configured with asp.net 2.0 and the AppPool is using 4.0. Got to change AppPool to 2.0. Then it works. Thanks
is all work fine with you? is my solution was helpful for you?
ASKER
No. Did not use your solution to solve the issue. Found a warning that commented out that code would cause other issues. But thanks for sending it.
lol , it was talking about AppPool also .. anyway am happy to hear that your problem solved , this just all i want , i tried to help you to get point , just to help you solve your problem ..that's it mate..
good luck
good luck
just to be sure , back to the article .. this paragraph :
Step 1 (IIS 7 or IIS 7.5 only)
This step is necessary only on operating systems that run IIS 7 or IIS 7.5, which includes Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.
Move the configSections definition in the Web.config file of the parent application (the application that runs ASP.NET 2.0 or ASP.NET 3.5) into the root Web.config file for the.NET Framework 2.0. The IIS 7 and IIS 7.5 native configuration system scans the configSections element when it merges the hierarchy of configuration files. Moving the configSections definition from the parent Web application’s Web.config file to the root Web.config file effectively hides the element from the configuration merge process that occurs for the child ASP.NET 4 application.
On a 32-bit operating system or for 32-bit application pools, the root Web.config file for ASP.NET 2.0 and ASP.NET 3.5 is normally located in the following folder:
Step 1 (IIS 7 or IIS 7.5 only)
This step is necessary only on operating systems that run IIS 7 or IIS 7.5, which includes Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.
Move the configSections definition in the Web.config file of the parent application (the application that runs ASP.NET 2.0 or ASP.NET 3.5) into the root Web.config file for the.NET Framework 2.0. The IIS 7 and IIS 7.5 native configuration system scans the configSections element when it merges the hierarchy of configuration files. Moving the configSections definition from the parent Web application’s Web.config file to the root Web.config file effectively hides the element from the configuration merge process that occurs for the child ASP.NET 4 application.
On a 32-bit operating system or for 32-bit application pools, the root Web.config file for ASP.NET 2.0 and ASP.NET 3.5 is normally located in the following folder:
ASKER
Thanks
lool thank you mate , i swear i was kidding , just i feel happy when anyone get his problem solved ,really i am here just to help people , this most work i love is helping other ... have good day mate
ASKER
I saw your point. Although I did not use your paper to solve the issue, the concept behind the problem was described in the paper. Therefore seemed fair to give you the points. Thanks
ASKER
In the webconfig file - I would delete or comment out all instances where Section Name or Group Name = system.web.extensions?
Please see attached. thanks
Picture-4.png