Jim Lawrence
accessd at shaw.ca
Tue Mar 11 15:42:19 CDT 2008
To all those who have been wondering what the problem was and the solution to that problem is, 4 hours on the phone to Microsoft finally created a solution. There have only been 14 cases similar to this, so I feel honoured. The solution was to go into the registries to the HKEY_CLASSES_ROOT (HKCR) and set the LOCAL SYSTEM account to have FULL control and USERS group (or authenticated users) to have READ permissions. Somehow some program... an MS update most likely changed the registry permissions. ASP can still not connect to the SQL servers but another specialist will be calling soon in the on going saga. Jim -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Saturday, March 01, 2008 4:40 PM To: 'Discussion concerning Visual Basic and related programming issues.' Subject: [dba-VB] OT ASP nightmare I run a test bed IIS 6 server for a number of client systems using everything from ColdFusion to PHP and from standard HTML to ASP.Net. A number of sites run straight ASP. (The Database Advisors web site http://www.databaseadvisors.com is one example.) Early last week, seeing the Server is 2003, an upgrade fro fso.objects was recommended via Microsoft. The upload and install was performed and everything ran fine....NOT! >From then on all ASP applications would fail with the following error: Active Server Pages error 'ASP 0201' Invalid Default Script Language The default script language specified for this application is invalid. There is nothing wrong with the IIS configuration, the security... to that end, the IIS server has been removed completely and replaced, twice. ASP is also completely replaced within this process. There is obviously nothing changed with IIS or ASP but the Server 2003 has had some subtle changes made to either the directory/file permissions or to some entry in the registry. A week later...no joy. Has anyone had similar problems and found a solution. (Sorry no current system backups... so the next step is a dreaded system re-install.) MTIA Jim PS I have now heard of a number of other individuals, through the web, who have had similar situations but in all case the only solution has been a call to MS or a system install... serious stuff. _______________________________________________ dba-VB mailing list dba-VB at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-vb http://www.databaseadvisors.com