BobF
Posts:9
 |
| 12/01/2009 06:31 |
|
We are getting the following error message
DotNetNuke.Services.Exceptions.ModuleLoadException:
String was not recognized as a valid DateTime. ---> System.FormatException:
String was not recognized as a valid DateTime. at
System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles
styles) at System.DateTime.Parse(String s, IFormatProvider provider,
DateTimeStyles styles) at BeckerSolutions.Modules.RS2005.ViewRS2005.31AA0() at
BeckerSolutions.Modules.RS2005.ViewRS2005.3AAA0(Object 0AAAA, EventArgs 1AAAA)
--- End of inner exception stack trace ---
Any ideas what the issue is? Would this cause any issues connecting to the SSRS web service?
SQL Reporting Services - v4.2.0
DotNetNuke Community Edition - 05.01.04 (3)
.NET Framework: - 3.5
|
|
|
|
|
host
Posts:502
 |
| 12/01/2009 08:25 |
|
| Bob, this is an interesting issue that has happened to a few people but we cannot reproduce it in our environment. We believe we have isolated the issue and are working today to fix it. We are unable to replicate this issue in our environment so testing is a problem. If you are interested in assisting us with a test build that we can give you to see if the problem is solved please send an email to service@modulemasters.com and we will email it to you when it is ready along with a follow up phone call to test it out. |
|
|
|
|
host
Posts:502
 |
| 12/01/2009 10:32 |
|
| Bob, please try downloading the module again and installing and let us know if you still have this issue. We published an updated version taking a stab at addressing this, but since we can't replicate it in our environment we aren't 100% certain we have corrected the issue you are seeing. |
|
|
|
|
BobF
Posts:9
 |
| 12/01/2009 11:25 |
|
Thanks for the help, hopefully l will try that tomorrow. I will let you know the outcome.
|
|
|
|
|
host
Posts:502
 |
| 12/03/2009 08:39 |
|
| Bob, did you get a chance to test this out? |
|
|
|
|
BobF
Posts:9
 |
| 12/03/2009 08:57 |
|
Hi did send a reply via my work email address (yes a bit confusing)
I have de-installed the module that was in the installed, and then downloaded a copy of the lastest Demo version, which l have installed.
When l added the module to the page the following error message comes up
Error: Reporting Services is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The DateTime represented by the string is not supported in calendar System.Globalization.GregorianCalendar. ---> System.FormatException: The DateTime represented by the string is not supported in calendar System.Globalization.GregorianCalendar. at System.DateTimeParse.ParseExact(String s, String format, DateTimeFormatInfo dtfi, DateTimeStyles style) at BeckerSolutions.Modules.RS2005.ViewRS2005.ᣢ() at BeckerSolutions.Modules.RS2005.ViewRS2005.ᣖ(Object ᙂ, EventArgs ᙄ) --- End of inner exception stack trace ---
If you want to send me a test version l am will to install it and see what happens
|
|
|
|
|
host
Posts:502
 |
| 12/03/2009 09:04 |
|
| Bob, odd, we can't find your other work email and I see this address in this profile keeps bouncing. Is there a number we can call you at? |
|
|
|
|
BobF
Posts:9
 |
| 12/03/2009 09:10 |
|
Hi l've updated my profile with tel number. The email address works fine, l get the updates from the forum OK.
|
|
|
|
|
host
Posts:502
 |
| 12/03/2009 18:56 |
|
| We have now isolated the error, will let you know when it is corrected. |
|
|
|
|
host
Posts:502
 |
| 12/03/2009 21:44 |
|
| Bob, we figured it out, in shotgunning an approach to fix the issue you were seeing, we actually ended up introducing another bug that was similar in nature. We have updated the module, however, since you already installed the build we had the issue with, there is a small script you'll need to run after you uninstall the module. I will email this to you. |
|
|
|
|
BobF
Posts:9
 |
| 12/04/2009 10:36 |
|
Hi thanks for you all your help, challenge solved, able run reports :-)
|
|
|
|
|
host
Posts:502
 |
| 12/04/2009 13:02 |
|
| Fantastic! |
|
|
|
|
dpijl10
Posts:11
 |
| 01/04/2010 05:46 |
|
Although an old thread, we've encountered this today for the first time. We upgraded from version 1.2 to 4.2 -> worked fine in demo mode. I tried activating with our default language (nl-NL), which succeeded, only to find the module stop working with the above message.
My guess is that the module writes a localized datetime for registration, but forgets to read it localized back. How can we fix this?
|
|
|
|
|
host
Posts:502
 |
| 01/04/2010 08:32 |
|
| dpijl10, actually there was nothing related to the licensing in 1.2 version, so if you are seeing this as part of this upgrade, that is puzzling, can you confirm you upgraded from 1.2 and not 4.1? The module does write a date / time, the bug we had before was our localization format we tried to force was not always working on some machines, so we bypassed this now and forced the format we want so this error should not exist. If you upgraded from 4.1, we will need to send you a script to correct this one. |
|
|
|
|
Wolfen
Posts:2
 |
| 01/25/2010 08:50 |
|
We have the same problem for tr-TR. so casn we get the script to fix for demo test please. Message: DotNetNuke.Services.Exceptions.ModuleLoadException: String was not recognized as a valid DateTime. ---> System.FormatException: String was not recognized as a valid DateTime. at System.DateTimeParse.ParseExact(String s, String format, DateTimeFormatInfo dtfi, DateTimeStyles style) at BeckerSolutions.Modules.RS2005.ViewRS2005.20AAA() at BeckerSolutions.Modules.RS2005.ViewRS2005.ᙃ(Object ᙂ, EventArgs 1AAAA) --- End of inner exception stack trace --- |
|
|
|
|
host
Posts:502
 |
| 01/25/2010 09:03 |
|
| Email sent. |
|
|
|
|
ruizzie
Posts:7
 |
| 06/01/2010 17:04 |
|
I just got the same error in demo version 4.3 which I have installed on DNN 5.4.2. My locale is nl-NL: DotNetNuke.Services.Exceptions.ModuleLoadException: De tekenreeks is niet als geldige DateTime herkend. ---> System.FormatException: De tekenreeks is niet als geldige DateTime herkend. bij System.DateTimeParse.ParseExact(String s, String format, DateTimeFormatInfo dtfi, DateTimeStyles style) bij BeckerSolutions.Modules.RS2005.ViewRS2005.CheckStatus() bij BeckerSolutions.Modules.RS2005.ViewRS2005.Page_Load(Object sender, EventArgs e) Is the script mentioned above still required? |
|
|
|
|
host
Posts:502
 |
| 06/01/2010 19:58 |
|
Interesting, the only way this bug would still be present is if you had installed the 4.3 version on top of an existing install of the module, did you do this? Make sure to download the latest copy of it from our website as well so you are not using some older copy of it. If you had already done an install of an older version or copy of the module, can try doing this: 1) Uninstall the module 2) Go to host -> sql, check run as script box and paste this code in there and run it. delete from {databaseOwner}{objectQualifier}ModuleSettings where moduleid in (select moduleid from {databaseOwner}{objectQualifier}ModuleSettings where settingname = 'ModuleDefaultDate'); 3) Reinstall the module and reactivate. Please report if you are good after this and advise if you had a prior version installed. |
|
|
|
|
ruizzie
Posts:7
 |
| 06/02/2010 02:50 |
|
I had to reinstall the module a few times, but always version 4.3, downloaded from your site.
The path I followed was:
- Installed DNN Reports module (unrelated I presume) on 5.4.1, did not get this to work properly
- Installed MM Reporting Services
- got KeyNotFoundException exception during installation
- Upgraded site to DNN 5.4.2
- finally fixed this via instructions in this thread.
- Did a few re-installs of the module in this process.
- Got Object not found (or null reference) error->fixed my config
- Got the Date conversion error.
- Hit the forums and here we are.
|
|
|
|
|
dpijl10
Posts:11
 |
| 06/02/2010 03:23 |
|
Hi, we had the same errormessage in locale nl-NL.
We fixed it this way:
1) Uninstall the module
2) Go to host -> sql, check run as script box and paste this code in there and run it.
delete from {databaseOwner}{objectQualifier}ModuleSettings
where moduleid in (select moduleid from {databaseOwner}{objectQualifier}ModuleSettings
where settingname = 'ModuleDefaultDate');
3) Reinstall the module
4) Use a portal with language setting "en-US" <- important
5) Drop the module on this page
6) Reactivate.
After activation it will work in all languages.
|
|
|
|
|
ruizzie
Posts:7
 |
| 06/02/2010 04:12 |
|
The given instructions appear to work, but now when I request the report, the reportviewer is not functioning properly:

The same thing happend when I tried the DNN reports module so I assume there is something wrong with the ReportViewer.dll?
|
|
|
|
|
dpijl10
Posts:11
 |
| 06/02/2010 04:24 |
|
We've seen that one before too...
Are you using IIS7? Check your web.config file ! The reference to the viewercontrol needs to be in the system.webServer section too, with the "Integrated" mode enabled.
..
preCondition="integratedMode,runtimeVersionv2.0" />
...
|
|
|
|
|
dpijl10
Posts:11
 |
| 06/02/2010 04:30 |
|
hmm that looked crazy... replace [] with appropriate tags
[section.webServer]
[module]
...
[/module]
[handler]
[add name="ReportViewerHandler" path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" preCondition="integratedMode,runtimeVersionv2.0"/]
...
[/handler]
[/section.webServer]
|
|
|
|
|
ruizzie
Posts:7
 |
| 06/02/2010 04:42 |
|
You are fantastic, thanks for the quick reply!
It's working now, I found a workaround at ReportXP's site but that meant changing the whole application model.
This is much better. I did not even have the handler you specify. I had a verb present but I understand IIS7 will look at the handlers section over the httpHandlers section.
Thank for all the support quick and proficient support!
|
|
|
|
|
host
Posts:502
 |
| 06/02/2010 07:34 |
|
| Feel free to email your web.config to service@modulemasters.com and we can spot check it for you if you are still having issues. |
|
|
|
|
host
Posts:502
 |
| 06/02/2010 23:25 |
|
| Well, apparently the bug is not entirely squashed on this one. I was able to replicate the datetime issue by setting the DNN language to nl-NL and activating the trial and the error occurred. Right now the work around is to run the delete script, change the language to en-US and activate. We had this issue when the regional settings of the machine was set to some other cultures, apparenty it occurs when DNN is also set, glad the mystery is solved, a fix for it will be available soon! |
|
|
|
|
host
Posts:502
 |
| 06/08/2010 19:42 |
|
| The datetime bug is now officially crushed. The download has been updated here and snowcovered. The issue was with non M/D/YYYY formats in the locale settings and was brought about by not only the regional settings of the web server, but also by the locale set within DNN at the time of registration. Glad to see this one resolved, anyone with any lingering issues, please let us know. |
|
|
|
|
ruizzie
Posts:7
 |
| 07/06/2010 05:24 |
|
Uhm.. I just activated the software and got the datetime bug. Redownloaded from the link in the mail message (RS2005_040300.zip dd. 17 june 2010?), uninstalled en reinstalled, but the bug is still happening.
I will try the workaround but I thought this shouldn't be necessary anymore?
|
|
|
|
|
host
Posts:502
 |
| 07/06/2010 06:25 |
|
| That file is the right one as of the date of this message, however I am very interested in the error logs from DNN and to know specifics on what locale you have set in DNN and the exact error messages, I find it hard to believe that this issue still exists. Did you upgrade from a previous version? |
|
|
|
|
ruizzie
Posts:7
 |
| 07/06/2010 07:34 |
|
The original error:
ModuleId: 685
ModuleDefId: 149
FriendlyName: Bezettingsprognose
ModuleControlSource: DesktopModules/RS2005/ViewRS2005.ascx
AssemblyVersion: 5.4.2
PortalID: 0
PortalName: AMZ Extranet
UserID: 1
UserName: host
ActiveTabID: 227
ActiveTabName: Bezettingsprognose
RawURL: /Default.aspx?tabid=227&language=nl-NL
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://extranet/Default.aspx?tabid=227&language=nl-NL
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; GTB6.5; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 1d70317f-8df7-4980-8947-ba13c2ddd378
InnerException: De tekenreeks is niet als geldige DateTime herkend.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.DateTimeParse.ParseExact
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: De tekenreeks is niet als geldige DateTime herkend. ---> System.FormatException: De tekenreeks is niet als geldige DateTime herkend. bij System.DateTimeParse.ParseExact(String s, String format, DateTimeFormatInfo dtfi, DateTimeStyles style) bij BeckerSolutions.Modules.RS2005.ViewRS2005.CheckStatus() bij BeckerSolutions.Modules.RS2005.ViewRS2005.Page_Load(Object sender, EventArgs e) --- Einde van intern uitzonderingsstackpad ---
During the final reinstall, after the SQL fix and switching to EN-us:
...
Info:: Start uitvoer Sql: 01.02.00.SqlDataProvider bestand
Info:: SQL uitvoer leverde de volgende uitzonderingen op: System.Data.SqlClient.SqlException: Column names in each table must be unique. Column name 'Domain' in table 'dbo.RS2005Servers' is specified more than once. bij System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) bij System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) bij System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) bij System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) bij System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) bij System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) bij System.Data.SqlClient.SqlCommand.ExecuteNonQuery() bij DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL) bij DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) /************************************************************/ /***** SqlDataProvider *****/ /***** *****/ /***** *****/ /***** Note: To manually execute this script you must *****/ /***** perform a search and replace operation *****/ /***** for dbo. and *****/ /***** *****/ /************************************************************/ /** Create Table **/ if exists (select * from dbo.sysobjects where id = object_id(N'dbo.RS2005Servers') and OBJECTPROPERTY(id, N'IsTable') = 1) ALTER TABLE dbo.RS2005Servers ADD [Domain] varchar(100)
Info:: Einde Sql uitvoer: 01.02.00.SqlDataProvider gereed
Info:: Backup van vorige versie wordt gemaakt - 01.04.00.SqlDataProvider
Info:: Aangemaakt - 01.04.00.SqlDataProvider
Info:: Uitvoeren01.04.00.SqlDataProvider
Info:: Start uitvoer Sql: 01.04.00.SqlDataProvider bestand
Info:: SQL uitvoer leverde de volgende uitzonderingen op: System.Data.SqlClient.SqlException: Column names in each table must be unique. Column name 'PortalId' in table 'dbo.RS2005Servers' is specified more than once. bij System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) bij System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) bij System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) bij System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) bij System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) bij System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) bij System.Data.SqlClient.SqlCommand.ExecuteNonQuery() bij DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL) bij DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) /************************************************************/ /***** SqlDataProvider *****/ /***** *****/ /***** *****/ /***** Note: To manually execute this script you must *****/ /***** perform a search and replace operation *****/ /***** for dbo. and *****/ /***** *****/ /************************************************************/ /** Alter Table **/ /** Change Log --added portalid **/ if exists (select * from dbo.sysobjects where id = object_id(N'dbo.RS2005Servers') and OBJECTPROPERTY(id, N'IsTable') = 1) BEGIN ALTER TABLE dbo.[RS2005Servers] ADD [PortalId] INT NULL END
Info:: Einde Sql uitvoer: 01.04.00.SqlDataProvider gereed
This doesn't seem to have given any problems though, the activated module now works correct.
The bug first showed when I tried to activate (NL-nl) and then after reinstalling the latest version. Only after performing the SQL fix and switching languages did the install and activitation succeed.
|
|
|
|
|