SQL Server 2008 R2 Express - Not capturing output from Eaton ETN 2000 Inverter

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Commencing the PVBC service. Output from the PVService log file suggests a 
string variable is trying to be recorded in a date/time variable. The PVBC 
service is then automatically shutdown.
2. I've activated the Trace, Meter Trace and Meter message in the log file. Not 
much additional information was captured in the log file, so I then also 
enabled the information and status options in the log file. 
3.Output from the 31/07/2011 around 12pm has the most detaied log file 
information, however I've included the entire PVService log file in case 
previous entries are of interest.

What is the expected output? What do you see instead?
Expect to see my Eaton ETN 2000 inverter recognised as a CMS Inverter type, and 
the data captured and stored in the SQl Server database

What version of the product are you using (e.g. 1.4.1.9 32bit)?
Version 1.5.0.5 according to the log file.

What Operating system (XP, Vista, Windows 7 - 32bit or 64bit)?
Windows WP - 32 bit.

Which Database Type (MySQL, MS Access, SQLite - If Access, 32bit or 64bit)?
SQL Server 2008 R2 Express

Are there any unusual messages in PVService.log? (upload a copy to this
issue if there are)

Yes - message as follows;

7/31/2011 12:09:42 PM :T5 ExecutionManager :InverterManagerManager: Loading 
Inverter Managers
7/31/2011 12:09:42 PM :T5 ExecutionManager :InverterManagerManager: Starting 
Inverter Managers - Type: CMS - Exception: String was not recognized as a valid 
DateTime.
7/31/2011 12:09:42 PM :T5 ExecutionManager :ExecutionStateManager: exception: 
StartInverterManagers: String was not recognized as a valid 
DateTime.PVInverterManagement.PVException
7/31/2011 12:09:42 PM :T5 ExecutionManager :ExecutionStateManager: Shutdown 
Requested

Please upload your settings.xml file with the issue. This answers many
questions I would otherwise need to ask.

I've attached the PVHistory and settings files.

Please provide any additional information below.

Thanks in advance for letting me add this as an issue. I suspect the output 
fields from my Eaton ETN 2000 Inverter are in a different format to that 
required.....although I'm a Solar newbie so that's just a guess!

Original issue reported on code.google.com by SolarNew...@gmail.com on 31 Jul 2011 at 2:34

[GoogleCodeExporter]

Request to support a different type of inverter

Original comment by DennisMackayFisher on 31 Jul 2011 at 5:45

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

The problem you have encountered is not related to the type of inverter. Your 
computer has a default "Locale" set to a something like English-USA. This 
results in the american style dates in the PVService.log file. This is the 
format used by the PVBC "Service" to read and write dates.

The "First Full Day" setting in the Settings.xml file uses the English / 
Australian date format. This indicates that your login is using a different 
Locale / date format to that used by your computer's service accounts. The date 
recorded in the Configuration program using your personal login Locale cannot 
be read by the Local Service account that is running PVService.exe.

The latest version 1.5.0.12 has extra date logic to deal with this issue. 
Install 1.5.0.12. Change the First Full Day again. This will cause PVBC to 
record your date format in the settings.xml file. The Service will use this 
explicit date format when reading the dates in Settings.xml.

To fix the problem with version 1.5.0.5 (this is probably worth doing anyway):

Control Panel -> Region and Language -> Administrative -> Copy Settings
Check "Welcome screen and system accounts" and "New accounts".
OK to save these changes.
Reboot the computer so that the changes take effect on all system services.

The above steps will copy your personal login Locale to the settings used by 
services and new accounts on the computer.

Dennis M-F

Original comment by DennisMackayFisher on 31 Jul 2011 at 6:08

• Changed state: Started

[GoogleCodeExporter]

Have you had any progress here?

Original comment by DennisMackayFisher on 5 Aug 2011 at 10:28

[GoogleCodeExporter]

Following has been copied from a direct email.............

Hi Dennis - please ignore my previous email. I decided to start from scratch 
again and now the database is communicating perfectly with the inverter. Steps 
I completed as follows;

    Delete PVHistory database from SQL Server
    Uninstall PV Bean Counter version 1.5.0.12
    Restart computer
    Recreate PV history database in SQL Server
    Grant full permissions on PVHistory database
    Reinstall PV Bean Counter version 1.5.0.12
    Configure PV Bean counter and reset first full day.

I tried it today and all expected PV History data is now being captured in the 
PV History database for the complete day.

Thanks again for making the Sql Server script and PV Bean Counter software 
available, you are a legend :)

cheers,

Original comment by DennisMackayFisher on 6 Aug 2011 at 2:22

• Changed state: Verified