Error 516 @ SUP101-Tutorial (iOS)

[Former Member]

Hi,

i´ve tried to go through the SUP101-Tutorial for Developing an iOS-App. Everythin works fine til getting a connection to SUP. I´ve already set a PIN and filled out the information in the iOS-Settings-Menu. When i run the code i have to fill in the PIN. Then a button with "Synchronize" is shown. Now there a two options:

• And after waiting 5 minutes the error 516 ("Error sending request to server") appears.
• When i click the "Synchronize"-Button twice the app crashes.

Here is the log:

2013-01-18 08:30:54.173 SUP101[736:c07] Application windows are expected to have a root view controller at the end of application launch

2013-01-18 08:31:01.299 SUP101[736:c07] App has been run before.

2013-01-18 08:31:01.299 SUP101[736:c07] Unlock messaging vault

2013-01-18 08:31:01.763 SUP101[736:c07] Got the encryption key: e45f05eb8d851770f6e3b039f36f0517a175f051430830c5ebc083e3ce820f7e00e34103f75103e77075d7a0b7efa0bb

2013-01-18 08:31:01.797 SUP101[736:c07] =================================================

2013-01-18 08:31:01.797 SUP101[736:c07] onConnectionStatusChanged: status = 102, code = 0, message = (null)

2013-01-18 08:31:01.797 SUP101[736:c07] =================================================

2013-01-18 08:31:01.805 SUP101[736:450f] =================================================

2013-01-18 08:31:01.805 SUP101[736:450f] onConnectionStatusChanged: status = 105, code = 0, message =

2013-01-18 08:31:01.806 SUP101[736:450f] =================================================

2013-01-18 08:31:01.806 SUP101[736:450f] =================================================

2013-01-18 08:31:01.807 SUP101[736:450f] onConnectionStatusChanged: status = 105, code = 0, message =

2013-01-18 08:31:01.807 SUP101[736:450f] =================================================

2013-01-18 08:31:02.351 SUP101[736:c07] waiting for connection...

2013-01-18 08:31:02.392 SUP101[736:5e03] =================================================

2013-01-18 08:31:02.392 SUP101[736:5e03] onConnectionStatusChanged: status = 103, code = 0, message =

2013-01-18 08:31:02.393 SUP101[736:5e03] =================================================

2013-01-18 08:31:02.393 SUP101[736:c07] Unlock SUP101 vault to get username/password credentials

2013-01-18 08:31:02.394 SUP101[736:5e03] =================================================

2013-01-18 08:31:02.395 SUP101[736:5e03] onConnectionStatusChanged: status = 103, code = 0, message =

2013-01-18 08:31:02.395 SUP101[736:5e03] =================================================

2013-01-18 08:31:03.595 SUP101[736:c07] [SQL TRACE][DEBUG] Synchronizing... ULRemoteId<Unknown> SynchronizationGroup<initialSync> UserContext<>

2013-01-18 08:31:04.437 SUP101[736:c07] [SQL TRACE][DEBUG] Synchronizing... ULRemoteId<Unknown> SynchronizationGroup<initialSync> UserContext<>

2013-01-18 08:36:02.829 SUP101[736:5e03] =================================================

2013-01-18 08:36:02.831 SUP101[736:5e03] onConnectionStatusChanged: status = 105, code = 516, message = Error: 516 Detail: Error sending request to server Native Error: -2 Source: /Users/iotabuilder/svn/Pioneer/MOClients/iPhone/../Common/C/moClient.cpp 1754.

2013-01-18 08:36:02.832 SUP101[736:5e03] =================================================

2013-01-18 08:36:02.833 SUP101[736:5e03] =================================================

2013-01-18 08:36:02.834 SUP101[736:5e03] onConnectionStatusChanged: status = 105, code = 516, message = Error: 516 Detail: Error sending request to server Native Error: -2 Source: /Users/iotabuilder/svn/Pioneer/MOClients/iPhone/../Common/C/moClient.cpp 1754.

2013-01-18 08:36:02.834 SUP101[736:5e03] =================================================

2013-01-18 08:36:03.324 SUP101[736:5e03] =================================================

2013-01-18 08:36:03.325 SUP101[736:5e03] onConnectionStatusChanged: status = 103, code = 0, message =

2013-01-18 08:36:03.325 SUP101[736:5e03] =================================================

2013-01-18 08:36:03.325 SUP101[736:5e03] =================================================

2013-01-18 08:36:03.326 SUP101[736:5e03] onConnectionStatusChanged: status = 103, code = 0, message =

2013-01-18 08:36:03.326 SUP101[736:5e03] =================================================

I hope someone can help me.

Thank you in advance!

Regards, Florian.

[brenton_ocallaghan]

Hi Florian,

From the log above it looks like your app is successfully registering the device with the SCC - the code 103 being returned is a good sign and you are probably showing up as online in the server for a few seconds at least.

However it looks to me like you might have a misconfiguration on your synchronisation profile and perhaps it is not pointing at the server correctly. For example on my dev system I would specify port 5001 for the MBS based device registration (the bit you have working) and then the synchronisation profile would have port 2480 (for RBS).

If you are not specifying either the correct server details or the right credentials for connection you might see something like this being returned.

I've posted an example here which may help you out - if you are still having a problem please post back with a code snippet and I can have another look.

Hope that helps,

Brenton.

[Former Member]

Hi Brenton,

We are getting the same error :

**************

status = 101, code= 516, message = Error: 516 Detail: Error sending request to server Native
Error: -2 Source: moClient.cpp 2036.

**************

We have checked the synchronization profile config and all the ports value in 2.3.4 SCC but still app stucks and throwing the same error.

Android version of the app working correctly against the same SUP server and packages.

Can you please tell us what is causing the problem though all the settings are correct ? Does  "moclient.cpp" library create any problem in syncing to SUP server for iOS app ?

Thanks in advance!

[Former Member]

Hi Florian...

I too  faced same problem...i m also very new to SUP....If i enter my PIN and click OK button it shows Synchrinise View...if i click the Synchrinose button it does't move to next view controller...if shows the status on log like this

2013-02-05 15:57:53.234 SUP101[8804:c07] Application windows are expected to have a root view controller at the end of application launch

2013-02-05 15:58:05.178 SUP101[8804:c07] App has been run before.

2013-02-05 15:58:05.179 SUP101[8804:c07] Unlock messaging vault

2013-02-05 15:58:06.861 SUP101[8804:c07] Got the encryption key: d7ad00037ef9ec0d34e3ce34038179f3bf3bdf9005df90b4142174ebb0c1084e34e05dc1f450baf43f79e7d041e3ddf4

2013-02-05 15:58:06.939 SUP101[8804:c07] =================================================

2013-02-05 15:58:06.940 SUP101[8804:c07] onConnectionStatusChanged: status = 102, code = 0, message = (null)

2013-02-05 15:58:06.940 SUP101[8804:c07] =================================================

2013-02-05 15:58:07.018 SUP101[8804:451f] =================================================

2013-02-05 15:58:07.018 SUP101[8804:451f] onConnectionStatusChanged: status = 105, code = 0, message =

2013-02-05 15:58:07.020 SUP101[8804:451f] =================================================

2013-02-05 15:58:07.021 SUP101[8804:451f] =================================================

2013-02-05 15:58:07.022 SUP101[8804:451f] onConnectionStatusChanged: status = 105, code = 0, message =

2013-02-05 15:58:07.023 SUP101[8804:451f] =================================================

2013-02-05 15:58:07.107 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2be _Z15GetTimeZoneInfoP10PIONEER_TZ + 574

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d446 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 114

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.112 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2f0 _Z15GetTimeZoneInfoP10PIONEER_TZ + 624

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d446 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 114

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.122 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2be _Z15GetTimeZoneInfoP10PIONEER_TZ + 574

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d693 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 703

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.125 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2f0 _Z15GetTimeZoneInfoP10PIONEER_TZ + 624

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d693 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 703

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.297 SUP101[8804:5c03] =================================================

2013-02-05 15:58:07.297 SUP101[8804:5c03] onConnectionStatusChanged: status = 103, code = 0, message =

2013-02-05 15:58:07.298 SUP101[8804:5c03] =================================================

2013-02-05 15:58:07.299 SUP101[8804:5c03] =================================================

2013-02-05 15:58:07.299 SUP101[8804:5c03] onConnectionStatusChanged: status = 103, code = 0, message =

2013-02-05 15:58:07.299 SUP101[8804:5c03] =================================================

2013-02-05 15:58:07.661 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2be _Z15GetTimeZoneInfoP10PIONEER_TZ + 574

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d446 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 114

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.663 SUP101[8804:c07] Unlock SUP101 vault to get username/password credentials

2013-02-05 15:58:07.664 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2f0 _Z15GetTimeZoneInfoP10PIONEER_TZ + 624

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d446 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 114

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.678 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2be _Z15GetTimeZoneInfoP10PIONEER_TZ + 574

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d693 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 703

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.686 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2f0 _Z15GetTimeZoneInfoP10PIONEER_TZ + 624

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d693 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 703

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.698 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2be _Z15GetTimeZoneInfoP10PIONEER_TZ + 574

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d446 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 114

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.704 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2f0 _Z15GetTimeZoneInfoP10PIONEER_TZ + 624

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d446 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 114

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.713 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2be _Z15GetTimeZoneInfoP10PIONEER_TZ + 574

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d693 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 703

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.716 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2f0 _Z15GetTimeZoneInfoP10PIONEER_TZ + 624

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d693 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 703

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.800 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2be _Z15GetTimeZoneInfoP10PIONEER_TZ + 574

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d446 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 114

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

2013-02-05 15:58:07.816 SUP101[8804:5d03] *** -[__NSCFCalendar components:fromDate:]: date cannot be nil

I mean really, what do you think that operation is supposed to mean with a nil date?

An exception has been avoided for now.

A few of these errors are going to be reported with this complaint, then further violations will simply silently do whatever random thing results from the nil.

Here is the backtrace where this occurred this time (some frames may be missing due to compiler optimizations):

(

          0   CoreFoundation                      0x00c31a75 -[__NSCFCalendar components:fromDate:] + 85

          1   SUP101                              0x0016c2f0 _Z15GetTimeZoneInfoP10PIONEER_TZ + 624

          2   SUP101                              0x00117d20 _Z18EGetPioneerTZIndexb + 32

          3   SUP101                              0x0014b11f _ZN10ECDateTime14BiasCalculatorERKS_R10ECTimeSpaniPb + 167

          4   SUP101                              0x0014b9ce _ZN10ECDateTime10EGetGMTimeERKS_i + 178

          5   SUP101                              0x0018d3ca _ZL16GetCurrentGMTimev + 58

          6   SUP101                              0x0018d446 _ZN2mo23CmocaProcessClientQueue20WaitForQueuedRequestERlRNS_9CmoStringES3_S1_S3_l + 114

          7   SUP101                              0x0018da99 _ZN2mo23CmocaProcessClientQueue18ProcessTillStoppedEv + 245

          8   SUP101                              0x00182674 _ZN2mo17CmocaProcessQueue7ProcessEv + 200

          9   SUP101                              0x0018131b _ZN2mo17CmocaProcessQueue10MOCAThreadEPv + 57

          10  libsystem_c.dylib                   0x97f28557 _pthread_start + 344

          11  libsystem_c.dylib                   0x97f12cee thread_start + 34

)

[Former Member]

Hello, you have some results on the problem ? I'm in the same situation. Thanks !