Yup I'm getting the same problem when I actually click on "Enroll for this event":

Error: Event Detail is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The stored procedure 'dbo.EventsSignupsSave' doesn't exist. ---> System.InvalidOperationException: The stored procedure 'dbo.EventsSignupsSave' doesn't exist. at System.Data.SqlClient.SqlCommand.DeriveParameters() at System.Data.SqlClient.SqlCommandBuilder.DeriveParameters(SqlCommand command) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Modules.Events.Data.SqlDataProvider.EventsSignupsSave(Int32 EventID, Int32 SignupID, Int32 ModuleID, Int32 UserID, Boolean Approved, String PayPalStatus, String PayPalReason, String PayPalTransID, String PayPalPayerID, String PayPalPayerStatus, String PayPalRecieverEmail, String PayPalUserEmail, String PayPalPayerEmail, String PayPalFirstName, String PayPalLastName, String PayPalAddress, String PayPalCity, String PayPalState, String PayPalZip, String PayPalCountry, String PayPalCurrency, DateTime PayPalPaymentDate, Double PayPalAmount, Double PayPalFee, DateTime EventTimeBegin, Int32 TimeZoneOffset) at DotNetNuke.Modules.Events.EventSignupsController.EventsSignupsSave(EventSignupsInfo objEventSignup) at DotNetNuke.Modules.Events.EventDetails.cmdSignup_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

but as you stated you forgot to include a stored proc in the package..so I'm definitely looking forward to the next update.  Thanks so much!!!

Testing of the DNN_Events_03.03.02_Beta1 resulted in the following:

1) Error during installation:

StartJob Begin Sql execution
Info Executing 03.03.02.SqlDataProvider
StartJob Start Sql execution: 03.03.02.SqlDataProvider file
Failure SQL Execution resulted in following Exceptions: System.Data.SqlClient.SqlException: Column names in each table must be unique. Column name 'EventTimeBegin' in table 'dbo.DNN_EventsSignups' is specified more than once. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) /* Database Tables */ ALTER TABLE dbo.DNN_EventsSignups ADD EventTimeBegin DateTime NULL System.Data.SqlClient.SqlException: Column names in each table must be unique. Column name 'TimezoneOffset' in table 'dbo.DNN_EventsSignups' is specified more than once. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) ALTER TABLE dbo.DNN_EventsSignups ADD TimezoneOffset int NULL 
EndJob End Sql execution: 03.03.02.SqlDataProvider file

2) I Appreciate the change to show the details view along with other modules using the page rather than admin skin. However, I would prefer to see the details displayed below the calendar (month) view rather than alone.  If displaying the details view alone, I would suggest adding a link to return from the details view to the calendar view as some users may not think to use their back button and since there will be no chance to select the calendar view from a menue in the module title bar if the calendar view has been set as the ONLY view in Module Settings.

3) I noticed this in the first two beta's but forgot to mention it: The .zip contains two image files with the same name - "gradient_LtBlue.jpg" which causes a file already exists error message during extraction. Surprisingly, there is no problem with this during install as the image file is simply extracted twice.

Otherwise, it looks like you're close to being ready for the release process!

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

This is my take on the issues you reported.

1) My guess this was not a clean install...This is a Beta Program.  My recommendation is not to install over top of an existing Beta.  This SQL Error will not occur if you install over an earlier Events Module or on a Clean DNN Install.  It's very difficut to maintain a install path for Beta over Beta over Beta....remember what we are testing.  Others will not install over the previous betas...they will be installing over a previous Events module or on a clean DNN install.  Please re-test in this mode and let me know if there are errors on the install.

2) I eliminated the Day List displaying under the Month View because others did not want.  I intend on creating a more detailed "Day View", similar to the "Week View", in the next few releases.  Eventually, the Views will be tied together, using a Tab Control (at the top of the page)...Currently, they display using the DNN Content Action below the View...All Views do not require a "Return" button by convention...I would consider addiing the return only to the Detailed Event View...convince me some more...anybody else have a take on this?

3) Thanks...I will eliminate the duplicate on the intall.