Chris Hammond wrote:
Do you still have a system.web.extensions.dll in the BIN folder of your website? If you have .net 3.5sp1 you won't need that file in the BIN folder.
Yes, we still have that file in the BIN folder (version 1.0.6)
But, we are still running on framework 2.0 (due to still using SQL 2000, and DNN 5.1.1)
Our portal which runs off the virtual directory now merely forwards to the DNN site on main root (of IIS)
(also tried putting the virtual directory site on the main root of IIS, but same errors and results).
When deleting the 'system.web.extensions.dll' file - A configuration error occurs.
When commenting out the assembly line of code (in web config) - it still redirects to the main portal.
------
Further Info:
I believe its recommended to remove old references to old aliases in the database when setting up on a new development server.
– so, on our new database, we did this:
- Removed portal alias to reference to the live website (in Portals and PortalAlias tables)
- Also had to remove all references to live portal id on new database ‘portal id 7’ (in modules table)
But, then it gives this error:
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
- Could it be giving this error because its trying to connect to the old portal ID - 'portal 7' instead of the portal we want 'portal 0' (perhaps this is why its redirecting – because it keeps looking for portal 7) ?
- is there any way we can check to see which portal id it is trying to connect to?