If "objectQualifier" is non-blank in "web.config" then some of the upgrade SQL scripts appear to fail/not be run (can check this by looking to see if "CanDeleteSkin" was created in DB). If objectQualifier is blank, the upgrade SQL scripts seem to run fine.

I didn't have logs enabled, unfortunately (I believe they are disabled until enabling under "Site Settings", or am I looking in the wrong place: Portals/_default/Logs ?) You should be able to easily reproduce by installing a fresh 4.4.1 installation and changing "web.config" so that "DotNetNuke > SqlDataProvider > objectQualifier" is non-blank.

I appreciate that DNN is a volunteer project and my strongest thanks goes to everyone involved for their efforts. It's just been particularly frustrating with the 4.4.1 release, because we've hit 2 major installation issues (missing DLLs from bin, objectQualifier bug described here) which seem to indicate lack of basic testing.

That provides a clue - this log file is missing, suggesting a logic flaw is causing the script not to be run, rather than the script is failing. The only log files I see in the above folder for a freshly installed/run 4.4.1 installation are: "DotNetNuke.Data.log", "DotNetNuke.Schema.log", "DotNetNuke.SetUp.log", all of which are empty.

An important update, BTW:  I installed a fresh 4.4.1 installation with no "objectQualifier" specified in web.config and got exactly the same problem:  the "04.04.01.SqlDataProvider" script isn't running, so "DeleteSkin" SP doesn't get created (can fix fully by running script manually).

From accounts here, I'm not the only one experiencing this problem. For reference though, I'm running IIS on Win2K, SQL Server Express 2005 on a named instance (as is the default), using the following connection string format:

    <add name="SiteSqlServer" connectionString="Server=MYMACHINE\SQLEXPRESS;Database=MYDBNAME;uid=BLAH;pwd=BLAH;" providerName="System.Data.SqlClient" />

Note that I'm seeing exactly the same problem installing on our remote host, who run Win 2003 with SQL Server 2005 (full). Other "web.config" changes, in case relevant:  debug enabled, FCKeditor installed.

Here's a copy of the installation notes displayed during the installation (note that the 4.4.1 SQL script isn't listed):

Installation Status Report

00:00:00.330 - Installing Version: 4.4.1
00:00:00.330 - Installing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:00.761 - Installing Script: DotNetNuke.Schema.SqlDataProvider Success
00:00:12.447 - Installing Script: DotNetNuke.Data.SqlDataProvider Success
00:00:17.654 - Installing MemberRole Provider:
00:00:17.754 -   Installing Script: InstallCommon.sql
00:00:20.738 -   Installing Script: InstallMembership.sql
00:00:23.973 -   Installing Script: InstallProfile.sql
00:00:24.454 -   Installing Script: InstallRoles.sql
00:00:26.006 - Performing General Upgrades
00:00:26.697 - Loading Host Settings:
00:00:26.897 - Configuring SuperUser:
00:00:27.949 - Installing Modules:
00:00:27.989 -   Installing Module File Documents_03.01.06_Install:  Success
00:00:31.103 -   Installing Module File FAQs_03.01.00_Install:  Success
00:00:33.857 -   Installing Module File HTML_03.03.00_Install:  Success
00:00:36.000 -   Installing Module File Links_03.03.00_Install:  Success
00:00:37.782 -   Installing Module File NewsFeeds_03.01.01_Install:  Success
00:00:38.543 -   Installing Module File Survey_04.00.20_Install:  Success
00:00:46.064 - Executing Additional Scripts:
00:00:46.074 -   Creating Portal: Haybridge School CMS Demo
00:01:05.030 -   Successfully Installed Portal 0:
00:01:05.030 - Installing Optional Resources:

I hope this helps to identify the problem. Let me know if need further information.

BJ