 |
|
|
Joined: 11/21/2005
Posts: 201
|
|
|
I'm using the DotNetNuke 4.3.3 "install" package, and I don't have Visual Studio, or the code for that matter, nor would I know what to do with either if I had them. But thanks for the suggestion, if only I knew/had more.
The portal on which I'm getting the error is a "demo" for a potential customer, who I would rather not see the "! Critical Error" message (giving the impression the system is seriously flawed, which I know it is not). Another thought: can we trap/supress all error messages, and if so - how? That would work for the time being.
If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
|
| |
|
|
 | |
|
|
 |
Joined: 1/30/2006
Posts: 5038
|
|
|
The only other thing I can think of is to change the colours in the cascading style sheet for the forum's theme. Might not work. The other thing to do would be to use SQL server 2000 or MSDE 2000.
In reality I think we'll just have to wait for a fix here (suggest you just lace the customer with booze).
Cheers
Alex
|
| |
|
|
| |
|
|
Joined: 11/21/2005
Posts: 201
|
|
|
In this case, the potential client is an organization, with multiple board members testing/reviewing the portal (especially the Forum Module - yikes). And this is the week they'll be hitting the Forum first time. If it were just one client, one person - sure I could explain what's up - or booze 'em up. :) But to a team of clients, I think I'll post a message above the Forum Module saying we're aware of the "My Posts" problem, yada-yada "and we are working to resolve it". Not looking for a specific date, but - average turnaround time for a fix of type?
Since (at least with the Install package) trapping the click on My Posts to do nothing, or squelching the !Critical Error message doesn't seem easily done, I guess there's one more thing I might do: quickly move to DotNetNuke 4.0.3 - ASAP. When this morning I built a DNN 4.0.3 installation, then installed Forum Module 3.20.06 into it, "My Posts" works beautifully. Maybe the problem isn't exactly rooted in SQL Server 2005 (express)? I don't know enough about these things to suggest anything, but that's my best effort for helping to research/test for the sake of resolving this issue.
If ONLY there were a quick way to move/migrate an already configured DNN 4.3.3 portal back-down to 4.0.3 rev. Timmy's DotNetNuke Add-On Wish List: "Miracle Migrator" Module v4 with "Back to the Future" feature for making reverse migrations. Buy Now! 
If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
|
| |
|
|
| |
|
|
 |
Joined: 10/30/2004
Posts: 293
|
|
|
Thanks Tikkune for bringing me on this post looks like i'm not the only one having the issue. The site am running is 4.3.3 all the rest of the site works sweet and the improvements are marvelous. The site am having hosted on webhost4life and presume is a win2005 server as has NetworkService running not ASPNET on filepermissions. The DB server is SQL2005 also so looking again in line with this posts findings.
Entire error am getting is .....
|
23/07/2006 19:14:13 General Exception AssemblyVersion: 04.03.03; PortalID: 0; PortalNa ... |
AssemblyVersion: 04.03.03
PortalID: 0
PortalName: club
UserID: 22
UserName: Machinekiller
ActiveTabID: 61
ActiveTabName: FORUMS
RawURL: /FORUMS/tabid/61/authors/22/scope/threadsearch/pagesize/20/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.club.co.uk/FORUMS/tabid/61/Default.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 88debb9f-767b-422f-a3e7-2b457f7c314b
InnerException: Unhandled Error:
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Data.SqlClient.SqlConnection.OnError
StackTrace:
Message: System.Exception: Unhandled Error: ---> DotNetNuke.Services.Exceptions.PageLoadException: ORDER BY items must appear in the select list if SELECT DISTINCT is specified. 0 ---> System.Data.SqlClient.SqlException: ORDER BY items must appear in the select list if SELECT DISTINCT is specified. 0 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.SqlDataReader.SetMetaData(_SqlMetaDataSet metaData, Boolean moreInfo) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Modules.Forum.SqlDataProvider.SearchGetResults(String Filter, Int32 PageIndex, Int32 PageSize, Int32 UserID, Int32 ModuleID, DateTime FromDate, DateTime ToDate) at DotNetNuke.Modules.Forum.SearchController.SearchGetResults(String Filter, Int32 PageIndex, Int32 PageSize, Int32 UserID, Int32 ModuleID, DateTime FromDate, DateTime ToDate) at DotNetNuke.Modules.Forum.ThreadSearch.OnPreRender() at DotNetNuke.Modules.Forum.ForumBaseControl.OnPreRender(EventArgs e) at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace --- at DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) at DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) at System.Web.UI.TemplateControl.OnError(EventArgs e) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.default_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---
Source: | |
Hoping to follow this post and the dnn site for a fix soon as i am in the same boat as other without VS Studio and also lack of asp.net skills :/
MK
|
| |
|
|
| |
|
|
|
Joined: 1/30/2006
Posts: 5038
|
|
|
I've had the same issue both on 4.0.3 and 4.3.3, two seperate installations, two seperate servers, both running SQL Server 2005 standard. On each instance I upgraded from 4.0.3 to 4.3.3. No change either way.
All the people so far who have posted with the issue are running SQL Server 2005 (whatever version).
I'm running the latest SQL Service packs. Don't know if that's anything to do with this either.
Cheers
Alex
|
| |
|
|
| |