Solaris 10 registration fails - InvalidAssetException

This is our first Solaris 10 install - all of our other systems are Solaris 8.

Release is:

#cat /etc/release

Solaris 10 6/06 s10s_u2wos_09a SPARC

Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.

Use is subject to license terms.

Assembled 09 June 2006

The registration profile:userName=xxxxxxx

password=xxxxxx

hostName=

subscriptionkey=

portalEnabled=false

proxyHostName=

proxyPort=

proxyUserName=

proxyPassword=

CLI:

#sconadm register -a -r /tmp/RegistrationProfile

sconadm is running

Authenticating user ...

failed registration!

The log file ends with:

Aug 30, 2006 2:30:00 PM com.sun.cns.basicreg.cacao.SWUPOMCacaoAdapter setSWUPPortalEnabled

INFO: CALL SWUPOfferingInstanceMBean.setSWUPPortalEnableKey(): false

Aug 30, 2006 2:30:00 PM com.sun.cns.basicreg.cacao.SWUPOMCacaoAdapter getSWUPOfferingFactoryMBean

INFO:

SWUPOfferingFactory ObjectName =

com.sun.scn:Vendor=Sun Microsystems Inc,assetProfile=OperatingSystem,assetSubProfile=TODO,host=192.168.14.9,name=SW UPOfferingFactory,scnType=OfferingFactory

Aug 30, 2006 2:30:00 PM com.sun.cns.basicreg.cacao.SWUPOMCacaoAdapter setSystemDisplayName

INFO: CALL SWUPOfferingInstanceMBean.setSystemDisplayName():

Aug 30, 2006 2:30:00 PM com.sun.cns.basicreg.cacao.SWUPOMCacaoAdapter registerSystem

INFO: CALL SWUPOfferingInstanceMBean.register()

Aug 30, 2006 2:30:04 PM com.sun.cns.basicreg.cacao.SWUPOMCacaoAdapter registerSystem

SEVERE: Error: SWUPOM register() exception: Failed to register asset with AMS. Error message is :com.sun.scn.offering.prom.AssetRegistrationException: InvalidAssetExceptionAug 30, 2006 2:30:04 PM com.sun.cns.basicreg.cacao.SWUPOMCacaoAdapter registerSystem

SEVERE:

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

sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

java.security.AccessController.doPrivileged(Native Method)

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

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

sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

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

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

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

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

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

java.security.AccessController.doPrivileged(Native Method)

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

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

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

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

Aug 30, 2006 2:30:04 PM com.sun.cns.basicreg.cacao.SWUPOMCacaoAdapter getRegisterResult

INFO: SWUPOM Fault: Failed to register asset with AMS. Error message is :com.sun.scn.offering.prom.AssetRegistrationException: InvalidAssetException

Have tested contact/login using browser on this system to update.sun.com with no problems. There is no proxy in line.

Also attempted with GUI with no success. The log shows much more data gathering, but ends with the same InvalidAssetException error.

Based on other posts in this forum, tried this procedure:

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

It did not alter the results in any way.

Any ideas?

Message was edited by:

AmClassAdmin

[5593 byte] By [AmClassAdmin] at [2007-11-26 9:51:22]
# 1

Can you post the output of the following command

# psrinfo -v

Theres a bug open for registration failing when there is a processor in a FAULTED or SPARE state.

It the output from the command above shows this to be the case use one of the commands below to move it into another state then retry registration. (note that this issue has been fixed for the next release)

To move the CPU state from

FAULTED to ONLINE : /usr/sbin/psradm -F -n <proc-id>

FAULTED to OFFLINE : /usr/sbin/psradm -F -f <proc-id>

FAULTED to NOINTR : /usr/sbin/psradm -F -i <proc-id>

To move the CPU state from

SPARE to ONLINE : /usr/sbin/psradm -n <proc-id>

SPARE to OFFLINE : /usr/sbin/psradm -f <proc-id>

SPARE to NOINTR : /usr/sbin/psradm -i <proc-id>

ForumModerator at 2007-7-7 1:04:08 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 2

All CPUs are on-line.

#psrinfo -v

Status of virtual processor 0 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:13.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 1 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 4 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 5 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 6 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 7 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 8 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 9 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 10 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 11 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 12 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 13 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 14 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 15 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 16 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 17 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 18 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 19 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 20 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 21 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 22 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 23 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 24 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 25 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 26 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 27 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 28 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 29 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 30 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

Status of virtual processor 31 as of: 09/01/2006 08:55:50

on-line since 08/30/2006 14:16:17.

The sparcv9 processor operates at 400 MHz,

and has a sparcv9 floating point processor.

AmClassAdmin at 2007-7-7 1:04:08 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 3

Hi.

What sun.com login are you using for the username in your registration profile? Could you try creating a new sun.com account and using that instead - there were some issues recently with usernames with uppercase characters, so please try creating a username with all lower case characters.

Also, it is possible that this system was previously registered with Sun Update?

ForumModerator at 2007-7-7 1:04:08 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 4
Hello,My username/password is all lower case - I had spotted previous postings with that problem.The E6500 was purchased used. It may have been previously registered. Is there a way to check for this from my end?
AmClassAdmin at 2007-7-7 1:04:08 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 5
Hi again.Unfortunately, no, there's no way for you to check from your side.Do you have a Sun contract number you could raise a support case with?
ForumModerator at 2007-7-7 1:04:08 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 6
We are out of contract at this moment. We are hoping to have one in place by the end of this month (September).
AmClassAdmin at 2007-7-7 1:04:08 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 7
Any news on the fix for this topic? I am having the exact same problem!
JimCovington at 2007-7-7 1:04:08 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 8
Your contract support case ending in 6131 is a bit different as you have a proxy and a connection exception.
ForumModerator at 2007-7-7 1:04:08 > top of Java-index,Administration Tools,Sun Update Connection-System...