By clicking cancel on the dialog box a runtime error screen pops up but then refreshing the browser presents the correct window whether it be default.aspx if just entering the site or the module definition page if I had just added a module.
Obviously the dialog box is generated by windows but it is being generated because DNN is doing something wrong, I must reiterate that version 4.0.3 worked and does work perfectly on exactly the same host, so there must be some difference in the way 4.3.3 is going about its business that is upsetting windows.
This is the error generated:
Server Error in '/' Application.
Access to the path 'C:\Domains\csifanclub.org.uk\wwwroot\Portals\_default\EventQueue\Application_Start--0c5d813b-73cd-4880-a314-66993f9fe555.config' is denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.UnauthorizedAccessException: Access to the path 'C:\Domains\csifanclub.org.uk\wwwroot\Portals\_default\EventQueue\Application_Start--0c5d813b-73cd-4880-a314-66993f9fe555.config' is denied.
ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.
To grant ASP.NET access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.
The thread detailed below gives some indication of why the error is being generated.
http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/47749/scope/posts/Default.aspx
And I have found this blog entry on the same subject:
http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/482/Default.aspx
This talks about touching the web.config file so the application is restarted. From what I can gather not being a techie is that the correct user with the correct permissions is not being used when the application starts. But when the browser has refreshed the application has completed loading and the correct user with the correct permissions is now in place and everything works fine.
I think I am on the right track but am at a loss as to what to do about it.......