search

Jishar13 / pvbeancounter

Automatically exported from code.google.com/p/pvbeancounter
1 stars 0 forks source link

Not starting DateTime invalid message in log #84

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.starting service 
2.
3.
Does not seem to start 

log below 

--------------------------------------------------------------------------------
-----------------------

--------------------------------------------------------------------------------
--------------------------------------------------------
Timeline Content
--------------------------------------------------------------------------------
--------------------------------------------------------
Start: 00:00:00 - End: 04:59:00 - Sleeping - EveningSuspend - Mandatory
Start: 05:00:00 - End: 20:59:00 - Running - EveningSuspend
Start: 21:00:00 - End: 23:59:00 - Sleeping - EveningSuspend - Mandatory
--------------------------------------------------------------------------------
--------------------------------------------------------
7/26/2011 1:31:32 PM :T6 ExecutionManager :ExecutionStateManager: State: 
Running Until:7/26/2011 9:00:00 PM
7/26/2011 1:31:32 PM :T6 ExecutionManager :InverterManagerManager: 
StartService: connecting to database: Data Source=C:\PVRecords\pvhistory.s3db
7/26/2011 1:31:32 PM :T6 ExecutionManager :InverterManagerManager: Starting 
Inverter Managers - Type: Sunny Explorer - Exception: String was not recognized 
as a valid DateTime.
7/26/2011 1:31:32 PM :T6 ExecutionManager :ExecutionStateManager: exception: 
StartInverterManagers: String was not recognized as a valid 
DateTime.PVInverterManagement.PVException
7/26/2011 1:31:32 PM :T6 ExecutionManager :ExecutionStateManager: Shutdown 
Requested
7/26/2011 1:31:32 PM :T6 ExecutionManager :ExecutionStateManager: State: 
Shutdown

Original issue reported on code.google.com by pwwukpw on 26 Jul 2011 at 12:35

GoogleCodeExporter commented 8 years ago 
I suspect there is an invalid date entered into "First Full Day" on the Basic 
Setup tab. It should look something like: 13/07/2011

Check this. If you cannot find the fault, please upload the settings.xml file

Dennis M-F

Original comment by DennisMackayFisher on 26 Jul 2011 at 12:40

GoogleCodeExporter commented 8 years ago 
First Full day field is :

13/04/2011 

Copied from field .. appear in order .. Re selected . Saved .. Restarted .. 
Same error

Original comment by pwwukpw on 26 Jul 2011 at 12:59

GoogleCodeExporter commented 8 years ago 
Can you please upload the settings.xml file (use Attach a file)

I cannot diagnose the problem without seeing the content of this file.

It would be useful to upload the PVService,log file at the same time.

Dennis M-F

Original comment by DennisMackayFisher on 26 Jul 2011 at 1:13

GoogleCodeExporter commented 8 years ago 
I suggest you try setting the date using the button beside the date field. 

The log extract you have attached indicates your computer account (Local 
Service) is using an American date format. The same format must be used in the 
settings.xml file. 

If your personal computer account is not using the same format, you may need to 
manually adjust the date entry or align your personal date format with the 
system (Local Service) default date format.

Dennis M-F

Original comment by DennisMackayFisher on 26 Jul 2011 at 1:19

GoogleCodeExporter commented 8 years ago 
Updated call log .. did not fix .. any more ideas ?

Original comment by pwwukpw on 26 Jul 2011 at 1:26

GoogleCodeExporter commented 8 years ago 
Dennis .. many thanks for your help  .. should I be updating using the call
log or email  >>?? Its confusing as I've not changed anything and was
working ..

In control panel my date time is set as (UTC) Dublin, Edinburgh, Lisbon,
London

Changed the date using the selector wigit ..

Same error

TY

Mandatory
Start: 05:00:00 - End: 20:59:00 - Running - EveningSuspend
Start: 21:00:00 - End: 23:59:00 - Sleeping - EveningSuspend - Mandatory
--------------------------------------------------------------------------------
--------------------------------------------------------
7/26/2011 2:29:53 PM :T6 ExecutionManager :ExecutionStateManager: State:
Running Until:7/26/2011 9:00:00 PM
7/26/2011 2:29:53 PM :T6 ExecutionManager :InverterManagerManager:
StartService: connecting to database: Data
Source=C:\PVRecords\pvhistory.s3db
7/26/2011 2:29:53 PM :T6 ExecutionManager :InverterManagerManager: Starting
Inverter Managers - Type: Sunny Explorer - Exception: String was not
recognized as a valid DateTime.
7/26/2011 2:29:53 PM :T6 ExecutionManager :ExecutionStateManager: exception:
StartInverterManagers: String was not recognized as a valid
DateTime.PVInverterManagement.PVException
7/26/2011 2:29:53 PM :T6 ExecutionManager :ExecutionStateManager: Shutdown
Requested
7/26/2011 2:29:53 PM :T6 ExecutionManager :ExecutionStateManager: State:
Shutdown

Original comment by pwwukpw on 26 Jul 2011 at 1:30

GoogleCodeExporter commented 8 years ago 
Go to Control Panel -> Region and Language -> Administrative -> Change System 
Locale

I expect you will find that this contains an american date format / Locale 
setting.

Change it to a format that matches your own account, save and reboot.

Ensure that the dates in the PVBC configuration program match your new settings 
before restarting PVBC.

Dennis M-F

Original comment by DennisMackayFisher on 26 Jul 2011 at 1:41

GoogleCodeExporter commented 8 years ago 
Dennis,

Thank you for being so helpful..

It was already set to UK

Peter

[image: image.png]

Original comment by pwwukpw on 26 Jul 2011 at 1:44

GoogleCodeExporter commented 8 years ago

Original comment by pwwukpw on 26 Jul 2011 at 1:48

GoogleCodeExporter commented 8 years ago 
Can you please upload the files requested using the "Attach a file" link below 
the comment box.

The entries such as
7/26/2011 2:29:53 PM :T6 ExecutionManager :ExecutionStateManager: State:
Running Until:7/26/2011 9:00:00 PM

show that your system is using a default date / time format that is typical in 
America and not typical in countries such as England, Australia, Ireland...

The key to the problem will be understanding why your system accounts (such as 
Local Service which is used by PVBC) have an unusual date format

Dennis

Original comment by DennisMackayFisher on 26 Jul 2011 at 1:51

GoogleCodeExporter commented 8 years ago 
The format in the image is as I expected. It is the format selected in 
Administrative -> Copy settings that I believe will be set to an American 
format for system accounts.

Open Administrative -> Copy Settings...

Check "Copy your current settings to: Welcome screen and system accounts"
and "New User Accounts".

Save and reboot.

Dennis

Original comment by DennisMackayFisher on 26 Jul 2011 at 1:57

GoogleCodeExporter commented 8 years ago 
Signing off now - it is getting late here. I will check back tomorrow morning

Original comment by DennisMackayFisher on 26 Jul 2011 at 2:05

GoogleCodeExporter commented 8 years ago 
Ok thanks for that .. seemed to fix it .. strange I've not had any issues
with other SW ..  Still your fix worked well .. & super software ..

Whilst I have you .. using my laptop from time to time to capture over
bluetooth and upload is fine but I hit the 60 per hour max ..
What would you recommend as a box to leave running all the time ? Guess
should be low power :-)

Many thanks ..

Peter

26/07/2011 15:05:02 :T6 ExecutionManager :ExecutionStateManager: State:
Running Until:26/07/2011 21:00:00
26/07/2011 15:05:02 :T6 ExecutionManager :InverterManagerManager:
StartService: connecting to database: Data
Source=C:\PVRecords\pvhistory.s3db
26/07/2011 15:05:02 :T6 ExecutionManager :InverterManagerManager:
NextFullDay set to no older than 15/04/2011 00:00:00 for manager Id 2
26/07/2011 15:05:02 :T6 ExecutionManager :Sunny Explorer: Inverter Manager -
Id = 2 loaded
26/07/2011 15:05:02 :T7 InverterManager :Sunny Explorer: RunExtract -
Inverter Manager - Id = 2 - manager running

Original comment by pwwukpw on 26 Jul 2011 at 2:07

GoogleCodeExporter commented 8 years ago 
I use a Vaio laptop. I let it run for 12 minutes every hour during the day. 

This new version should have less trouble with pvoutput hourly limits. Hitting 
the limit does not loose any data. It only delays data upload to pvoutput. It 
will eventually get there when you receive extra quota (every hour on the 
hour). 

Ensure "API Version" is left blank (currently defaults to r2). This give you a 
larger hourly quota at pvoutput as "r2" uses batched updates when there are 
multiple updates to be loaded. If you update pvoutput at least once each hour, 
you should never reach the limit. You should only reach the limit if you are 
"catching up" several hours.

Dennis M-F

Original comment by DennisMackayFisher on 26 Jul 2011 at 2:20

GoogleCodeExporter commented 8 years ago 
How can I tell if it has established a BT connection to the SB4000TL ? 
Do I need to run SunneyExplorer ? 

Thank you so much .. sorry to be a pain .. 

Peter

Original comment by pwwukpw on 27 Jul 2011 at 8:47

GoogleCodeExporter commented 8 years ago 
If you check "Trace" on the Log Files tab and save settings, you will get 
entries in the PVService.log file that shows current activity. You will see 
Sunny Explorer running every 5 minutes.

Of course, if data appears in your pvoutput.org dataset, it is working.

The database will also contain entries in the OutputHistory table.

There will be Sunny Explorer csv files in the Archive sub-directory

Dennis M-F

Original comment by DennisMackayFisher on 27 Jul 2011 at 10:31

GoogleCodeExporter commented 8 years ago 
If you have not upgraded to version 1.5.0.12, please do so.

I am closing this now as I believe all issues have been addressed

Original comment by DennisMackayFisher on 31 Jul 2011 at 7:27