Tested with build20060919:
Steps:
1.Deployed CalendarClient and CalendarServer samples to local appserver and
remote AM server.
2.Switched to local AM server.
3. Deployed CalendarServer;it was failed, but the second time was successful.
4. Deployed CalendarClient; it was failed. Tried a few times, all were failed
with the following in output window:
init:
deps-module-jar:
deps-ear-jar:
deps-jar:
wscompile-init:
calendarService-client-wscompile:
web-service-client-generate:
library-inclusion-in-archive:
library-inclusion-in-manifest:
web-service-client-compile:
compile:
compile-jsps:
Building jar: C:\Documents and
Settings\HONG\CalendarClient3\CalendarClient3\dist\CalendarClient.war
do-dist:
dist:
C:\Documents and
Settings\HONG\CalendarClient3\CalendarClient3\nbproject\build-impl.xml:456:
Deployment error:
Wrong Admin user name or password.
See the server log for details.
BUILD FAILED (total time: 0 seconds)

See the attached server log file.

Created attachment 34339 [details]
appserver log file.

Buile 20a:
deploy after switching local AM to remote AM:
Deploying wsp provider CalendarService
ServerProperties: jsqai6 (jsqai6:8080)
com.iplanet.sso.SSOException:
AQIC5wM2LY4Sfcy0CHnL5a375ubhwvHwqyOgnm6RRTaKiDw=@AAJTSQACMDE=# Invalid session
ID.AQIC5wM2LY4Sfcy0CHnL5a375ubhwvHwqyOgnm6RRTaKiDw=@AAJTSQACMDE=#
        at
com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:178)
        at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:305)
        at
com.sun.identity.authentication.AuthContext.getSSOToken(AuthContext.java:1052)
        at
com.sun.identity.security.SystemAppTokenProvider.getAppSSOToken(SystemAppTokenProvider.java:104)
        at com.sun.identity.security.AdminTokenAction.run(AdminTokenAction.java:231)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.identity.wss.provider.ProviderConfig.getAdminToken(ProviderConfig.java:553)
        at
com.sun.identity.wss.provider.ProviderConfig.getProvider(ProviderConfig.java:447)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
org.netbeans.modules.identity.profile.api.configurator.impl.dynamic.ProviderConfigImpl.getProviderConfig(ProviderConfigImpl.java:159)
        at
org.netbeans.modules.identity.profile.api.configurator.impl.dynamic.ProviderConfigImpl.<init>(ProviderConfigImpl.java:138)
        at
org.netbeans.modules.identity.profile.api.configurator.ProviderConfigFactory.newInstance(ProviderConfigFactory.java:39)
        at
org.netbeans.modules.identity.profile.api.configurator.ProviderConfigurator.init(ProviderConfigurator.java:121)
        at
org.netbeans.modules.identity.profile.api.configurator.ProviderConfigurator.getConfigurator(ProviderConfigurator.java:93)
        at
org.netbeans.modules.identity.ant.AMDeploy.deployWSPProviders(AMDeploy.java:165)
        at org.netbeans.modules.identity.ant.AMDeploy.execute(AMDeploy.java:102)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at org.apache.tools.ant.Task.perform(Task.java:364)
        at org.apache.tools.ant.Target.execute(Target.java:341)
        at org.apache.tools.ant.Target.performTasks(Target.java:369)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
        at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
        at
org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:240)
        at
org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:293)
        at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:131)
SERVICE_TYPE: urn:CalendarService
trustAuthConfig = com.sun.identity.wss.provider.plugins.DiscoveryAgent@c1609b
Registering provider with Discovery Service
run-deploy:
BUILD SUCCESSFUL (total time: 11 seconds)

Change back to its original and lower it to its original priority. The
deployment failure problem will be filed as another defect.

This is a harmless error msg which doesnt prevent the eployment to go through.
The amserver keeps the session for the clientkSDK and tried to refreshes the
session everytime we call the ProviderConfig APIs. Its unable to refresh the
session and hence creates a new one for this to proceed. This exception is a
runtimeexception thrown from the AM server which should be handled on their side
because this is harmless anyway. I am filing a bugster issue 6474369 to track
this on accessmanager runtime. Closing the one in the IDE.