Error in SWUP/Cacao Register system

I am getting this on a brand new x86 install. I have read all the other posts and tried all the sugggested fixes with no success.Anyone know of other fixes not posted on this forum, or indeed the status of the bug 6444178 ?Thanks and regards.
[263 byte] By [DRooks] at [2007-11-26 9:33:29]
# 1
The bug responsible for this behaviour (actually bug ID 6452648 - bug 6444178 is just open to improve the error message) is closed as fixed as of 15th Aug.Are you still getting this error when attempting to register?
ForumModerator at 2007-7-7 0:21:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 2
Yes. Did a scratch reinstall yesterday and got the error immediately.
DRooks at 2007-7-7 0:21:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 3

I just upgraded another system using the latest CD images, this one a Sparc which had been running an older version of Solaris 10, and was already registered. After the upgrade, "smpatch update" told me the system was not registered, so I ran "sconadm register -c" and......... you guessed it, same error, "Error in SWUP/Cacao Register System".

Help!

DRooks at 2007-7-7 0:21:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 4

Hello,

Please can you verify that you have performed the following:

1. Edit /etc/default/init settings, modify the locale value to:

"en_US.ISO8859-1"

2. Reboot your system and check your modified locale was added in

your environment. Make sure that you are getting the locale

output as below :

# locale

LANG=en_US.ISO8859-1

LC_CTYPE=en_US.ISO8859-1

LC_NUMERIC=en_US.ISO8859-1

LC_TIME=en_US.ISO8859-1

LC_COLLATE=en_US.ISO8859-1

LC_MONETARY=en_US.ISO8859-1

LC_MESSAGES=C

LC_ALL=

3. After the completion of the above, try to do the Basic Registration.

4. Whether the registration attempt is successful or not please revert the "locale"

settings to what they were previously.

Regards,

ForumModerator at 2007-7-7 0:21:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 5

Thanks for the reply. My /etc/default/init contains only settings for TZ and CMASK, so I am not sure I am satisfying your request. Before changes, the locale command reports a value of C for the locale variables. I added

LANG=en_US.ISO8859-1

to the init file and after reboot the locale command reports this setting, but the LC_* variables are still set to C. Added the LC_*=en_US.ISO8859-1 assignments but after reboot they still report value of C. Reran "sconadm register -c", same error.

This is the error from the /var/cacao/instances/default/logs/cacao.0 log file:

Aug 18, 2006 8:50:24 AM com.sun.scn.offering.prom.AssetManagementServiceProvider registerAsset

INFO: calling ams.registerAsset .......

Aug 18, 2006 8:50:24 AM com.sun.scn.offering.prom.AssetManagementServiceProvider registerAsset

INFO: DEBUG: next call is ams.registerAsset

Aug 18, 2006 8:50:25 AM com.sun.scn.service.BaseServiceClient dumpThrowable

WARNING: XYXYXY

com.sun.scn.offering.service.ams.InternalResourceException: Internal DB Error. Error: com.sun.cc.platform.common.exception.IMException: com.sun.cc.ia.except

ion.ServiceException: net.sf.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update

at com.sun.scn.offering.service.ams.InternalResourceException_LiteralSerializer.do Deserialize(InternalResourceException_LiteralSerializer.java:56)

at com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalDeserializ e(LiteralObjectSerializerBase.java:216)

at com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.deserialize(Litera lObjectSerializerBase.java:124)

at com.sun.scn.offering.service.ams.AssetMgmtServiceIF_registerAsset_Fault_SOAPSer ializer.deserializeDetail(AssetMgmtServiceIF_registerAsset_Fault_SO

APSerializer.java:147)

at com.sun.xml.rpc.encoding.SOAPFaultInfoSerializer.doDeserialize(SOAPFaultInfoSer ializer.java:134)

at com.sun.xml.rpc.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase. java:192)

at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableS erializerImpl.java:155)

at com.sun.scn.offering.service.ams.AssetMgmtServiceIF_Stub._readBodyFaultElement( AssetMgmtServiceIF_Stub.java:480)

at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:208)

at com.sun.scn.offering.service.ams.AssetMgmtServiceIF_Stub.registerAsset(AssetMgm tServiceIF_Stub.java:197)

at com.sun.scn.offering.prom.AssetManagementServiceProvider.registerAsset(AssetMan agementServiceProvider.java:154)

at com.sun.scn.offering.swupom.SWUPOfferingInstance.register(SWUPOfferingInstance. java:500)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:4 14)

at javax.management.StandardMBean.invoke(StandardMBean.java:323)

at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213 )

at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServer Interceptor.java:815)

at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)

at com.sun.jdmk.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServe rInterceptor.java:203)

at com.sun.cacao.agent.DispatchInterceptor.invoke(DispatchInterceptor.java:662)

at com.sun.cacao.agent.auth.impl.AccessControlInterceptor.invoke(AccessControlInte rceptor.java:618)

at com.sun.jdmk.JdmkMBeanServerImpl.invoke(JdmkMBeanServerImpl.java:764)

at com.sun.cacao.common.instrum.impl.InstrumDefaultForwarder.invoke(InstrumDefault Forwarder.java:106)

at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.jav a:1408)

at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java :81)

at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnec tionImpl.java:1245)

at java.security.AccessController.doPrivileged(Native Method)

at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnecti onImpl.java:1348)

at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782 )

at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)

at sun.rmi.transport.Transport$1.run(Transport.java:153)

at java.security.AccessController.doPrivileged(Native Method)

at sun.rmi.transport.Transport.serviceCall(Transport.java:149)

at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)

at java.lang.Thread.run(Thread.java:595)

DRooks at 2007-7-7 0:21:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 6

Hello,

Please can you attempt the following:

1. Stop the cacao container by executing : cacaoadm stop

2. rm /var/scn/persistence/SCN*

3. /usr/lib/cc-cfw/framework/lib/cc-client-adm stop

4. /usr/lib/cc-cfw/framework/lib/cc-client-adm disable

5. /usr/lib/cc-ccr/bin/eraseCCRRepository

6. cacaoadm start

7. Attempt to register again

If this fails please can you run the following commands:

$ cat /etc/release

$ /usr/lib/cc-ccr/bin/ccr -g cns.assetid

$ smpatch get

$ smpatch analyze

$ pkginfo -l SUNWcacaort

$ pkginfo -l SUNWbreg

$ pkginfo -l SUNWdc

$ pkginfo -l SUNWbrg

$ pkginfo -l SUNWbrgr

$ cacaoadm status

$ cacaoadm list-modules

$ showrev -p | grep update

And forward the output to the following address "rsc-forum-inbound@Sun.COM".

Regards,

ForumModerator at 2007-7-7 0:21:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 7
I performed these steps on both machines mentioned above, no change.I have emailed the requested info on one of the machines (x86) to the address you gave. I hope to hear back from you soon. Thx.
DRooks at 2007-7-7 0:21:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 8
Got a solution back via email - my sunsolve account name was mixed case, the bug is that only lowercase works! For goodness' sake, please put a warning in the registration wizard and a decent error message!Thanks and may God bless.
DRooks at 2007-7-7 0:21:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 9

So, in conclusion, the fix is to have a Sunsolve ID that only contains lowercase characters? I've just installed Solaris 10 x86 06/06 on an X4100 and I'm having this exact problem. If this is the resolution, what am I supposed to do? Create a new Sunsolve ID? If I put my actual Sunsolve ID in lowercase, I get an error that it doesn't exist.

Iain

UWEBristol at 2007-7-7 0:21:20 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 10
Correct, create a lower case SunSolve account if this error occurs. This appears to be due to bug 6439845.
ForumModerator at 2007-7-7 0:21:21 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 11
Ran into this SWUP/Cacao problem as well. Only change I made was to /etc/default/init and changed TZ=Europe/Berin to TZ=US/Pacific.Had to back up a few pages in the GUI back to the sunlogin screen... and contunued on. It took the registration fine then.
Mister_Snufkin at 2007-7-7 0:21:21 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 12

I had the same problem and found this thread.

Based on the information here I guessed it was something to do with time. The time on my Sun station was 30 minutes behind real time. The time zone was correct.

I enabled ntp client, updated the time, and Sun Update Connection then performed without error. Hope this helps someone.

rogercrawford at 2007-7-7 0:21:21 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 13

Regarding choosing an appropriate SunSolve id:

A few years ago we used a 2-letter SunSolve id (both letters in uppercase) with a rather stupid/obvious password.

One day i logged in with the id in lowercase and reviewed the profile. It wasn't my account, but one belonging to a user in France...

Michael

MAALATFT at 2007-7-7 0:21:21 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 14
This issue has now been fixed.
RobG@Sun at 2007-7-7 0:21:21 > top of Java-index,Administration Tools,Sun Update Connection-System...