Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

SUPPersistenceException: exception is in personalizationParameters

3 posts in General Discussion Last posting was on 2013-02-26 13:11:38.0Z
Guven Posted on 2012-10-03 16:06:06.0Z
Sender: 70a5.506c3131.1804289383@sybase.com
From: Guven
Newsgroups: sybase.public.sup.general
Subject: SUPPersistenceException: exception is in personalizationParameters
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <506c626e.7959.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 3 Oct 2012 09:06:06 -0700
X-Trace: forums-1-dub 1349280366 172.20.134.41 (3 Oct 2012 09:06:06 -0700)
X-Original-Trace: 3 Oct 2012 09:06:06 -0700, 172.20.134.41
Lines: 27
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sup.general:1105
Article PK: 1020176

SUP 2.1.3 & XCode 4.5 & SDK iOS 6.0 & ARC enabled Project &
Mac OSx 10.7.5

1) Registration of the application succeeds.
2) The call to 'beginSynchronizeWithListener:self' is made.
3) SUPPersistenceException is thrown from within this call.
Following trace is captured:

SELECT
p."key_name",p."user",p."value",p."user_defined",p."description"
,p."id" from "co_<myPackageName>_clientpersonalization" p
where p."user" = ?
{thread:0xa98f790,dbConn:0xc956900}:user = supAdmin
{thread:0xa98f790,dbConn:0xc956900}: --- 0 rows selected
SUPPersistenceException: SUPPersistenceException from
synchronize: -- SUPPersistenceException: exception is in
personalizationParameters: -[SUPClientPersonalization
setKey_name:]: unrecognized selector sent to instance
0xc076770

4) The synchronization fails. Cannot proceed due to this
exception.

I am not sure if the query to the 'clientpersonalization'
table should return 0 rows. The exception occurs in the
libraries so I cannot debug to see exactly where the
exception is being thrown.


Nisha Posted on 2013-02-26 11:17:32.0Z
Sender: 1498.512c9832.1804289383@sybase.com
From: Nisha
Newsgroups: sybase.public.sup.general
Subject: Re: SUPPersistenceException: exception is in personalizationParameters
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <512c99cc.152d.1681692777@sybase.com>
References: <506c626e.7959.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 26 Feb 2013 03:17:32 -0800
X-Trace: forums-1-dub 1361877452 172.20.134.41 (26 Feb 2013 03:17:32 -0800)
X-Original-Trace: 26 Feb 2013 03:17:32 -0800, 172.20.134.41
Lines: 65
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sup.general:1142
Article PK: 1307931

Hi All,

I am facing exactly the same issue. Creating a simple
personalization parameter, fails on subscribe. If I skip
subscribe step, then it fails on synchronize.
This is happening only on iOS. The same SUP project works
fine for Android.

I debugged in the generated code, and it is failing in the
init of the PersonalizationParameters.

- (id) init
{
if ((self = [super init]))
{
self.classMetaData = (SUPEntityMetaDataRBS
*)[GCPPersonalizationParameters metaData];
[self setClassDelegate:[[self class] delegate]];
self.CRM_ID = (NSString*)@"BUSDEV03";
self.CRM_IDUserDefined = NO;
_usernameUserDefined = NO;
_passwordUserDefined = NO;
clientPersonalizationTableName =
@"co_glanbiacustomer_1_0_clientpersonalization";
[self load]; //Where it fails

}
return self;
}

Anybody who has any idea on what could be the issue, please
help.
I have tried setting a default value for the personalization
parameter, making it nullable. But does not work.

Thanks

> SUP 2.1.3 & XCode 4.5 & SDK iOS 6.0 & ARC enabled Project
> & Mac OSx 10.7.5
>
> 1) Registration of the application succeeds.
> 2) The call to 'beginSynchronizeWithListener:self' is
> made. 3) SUPPersistenceException is thrown from within
> this call. Following trace is captured:
>
> SELECT
> p."key_name",p."user",p."value",p."user_defined"
> ,p."description" ,p."id" from
> "co_<myPackageName>_clientpersonalization" p where
> p."user" = ? {thread:0xa98f790,dbConn:0xc956900}:user =
> supAdmin {thread:0xa98f790,dbConn:0xc956900}: --- 0 rows
> selected SUPPersistenceException: SUPPersistenceException
> from synchronize: -- SUPPersistenceException: exception is
> in personalizationParameters: -[SUPClientPersonalization
> setKey_name:]: unrecognized selector sent to instance
> 0xc076770
>
> 4) The synchronization fails. Cannot proceed due to this
> exception.
>
> I am not sure if the query to the 'clientpersonalization'
> table should return 0 rows. The exception occurs in the
> libraries so I cannot debug to see exactly where the
> exception is being thrown.


Nisha Posted on 2013-02-26 13:11:38.0Z
Sender: 1498.512c9832.1804289383@sybase.com
From: Nisha
Newsgroups: sybase.public.sup.general
Subject: Re: SUPPersistenceException: exception is in personalizationParameters
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <512cb48a.1ed6.1681692777@sybase.com>
References: <512c99cc.152d.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 26 Feb 2013 05:11:38 -0800
X-Trace: forums-1-dub 1361884298 172.20.134.41 (26 Feb 2013 05:11:38 -0800)
X-Original-Trace: 26 Feb 2013 05:11:38 -0800, 172.20.134.41
Lines: 87
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sup.general:1143
Article PK: 1307940

Hi All,

Just figure out the reason. It is basically a bug in the
client api for iphone which has been fixed in the ESD3 patch
released in June.

For those who face this error, make sure that you install
the patch on your SUP server for 2.1.3.

And in your client xcode project, do not forget to add the
updated iOS libraries as a reference. It is a client API
fix, so you need to reference the updated libraries.

Subscribe or synchronize should work smoothly thereafter.

This was the link that helped me :
http://search.sybase.com/kbx/changerequests?bug_id=710893

Thanks

> Hi All,
>
> I am facing exactly the same issue. Creating a simple
> personalization parameter, fails on subscribe. If I skip
> subscribe step, then it fails on synchronize.
> This is happening only on iOS. The same SUP project works
> fine for Android.
>
> I debugged in the generated code, and it is failing in the
> init of the PersonalizationParameters.
>
> - (id) init
> {
> if ((self = [super init]))
> {
> self.classMetaData = (SUPEntityMetaDataRBS
> *)[GCPPersonalizationParameters metaData];
> [self setClassDelegate:[[self class] delegate]];
> self.CRM_ID = (NSString*)@"BUSDEV03";
> self.CRM_IDUserDefined = NO;
> _usernameUserDefined = NO;
> _passwordUserDefined = NO;
> clientPersonalizationTableName =
> @"co_glanbiacustomer_1_0_clientpersonalization";
> [self load]; //Where it fails
>
> }
> return self;
> }
>
> Anybody who has any idea on what could be the issue,
> please help.
> I have tried setting a default value for the
> personalization parameter, making it nullable. But does
> not work.
>
> Thanks
>
>
> > SUP 2.1.3 & XCode 4.5 & SDK iOS 6.0 & ARC enabled
> > Project & Mac OSx 10.7.5
> >
> > 1) Registration of the application succeeds.
> > 2) The call to 'beginSynchronizeWithListener:self' is
> > made. 3) SUPPersistenceException is thrown from within
> > this call. Following trace is captured:
> >
> > SELECT
> > p."key_name",p."user",p."value",p."user_defined"
> > ,p."description" ,p."id" from
> > "co_<myPackageName>_clientpersonalization" p where
> > p."user" = ? {thread:0xa98f790,dbConn:0xc956900}:user =
> > supAdmin {thread:0xa98f790,dbConn:0xc956900}: --- 0 rows
> > selected SUPPersistenceException:
> > SUPPersistenceException from synchronize: --
> > SUPPersistenceException: exception is in
> > personalizationParameters: -[SUPClientPersonalization
> > setKey_name:]: unrecognized selector sent to instance
> 0xc076770 >
> > 4) The synchronization fails. Cannot proceed due to this
> > exception.
> >
> > I am not sure if the query to the
> > 'clientpersonalization' table should return 0 rows. The
> > exception occurs in the libraries so I cannot debug to
> > see exactly where the exception is being thrown.