Error processing ...

VMUser · Post by **VMUser** » Fri Jun 01, 2012 4:40 am

Many more error messages this morning, it started appearing every 1 minute.

Error processing 'http://mydomain.de/MyFolder/MyCalendar.ics'...

The error is: expecting "COLON", found '
' at line 891 and column 136.

...
The error is: expecting "COLON", found '
' at line 1158 and column 65.

...
The error is: expecting "COLON", found '
' at line 849 and column 54.

...
The error is: expecting "COLON", found '
' at line 251 and column 8.

After restarting VueMinder it stopped.

I see on my server that the ics files are changing every minute and I wonder why. I set up subscription to "every 1 minute" but publishing to "Whenever a change is made". But there is no change so VueMinder obviously rewrites the files every minute without change - why?

Post by **VueSoft** » Fri Jun 01, 2012 4:50 pm

When both publishing and subscribing to the same location, publishing will happen after the subscription updates. This ensures changes are kept in sync with other computers. If the subscription updates every 1 minute, then publishing will also happen every 1 minute.

I tried duplicating the problem with the ICS file that was provided. I configured the calendar to be both published and subscribed every 1 minute. So far, it has been running for 2 days straight and I haven't seen the problem yet. I'll keep it running over the weekend and will let you know if I can repeat the problem. At this point, I'm still not sure what is causing it.

VMUser · Post by **VMUser** » Fri Jun 01, 2012 5:43 pm

VueSoft wrote:When both publishing and subscribing to the same location, publishing will happen after the subscription updates. This ensures changes are kept in sync with other computers. If the subscription updates every 1 minute, then publishing will also happen every 1 minute.

Sorry, I don't really understand how this should work.

Directly after a subscription update I have two identical ics files on my PC and on my server. Why should publishing the same file back to the server help to keep sync with other computers?

With two computers using the same ics file there will be always a chance to miss and delete a change from the other computer. That's why I set up the update to every 1 minute.

Prior to VueMinder I used Thunderbird/Lightning but it was a mess. The ics files always got "locked" and didn't work then.

What is your recommendation in this case -- to use the same ics files with more than one computer?

Thanks.

VMUser · Post by **VMUser** » Thu Jun 28, 2012 2:16 am

Starting suddenly yesterday I'm getting new error messages for different calendars:

Error processing 'http://mydomain.de/_wichtige_Daten/1_Cal1.ics'...

The error is: expecting "COLON", found '
' at line 390 and column 4.

Error processing 'http://mydomain.de/_wichtige_Daten/1_Cal1.ics'...

The error is: expecting "COLON", found '
' at line 147 and column 31.

Error processing 'http://mydomain.de/_wichtige_Daten/2_Cal2.ics'...

The error is: expecting "END", found 'BEGI' at line 3253 and column 1.

Error processing 'http://mydomain.de/_wichtige_Daten/3_Cal3.ics'...

The error is: iCalDateTime.Parse cannot parse the value '20120628T163RIORITY:0' because it is not formatted correctly.

Error processing 'http://mydomain.de/_wichtige_Daten/3_Cal3.ics'...

The error is: expecting "COLON", found '
' at line 1157 and column 4.

Post by **VueSoft** » Thu Jun 28, 2012 9:20 pm

That's odd. I'm not sure what would have caused the error. Does restarting VueMinder and/or your computer fix it? Based on the errors, it appears there are problems with the files missing characters. Is something going on with your internet connection?

VMUser · Post by **VMUser** » Fri Jun 29, 2012 4:57 am

Yes, restarting VueMinder fixes it mostly. But some hours or days later suddenly it appears again.

My internet connection is quite reliable (ADSL).

VMUser · Post by **VMUser** » Fri Jun 29, 2012 9:17 am

Right now it started again:

16:13

Error processing 'http://mydomain.de/_wichtige_Daten/2_Cal2.ics'...

The error is: iCalDateTime.Parse cannot parse the value '20120629T140941ZxIGhvdXIyDgi7lYn02p7I5wgQARgBQgASGgoGMSBob3VyEggKBE5hbWUQARoAIgAyADoAcBM=' because it is not formatted correctly.