Hy,

I'm tryng to install DNN release 3.2.2, but I have received an error much strange one.

This is the report of my installation:
---------------------------------------------------------------------------------------

Installing DotNetNuke

Version: 03.02.02

Installation Status Report

00:00:00.120 - Installing Version: 3.1.0
00:00:00.130 - Installing Script: DotNetNuke.SetUp.SqlDataProvider
00:00:00.370 - Installing Script: DotNetNuke.Schema.SqlDataProvider
00:00:03.474 - Installing Script: DotNetNuke.Data.SqlDataProvider
00:00:08.692 - Installing MemberRole Provider:
00:00:08.692 - Executing InstallCommon.sql
00:00:09.904 - Executing InstallMembership.sql
00:00:10.735 - Executing InstallProfile.sql
00:00:11.005 - Executing InstallRoles.sql
00:00:11.676 - Upgrading to Version: 3.1.1
00:00:12.838 - Upgrading to Version: 3.2.0
00:00:12.998 - Upgrading to Version: 3.2.1
00:00:13.098 - Upgrading to Version: 3.2.2
00:00:13.198 - Performing General Upgrades

Server Error in '/dotnetnuke' Application.
The stored procedure 'dbo.DNN_GetTabByName' doesn't exist.

ecc. with the error debug.
-------------------------------------------------------------------------------------------

That it wants to say ?
This is possible that lacks a Stored Procedures ?
I Am blocked why I do not succeed to find some explanation.

Thanks to who want to help me !

I ran into the same problem and fixed it by reading another post on this site. Changing the collation of my SQL Server database when creating to a case-insensitive collation (like SQL_Latin1_General_CP1_CI_AS) is what fixed it for me. The GetTabByName stored procedure references the FileID column in the Tabs table in a LEFT JOIN, but the schema of the Tabs table shows the name of the column to be FileId (the "d" is lower case in the table, but upper case in the stored proc). Below is a list of steps I took to resolve the issue:

1. Drop the existing database
2. Recreate your database and select SQL_Latin1_General_CP1_CI_AS as your Collation Name (General tab)
3. Apply logins according to DNN Install instructions
4. Open your local site in a browser (your upgrade should complete successfully)

HTH.
Mike 

You could reinstall. I tried installing 3.2.2 right out of the gate when I got the error message, w/ my default collation set to Latin1_General_BIN (case sensitive). I then deleted and reinstalled 3.2.2 using the same collation (dropped and recreated the database), deleted and installed 3.2.1 w/ the same collation (dropped and recreated the database), then discovered the fix and changed my collation to be case-insensitive (dropped and recreated the database) and succeeded.