Authentication denied: Boot identity not valid for Managed Server

Weblogic 8.1 SP4. Solaris 2.8.
Initially, I only had the admin server in my domain. My application was targetted to the admin. Eventually, I created a new managed server so that my application would be targetted here and my admin server would just be dedicated to its admin tasks. I tried starting my managed server for the first time using the standard startManagedWeblogic.sh -
I get this:
####<Aug 22, 2005 12:38:37 PM EDT> <Critical> <Security> <md3801> <winsManagedServer> <main> <<WLS Kernel>>
<> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity
file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was create
d. Please edit and update the boot identity file with the proper values of username and password. The first time the
updated boot identity file is used to start the server, these new values are encrypted.>
bash-2.03$
Starting the admin server is fine and it uses the same boot.properties file in my root directory (user weblogic). But when I start my managed server instance (which is in the same root directory), it complains about the boot.properties ! I assume it uses the same boot.properties file. Any insights ? Thanks.

Hi,
You should know the right username and password, so you have to edit boot.properties by hand.
Remove user and password entry and re-insert them.
Regards,
Antenore.
Antenore Gatta
Middleware Specialist
Hequa S.r.l
C.so Buenos Aires 77
20124 Milano
http://www.Hequa.it
Tel +39(0)267493078
Fax +39(0)267493079
Mobile +39 3481537897
______________________________________

Similar Messages

Weblogic 10.2 :Authentication denied: Boot identity not valid

Weblogic 10.2 ,Windows xp prof
I have only one admin server (portal domain) and my application is targetted to admin server only. When I am startting my server the server is stopped forcedly with following exception.
If any have same kind of problem and solved it. please share the solutioin or reason for this :
<May 9, 2008 9:48:19 AM CEST> <Info> <WebLogicServer> <BEA-000215> <Loaded License : Y:\bea\license.bea>
<May 9, 2008 9:48:19 AM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<May 9, 2008 9:48:19 AM CEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<May 9, 2008 9:48:20 AM CEST> <Notice> <Log Management> <BEA-170019> <The server log file Y:\bea\user_projects\doma
ins\merlinAJAX_domain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be writte
n to this file.>
<May 9, 2008 9:48:23 AM CEST> <Error> <Security> <BEA-000000> <[Security:090737]An exception occurred while getting
connection to validate the configuration settings
java.sql.SQLException: [Security:090735]The DBMS connection was not usable
at weblogic.security.providers.authentication.DBMSSQLAuthenticatorDelegateImpl.getManageableConnection(DBMS
SQLAuthenticatorDelegateImpl.java:911)
at weblogic.security.providers.authentication.DBMSSQLAuthenticatorDelegateImpl.validateConfiguration(DBMSSQ
LAuthenticatorDelegateImpl.java:150)
at weblogic.security.providers.authentication.DBMSSQLAuthenticatorDelegateImpl.<init>(DBMSSQLAuthenticatorD
elegateImpl.java:76)
at weblogic.security.providers.authentication.DBMSAuthenticatorDelegateImpl.getInstance(DBMSAuthenticatorDe
legateImpl.java:452)
at weblogic.security.providers.authentication.DBMSSQLAuthenticationProviderImpl.initialize(DBMSSQLAuthentic
ationProviderImpl.java:42)
Truncated. see log file for complete stacktrace
>
<May 9, 2008 9:48:26 AM CEST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.
>
<May 9, 2008 9:48:26 AM CEST> <Error> <Security> <BEA-000000> <[Security:090735]The DBMS connection was not usable>
<May 9, 2008 9:48:26 AM CEST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; T
he user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have
been changed since the boot identity file was created. Please edit and update the boot identity file with the prop
er values of username and password. The first time the updated boot identity file is used to start the server, thes
e new values are encrypted.>
<May 9, 2008 9:48:26 AM CEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.s
ecurity.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or passw
ord from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the b
oot identity file was created. Please edit and update the boot identity file with the proper values of username and
password. The first time the updated boot identity file is used to start the server, these new values are encrypte
d.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name an
d/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed s
ince the boot identity file was created. Please edit and update the boot identity file with the proper values of us
ername and password. The first time the updated boot identity file is used to start the server, these new values ar
e encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
>
<May 9, 2008 9:48:26 AM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<May 9, 2008 9:48:26 AM CEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shu
t itself down>
<May 9, 2008 9:48:26 AM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Stopping PointBase server...
PointBase server stopped.
Autonomy server stopped.
-Sreeram
Edited by sreeram.jonnalagadda at 05/09/2008 1:54 AM

It seems in my case I have a locked pointbase java process.
So I entered task manager and killed all running java process and MY domain started sucessfully.
Sreeram

Java.lang.SecurityException: Authentication denied: Boot identity not valid

Hi,
When I try to start up the WebLogic server by running a startup script
in the WebLogic server root directory, I am getting the following
error:
<Apr 23, 2003 1:15:11 PM EDT> <Critical> <WebLogicServer> <000364>
<Server failed during initialization.
Exception:java.lang.SecurityException: Authentication denied: Boot
identity not valid
java.lang.SecurityException: Authentication denied: Boot identity not
valid
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(SecurityServiceManager.java:1074)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1216)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
>
<Apr 23, 2003 1:15:11 PM EDT> <Emergency> <WebLogicServer> <000342>
<Unable to initialize the server: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication denied: Boot
identity not valid
java.lang.SecurityException: Authentication denied: Boot identity not
valid
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(SecurityServiceManager.java:1074)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1216)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.SecurityException: Authentication denied: Boot identity not
valid
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(SecurityServiceManager.java:1074)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1216)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
Reason: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication denied: Boot
identity not valid
java.lang.SecurityException: Authentication denied: Boot identity not
valid
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(SecurityServiceManager.java:1074)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1216)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
I am also pasting below the source code of the startup script that I
am using to start WebLogic server:
#!/bin/sh
# This script is used to start WebLogic Server.
# To create your own start script for your domain, simply set the
SERVER_NAME
# variable to your server name then call this script from your domain
# directory.
# This script sets the following variables before starting WebLogic
Server:
# WL_HOME - The root directory of your WebLogic installation
# JAVA_HOME - Location of the version of Java used to start
WebLogic
# Server. This variable must point to the root
directory of a
# JDK installation and will be set for you by the
installer.
# See the WebLogic platform support page
# (http://e-docs.bea.com/wls/platforms/index.html)
for an up-to-date list of
# supported JVMs on your platform.
# PATH - Adds the JDK and WebLogic directories to the system
path.
# CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
# JAVA_OPTIONS - Java command-line options for running the server.
# Other variables that startWLS takes are:
# ADMIN_URL - If this variable is set, the server started will be
a
# managed server, and will look to the url specified
(i.e.
# http://localhost:7001) as the admin server.
# WLS_USER - Admin username for server startup
# WLS_PW - Cleartext password for server startup
# STARTMODE - Set to true for production mode servers, false for
# development mode
# JAVA_OPTIONS - Java command-line options for running the server.
(These
# will be tagged on to the end of the JAVA_VM and
MEM_ARGS)
# JAVA_VM - The java arg specifying the VM to run. (i.e.
-server,
# -hotspot, etc.)
# MEM_ARGS - The variable to override the standard memory
arguments
# passed to java
# PRE_CLASSPATH - Path style variable to be added to the beginning of
the
# CLASSPATH
# POST_CLASSPATH - Path style variable to be added to the end of the
# CLASSPATH
# PRE_PATH - Path style variable to be added to the beginning of
the
# PATH
# POST_PATH - Path style variable to be added to the end of the
PATH
# Alternately, this script will take the first two positional
parameters and
# set them to SERVER_NAME and ADMIN_URL. For instance, you could call
this
# script: "sh startWLS.sh myserver http://localhost:7001" to start a
# managed server named myserver, or just "sh startWLS.sh myserver"
# to start a server named myserver.
# jDriver for Oracle users: This script assumes that native libraries
required
# for jDriver for Oracle have been installed in the proper location
and that
# your os specific library path variable (i.e.
LD_LIBRARY_PATH/solaris,
# SHLIB_PATH/hpux, etc...) has been set appropriately. Also note that
this
# script defaults to the oci817_8 version of the shared libraries. If
this is
# not the version you need, please adjust the library path variable
# accordingly.
# For additional information, refer to the WebLogic Server
Administration Guide
# (http://e-docs.bea.com/wls/docs70/adminguide/startstop.html).
WL_HOME="/usr/local/bea/weblogic700"
JAVA_HOME="/usr/local/bea/jdk131_06"
. ${WL_HOME}/common/bin/commEnv.sh
# Check that the WebLogic classes are where we expect them to be
if [ ! -f "${WL_HOME}/server/lib/weblogic.jar" ]; then
echo
echo "The WebLogic Server wasn't found in directory
${WL_HOME}/server."
echo "Please edit your script so that the WL_HOME variable points"
echo "to the WebLogic installation directory."
# Check that java is where we expect it to be
elif [ ! -d "${JAVA_HOME}/bin" ]; then
echo
echo "The JDK wasn't found in directory ${JAVA_HOME}."
echo "Please edit your script so that the JAVA_HOME variable"
echo "points to the location of your JDK."
else
# Grab some file descriptors.
if [ ! -n "`uname -s |grep -i cygwin || uname -s |grep -i windows_nt`"
]; then
maxfiles=`ulimit -H -n`
if [ !$? -a "${maxfiles}" != 1024 ]; then
if [ "${maxfiles}" = "unlimited" ]; then
maxfiles=1025
fi
if [ "${maxfiles}" -lt 1024 ]; then
ulimit -n ${maxfiles}
else
ulimit -n 1024
fi
fi
fi
# Set first two positional parameters to SERVER_NAME and ADMIN_URL
if [ -n "${1}" -a "${SERVER_NAME}" = "" ]; then
SERVER_NAME="${1}"
fi
if [ -n "${2}" -a "${ADMIN_URL}" = "" ]; then
ADMIN_URL="${2}"
fi
# Figure out how to use our shared libraries
case `uname -s` in
AIX)
if [ -n "${LIBPATH}" ]; then
LIBPATH="${LIBPATH}:${WL_HOME}/server/lib/aix:${WL_HOME}/server/lib/aix/oci817_8"
else
LIBPATH="${WL_HOME}/server/lib/aix:${WL_HOME}/server/lib/aix/oci817_8"
fi
PATH="${WL_HOME}/server/lib/aix:${PATH}"
export LIBPATH PATH
export AIXTHREAD_SCOPE=S
export AIXTHREAD_MUTEX_DEBUG=OFF
export AIXTHREAD_RWLOCK_DEBUG=OFF
export AIXTHREAD_COND_DEBUG=OFF
echo "LIBPATH=${LIBPATH}"
HP-UX)
if [ -n "${SHLIB_PATH}" ]; then
SHLIB_PATH="${SHLIB_PATH}:${WL_HOME}/server/lib/hpux11:${WL_HOME}/server/lib/hpux11/oci817_8"
else
SHLIB_PATH="${WL_HOME}/server/lib/hpux11:${WL_HOME}/server/lib/hpux11/oci817_8"
fi
PATH="${WL_HOME}/server/lib/hpux11:${PATH}"
export SHLIB_PATH PATH
echo "SHLIB_PATH=${SHLIB_PATH}"
IRIX)
if [ -n "${LD_LIBRARY_PATH}" ]; then
LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:${WL_HOME}/server/lib/irix"
else
LD_LIBRARY_PATH="${WL_HOME}/server/lib/irix"
fi
PATH="${WL_HOME}/server/lib/irix:${PATH}"
export LD_LIBRARY_PATH PATH
echo "LD_LIBRARY_PATH=${LD_LIBRARY_PATH}"
LINUX|Linux)
arch=`uname -m`
if [ -n "${LD_LIBRARY_PATH}" ]; then
LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:${WL_HOME}/server/lib/linux/${arch}:${WL_HOME}/server/lib/linux/${arch}/oci817_8"
else
LD_LIBRARY_PATH="${WL_HOME}/server/lib/linux/${arch}:${WL_HOME}/server/lib/linux/${arch}/oci817_8"
fi
PATH="${WL_HOME}/server/lib/linux:${PATH}"
export LD_LIBRARY_PATH PATH
echo "LD_LIBRARY_PATH=${LD_LIBRARY_PATH}"
OSF1)
if [ -n "${LD_LIBRARY_PATH}" ]; then
LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:${WL_HOME}/server/lib/tru64unix"
else
LD_LIBRARY_PATH="${WL_HOME}/server/lib/tru64unix"
fi
PATH="${WL_HOME}/server/lib/tru64unix:${PATH}"
export LD_LIBRARY_PATH PATH
echo "LD_LIBRARY_PATH=${LD_LIBRARY_PATH}"
SunOS)
if [ -n "${LD_LIBRARY_PATH}" ]; then
LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:${WL_HOME}/server/lib/solaris:${WL_HOME}/server/lib/solaris/oci817_8"
else
LD_LIBRARY_PATH="${WL_HOME}/server/lib/solaris:${WL_HOME}/server/lib/solaris/oci817_8"
fi
PATH="${WL_HOME}/server/lib/solaris:${PATH}"
export LD_LIBRARY_PATH PATH
echo "LD_LIBRARY_PATH=${LD_LIBRARY_PATH}"
if [ "${JAVA_VM}" = "" ]
then
# JAVA_VM=-server
JAVA_VM=${COMM_SERVER_VM}
fi
Windows_NT*)
if [ "${JAVA_VM}" = "" ]
then
# JAVA_VM=-hotspot
JAVA_VM=${COMM_VM}
fi
PATHSEP=\;
CLASSPATHSEP=\;
CYGWIN*)
if [ "${JAVA_VM}" = "" ]
then
# JAVA_VM=-hotspot
JAVA_VM=${COMM_VM}
fi
CLASSPATHSEP=\;
echo "$0: Don't know how to set the shared library path for `uname
-s`. "
esac
if [ "${MEM_ARGS}" = "" ]
then
MEM_ARGS="-Xms32m -Xmx200m"
fi
if [ "${PATHSEP}" = "" ]; then
PATHSEP=:
fi
if [ "${CLASSPATHSEP}" = "" ]; then
CLASSPATHSEP=:
fi
CLASSPATH="${JAVA_HOME}/lib/tools.jar${CLASSPATHSEP}${WL_HOME}/server${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic_sp.jar${CLASSPATHSEP}${WL_H
OME}/server/lib/weblogic.jar${CLASSPATHSEP}${CLASSPATH}"
# If we are on an old version of Cygnus we need to turn <letter>:/ in
the path
# to //<letter>/
if [ `uname -s` = "CYGWIN32/NT" ]; then
WL_HOME=`echo $WL_HOME | sed "s#$[a-zA-Z]$:#//\1#g"`
JAVA_HOME=`echo $JAVA_HOME | sed "s#$[a-zA-Z]$:#//\1#g"`
fi
# If we are on an new version of Cygnus we need to turn <letter>:/ in
the path
# to /cygdrive/<letter>/
if [ -n "`uname -s |grep -i cygwin_`" ]; then
WL_HOME=`echo $WL_HOME | sed "s#$[a-zA-Z]$:#/cygdrive/\1#g"`
JAVA_HOME=`echo $JAVA_HOME | sed "s#$[a-zA-Z]$:#/cygdrive/\1#g"`
fi
PATH=".${PATHSEP}${WL_HOME}/server/bin${PATHSEP}${JAVA_HOME}/jre/bin${PATHSEP}${JAVA_HOME}/bin${PATHSEP}${PATH}"
# Import extended environment
if [ -f extEnv.sh ]; then
. extEnv.sh
fi
if [ ! -z "${EXT_PRE_CLASSPATH}" ]; then
CLASSPATH="${EXT_PRE_CLASSPATH}${CLASSPATHSEP}${CLASSPATH}"
fi
if [ ! -z "${EXT_POST_CLASSPATH}" ]; then
CLASSPATH="${CLASSPATH}${CLASSPATHSEP}${EXT_POST_CLASSPATH}"
fi
if [ ! -z "${EXT_PRE_PATH}" ]; then
PATH="${EXT_PRE_PATH}${PATHSEP}${PATH}"
fi
if [ ! -z "${EXT_POST_PATH}" ]; then
PATH="${PATH}${PATHSEP}${EXT_POST_PATH}"
fi
# Get PRE and POST environment
if [ ! -z "${PRE_CLASSPATH}" ]; then
CLASSPATH="${PRE_CLASSPATH}${CLASSPATHSEP}${CLASSPATH}"
fi
if [ ! -z "${POST_CLASSPATH}" ]; then
CLASSPATH="${CLASSPATH}${CLASSPATHSEP}${POST_CLASSPATH}"
fi
if [ ! -z "${PRE_PATH}" ]; then
PATH="${PRE_PATH}${PATHSEP}${PATH}"
fi
if [ ! -z "${POST_PATH}" ]; then
PATH="${PATH}${PATHSEP}${POST_PATH}"
fi
echo CLASSPATH=${CLASSPATH}
echo
echo PATH=${PATH}
echo
echo "***************************************************"
echo "* To start WebLogic Server, use a username and *"
echo "* password assigned to an admin-level user. For *"
echo "* server administration, use the WebLogic Server *"
echo "* console at http://<hostname>:<port>/console *"
echo "***************************************************"
if [ "$ADMIN_URL" != "" ]
then
set -x
"${JAVA_HOME}/bin/java" ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS}
-classpath "${CLASSPATH}" -Dweblogic.Name=${SERVER_NAME}
-Dbea.home="/usr/local
/bea" -Dweblogic.management.username=${WLS_USER}
-Dweblogic.management.password=${WLS_PW}
-Dweblogic.management.server=${ADMIN_URL} -Dweblogic
.ProductionModeEnabled=${STARTMODE}
-Djava.security.policy="${WL_HOME}/server/lib/weblogic.policy"
weblogic.Server
else
set -x
"${JAVA_HOME}/bin/java" ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS}
-classpath "${CLASSPATH}" -Dweblogic.Name=${SERVER_NAME}
-Dbea.home="/usr/local
/bea" -Dweblogic.management.username=${WLS_USER}
-Dweblogic.management.password=${WLS_PW}
-Dweblogic.ProductionModeEnabled=${STARTMODE} -Djava
.security.policy="${WL_HOME}/server/lib/weblogic.policy"
weblogic.Server
fi
set +x
fi
--------------END OF SCRIPT----------
So can you please look at the exception and the above-pasted source
code of the startup script file and let me know what needs to be done
to fix the error?
Thanks,
Kalpana

Senthil,
What may have happened is that the boot identity (e.g., the "weblogic" user) is no longer in the realm. Or, you added a second authenticator which has a Control Flag of Required but the weblogic user cannot be found there.
If it's the first scenario, add the weblogic user (and his inclusion in the Administrators group) to the data store for your authenticator.
If it's the second scenario, you need to change the Control Flag to something less drastic such as Sufficient. In this case, you can't make the change in WebLogic Console since you can't boot your server. Have a look in config.xml and see if your newly created authenticator is listed there. If it is, change the Control Flag and try to reboot the server.
Otherwise, copy config.xml.booted to config.xml and start your server. You'll have to re-do your security realm changes, though.
HTH,
Mike

Authentication denied: Boot identity not valid

Hi,
After ADF Security Configuration, I am getting following error while running jspx pages:
<Jun 25, 2010 11:34:51 AM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jun 25, 2010 11:34:51 AM IST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
(Purposefully not putting entire run log to avoid cluttering. Can provide if needed.)
Please note that before ADF Security Configuration, I was able to run my jspx pages.
I have condifured ADF security as follows:
'ADF Authentication and Authorization' model
Form-based authentication with default login and error pages
No Automatic Grants
Redirect upon successful authentication - one of my jspx page (which was rendering fine before ADF Security Config)
Also is it possible to temporarily disable ADF security?
Where is the boot.properties located?
Thanks in advance

This error usually occurs on Weblogic server when identity store is changed. Basically the default admin user name password which is used by weblogic when u start with startWeblogic.cmd does not work.
so this is definitely not an issue of ADF Security.
You can remove ADF security from your application from the same menu which you created ADF security. Third option removed all security configuration. Before that you may want to copy your jazn-data.xml and keep it for backup.
boot.properties is to be created in domain\servers\AdminServer\security if present just edit it and
password=
username=
When you run the server it will encrypt the contents.
But as i see it is not an issue with ADF security and unless you have changed something in weblogic console realm providers not an issue with weblogic also.
Easy solution is to clode Jdev and delete defaultdomain in : C:\Documents and Settings\user\Application Data\JDeveloper\system11.1.1.2.36.55.36 and satrt Jdeveloper. Your domain will be automatically created.
Venkat

Boot identity not valid.

Hi, when im trying to start one of my managed servers im getrting the error boot identity not valid.
We tried to create the boot.properties with current admin passoerd and user name. Still server is not coming up.
Few weeks before we configured the node manager for the machine. We got this error when we are trying to start through startMangedweblogic.sh. as we are no longer using nodemanager for this domain.
Plz sort out the issue.. Please refore the error log generarting
<Apr 26, 2012 11:34:20 AM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Apr 26, 2012 11:34:20 AM BST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Apr 26, 2012 11:34:21 AM BST> <Notice> <Log Management> <BEA-170019> <The server log file /var/flarea/soalogs/node1/server/bpmsq_bam_ms1/logs/bpmsq_bam_ms1.log is opened. All server side log events will be written to this file.>
<Apr 26, 2012 11:34:25 AM BST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Apr 26, 2012 11:34:25 AM BST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
<Apr 26, 2012 11:34:25 AM BST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:959)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:244)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Truncated. see log file for complete stacktrace
>
<Apr 26, 2012 11:34:25 AM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Apr 26, 2012 11:34:25 AM BST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Apr 26, 2012 11:34:25 AM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Hi,
1: remove the boot.properties file completely from the managed server directory.
2: remove the ManagedServerDir/data/ldap directory completely.
3: Always keep backup of files before removing it.
4: Now try to start the server from the command prompt and provide the username/password used to login to the Admin Console.
Regards,
Fabian

Weblogic Server not starting up: Boot identity not valid

Hi All,
I am trying to start the weblogic server and the following error appears:
####<May 28, 2010 12:05:53 PM IST> <Notice> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275028553504> <BEA-090082> <Security initializing using security realm myrealm.>
####<May 28, 2010 12:05:53 PM IST> <Critical> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275028553535> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
####<May 28, 2010 12:05:53 PM IST> <Critical> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553535> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:959)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
     at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:243)
     at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
     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:597)
     at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
     at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
     at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
     at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
     at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
     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:597)
     at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
     at $Proxy16.login(Unknown Source)
     at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:91)
     at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
     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:597)
     at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
     at $Proxy34.authenticate(Unknown Source)
     at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
     at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:347)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<May 28, 2010 12:05:53 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553567> <BEA-000365> <Server state changed to FAILED>
####<May 28, 2010 12:05:53 PM IST> <Error> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553567> <BEA-000383> <A critical service failed. The server will shut itself down>
####<May 28, 2010 12:05:53 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553567> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<May 28, 2010 12:05:53 PM IST> <Info> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553582> <BEA-000236> <Stopping execute threads.>
Kindly help me regarding
Thanks in advance

Just to add some more details here which will help in diagnosing the problem. I deleted the boot.properties file and the command prompt asked me for the username and password. I provided the correct details but still the server could not start up. Here are the details from the log file:
####<May 28, 2010 12:45:47 PM IST> <Notice> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275030947053> <BEA-090082> <Security initializing using security realm myrealm.>
####<May 28, 2010 12:45:47 PM IST> <Critical> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275030947084> <BEA-090403> <Authentication for user weblogic denied>
####<May 28, 2010 12:45:47 PM IST> <Critical> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947084> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
     at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:243)
     at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
     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:597)
     at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
     at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
     at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
     at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
     at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
     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:597)
     at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
     at $Proxy16.login(Unknown Source)
     at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:91)
     at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
     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:597)
     at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
     at $Proxy34.authenticate(Unknown Source)
     at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
     at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:347)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<May 28, 2010 12:45:47 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947116> <BEA-000365> <Server state changed to FAILED>
####<May 28, 2010 12:45:47 PM IST> <Error> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947116> <BEA-000383> <A critical service failed. The server will shut itself down>
####<May 28, 2010 12:45:47 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947116> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<May 28, 2010 12:45:47 PM IST> <Info> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947131> <BEA-000236> <Stopping execute threads.>

The login information is not valid for this server

Hello,
i've recently setup open directory for 30 MAC running 10.5 and 10.6
it works sort of fine.
having a few errors with mobility though that's for another thread.
My prob, is that the first time ive set OD, the next day while logging into WGM i had an error and couldnt login with directory administrator username.
i've trieed the following to resolve it:
tried reseting password according to an apple support document
disabled SSL(advice on some none apple forum)
rebooted the server
tried logging in localy from the server itself
checked tht LDAP autehtnication is the first to be checked while authenticaing with the server.
None of the above worked, where i had to wipe my OD, by choosing standalone from the server admin, and then doing it all over again.
today and for the second time i had the same issue.
i've managed to take screenshots of the errors i'm recieving. you can find them attached.
the below errors are ones which appeared while i had my WGM already authenticated and tried to work on it:
i appreciate any help with this matter.
Thanks,

To be sure, the server field says your server "name"
you are tying to log in as diradmin
and you are using your password from when you set up the server? This password is also the same local admin password that you setup.

Weblogic(BEA 09042): Authentication denied. Boot properties not valid error

Dear All,
I am getting the following Weblogic error while trying to start the application.
Web logic server is working fine independently and was able to create domains. But when the application was trying to invoke web logic, security encrytion issues are encountered in boot.properties file.
Please provide some ideas or suggestions on how to handle such kind of errors with the log details provided below., Thanks
starting weblogic with Java version:
java version "1.5.0_21"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_21-b01)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_21-b01, mixed mode)
"Starting Weblogic with the following arguments"
C:\Java\JDK15~1.0_2\bin\java -server -Xms1024m -Xmx1024m -XX:PermSize=300m -d
a -Dplatform.home=C:\bea\WLSERV~1.0 -Dwls.home=C:\bea\WLSERV~1.0\myserver -Dwli.
home=C:\bea\WLSERV~1.0\integration -Dweblogic.management.discover=true -Dwlw.i
terativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:
\bea\patch_wss110\profiles\default\sysext_manifest_classpath;C:\bea\patch_wlw102
1\profiles\default\sysext_manifest_classpath;C:\bea\patch_wls1002\profiles\defau
lt\sysext_manifest_classpath;C:\bea\patch_cie640\profiles\default\sysext_manifes
t_classpath -Dweblogic.management.username=weblogic -Dweblogic.Name=myserver -Dj
ava.security.policy=C:\bea\WLSERV~1.0\server\lib\weblogic.policy weblogic.Serve
r
<Feb 8, 2011 3:13:09 AM PST> <Notice> <WebLogicServer> <BEA-000395> <Following e
xtensions directory contents added to the end of the classpath:
C:\bea\wlserver_10.0\platform\lib\p13n\p13n-schemas.jar;C:\bea\wlserver_10.0\pla
tform\lib\p13n\p13n_common.jar;C:\bea\wlserver_10.0\platform\lib\p13n\p13n_syste
m.jar;C:\bea\wlserver_10.0\platform\lib\p13n\wlp_services.jar;C:\bea\wlserver_10
.0\platform\lib\wlp\netuix_common.jar;C:\bea\wlserver_10.0\platform\lib\wlp\netu
ix_schemas.jar;C:\bea\wlserver_10.0\platform\lib\wlp\netuix_system.jar;C:\bea\wl
server_10.0\platform\lib\wlp\wsrp-client.jar;C:\bea\wlserver_10.0\platform\lib\w
lp\wsrp-common.jar>
<Feb 8, 2011 3:13:10 AM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebL
ogic Server with Java HotSpot(TM) 64-Bit Server VM Version 1.5.0_21-b01 from Sun
Microsystems Inc.>
<Feb 8, 2011 3:13:11 AM PST> <Info> <Management> <BEA-141107> <Version: WebLogic
Server 10.0 MP2 Sat Apr 25 01:45:38 EDT 2009 1213942 >
<Feb 8, 2011 3:13:13 AM PST> <Info> <WebLogicServer> <BEA-000215> <Loaded Licens
e : C:\bea\license.bea>
<Feb 8, 2011 3:13:13 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to STARTING>
<Feb 8, 2011 3:13:13 AM PST> <Info> <WorkManager> <BEA-002900> <Initializing sel
f-tuning thread pool>
<Feb 8, 2011 3:13:14 AM PST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\SPL\CCBWLS\logs\system\myserver.log is opened. All server side log e
vents will be written to this file.>
<Feb 8, 2011 3:13:18 AM PST> <Notice> <Security> <BEA-090082> <Security initiali
zing using security realm myrealm.>
<Feb 8, 2011 3:13:18 AM PST> <Critical> <Security> <BEA-090402> <Authentication
denied: Boot identity not valid; The user name and/or password from the boot ide
ntity file (boot.properties) is not valid. The boot identity may have been chang
ed since the boot identity file was created. Please edit and update the boot ide
ntity file with the proper values of username and password. The first time the u
pdated boot identity file is used to start the server, these new values are encr
ypted.>
<Feb 8, 2011 3:13:18 AM PST> <Critical> <WebLogicServer> <BEA-000386> <Server su
bsystem failed. Reason: weblogic.security.SecurityInitializationException: Authe
ntication denied: Boot identity not valid; The user name and/or password from th
e boot identity file (boot.properties) is not valid. The boot identity may have
been changed since the boot identity file was created. Please edit and update th
e boot identity file with the proper values of username and password. The first
time the updated boot identity file is used to start the server, these new value
s are encrypted.
<Feb 8, 2011 3:13:18 AM PST> <Critical> <WebLogicServer> <BEA-000386> <Server su
bsystem failed. Reason: weblogic.security.SecurityInitializationException: Authe
ntication denied: Boot identity not valid; The user name and/or password from th
e boot identity file (boot.properties) is not valid. The boot identity may have
been changed since the boot identity file was created. Please edit and update th
e boot identity file with the proper values of username and password. The first
time the updated boot identity file is used to start the server, these new value
s are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot i
dentity not valid; The user name and/or password from the boot identity file (bo
ot.properties) is not valid. The boot identity may have been changed since the b
oot identity file was created. Please edit and update the boot identity file wit
h the proper values of username and password. The first time the updated boot id
entity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do
BootAuthorization(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itialize(Unknown Source)
at weblogic.security.service.SecurityServiceManager.initialize(Unknown S
ource)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
>
<Feb 8, 2011 3:13:18 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to FAILED>
<Feb 8, 2011 3:13:18 AM PST> <Error> <WebLogicServer> <BEA-000383> <A critical s
ervice failed. The server will shut itself down>
<Feb 8, 2011 3:13:18 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to FORCE_SHUTTING_DOWN>
Stopping PointBase server...
PointBase server stopped.
You can close this window
Regards,
Sam.

Hi Baji, P-H,
Sorry for the delay. The ideas were useful and helped me a lot but i currently face the follwoing initialization of VM and object heap error.
Please adive and provide suggestion on the following issue. The logs are pasted below, Thanks,
JAVA Memory arguments: -Xms1024m -Xmx1024m -XX:PermSize=300m
WLS Start Mode=Development
CLASSPATH=C:\bea\WLSERV~1.0\samples\server\examples\build\serverclasses;C:\bea\p
atch_wss110\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\pa
tch_wlw1021\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\pa
tch_wls1002\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\pa
tch_cie640\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Java\JD
K15~1.0_2\lib\tools.jar;C:\bea\WLSERV~1.0\server\lib\weblogic_sp.jar;C:\bea\WLSE
RV~1.0\server\lib\weblogic.jar;C:\bea\modules\features\weblogic.server.modules_1
0.0.2.0.jar;C:\bea\modules\features\com.bea.cie.common-plugin.launch_2.1.2.0.jar
;C:\bea\WLSERV~1.0\server\lib\webservices.jar;C:\bea\modules\ORGAPA~1.5/lib/ant-
all.jar;C:\bea\modules\NETSFA~1.0/lib/ant-contrib.jar;;C:\bea\WLSERV~1.0\common\
eval\pointbase\lib\pbembedded51.jar;C:\bea\WLSERV~1.0\common\eval\pointbase\lib\
pbupgrade51.jar;C:\bea\WLSERV~1.0\common\eval\pointbase\lib\pbclient51.jar;C:\be
a\WLSERV~1.0\server\lib\xqrl.jar;;;C:\Spl\ccbwls\splapp\standalone\lib\xalan-2.7
.0.jar;C:\Spl\ccbwls\splapp\standalone\lib\serializer-2.7.0.jar;C:\Spl\ccbwls\sp
lapp\standalone\lib\antlr-2.7.6.jar
PATH=C:\bea\patch_wss110\profiles\default\native;C:\bea\patch_wlw1021\profiles\d
efault\native;C:\bea\patch_wls1002\profiles\default\native;C:\bea\patch_cie640\p
rofiles\default\native;C:\bea\WLSERV~1.0\server\native\win\x64;C:\bea\WLSERV~1.0
\server\bin;C:\bea\modules\ORGAPA~1.5\bin;C:\Java\JDK15~1.0_2\jre\bin;C:\Java\JD
K15~1.0_2\bin;C:\MICROF~1\SERVER~1.1\bin;C:\spl\ccbwls\runtime;C:\Java\jdk1.5.0_
21\bin;C:\spl\ccbwls\runtime;C:\spl\ccbwls\bin;C:\spl\ccbwls\product\apache-ant-
1.7.0\bin;C:\app\Administrator\product\11.2.0\dbhome_1;C:\app\Administrator\prod
uct\11.2.0\dbhome_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;
C:\Windows\System32\WindowsPowerShell\v1.0\;C:\app\Administrator\product\11.2.0\
dbhome_1\perl\bin;C:\Java\jdk1.5.0_21\bin;C:\Java\jdk1.5.0_21\lib;C:\Java\JRocki
t Real Time\jrrt-3.1.2-1.5.0\bin;C:\bea\WLSERV~1.0\server\native\win\x64\oci920_
8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.5.0_21"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_21-b01)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_21-b01, mixed mode)
"Starting Weblogic with the following arguments"
C:\Java\JDK15~1.0_2\bin\java -server -Xms1024m -Xmx1024m -XX:PermSize=300m -d
a -Dplatform.home=C:\bea\WLSERV~1.0 -Dwls.home=C:\bea\WLSERV~1.0\myserver -Dwli.
home=C:\bea\WLSERV~1.0\integration -Dweblogic.management.discover=true -Dwlw.i
terativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:
\bea\patch_wss110\profiles\default\sysext_manifest_classpath;C:\bea\patch_wlw102
1\profiles\default\sysext_manifest_classpath;C:\bea\patch_wls1002\profiles\defau
lt\sysext_manifest_classpath;C:\bea\patch_cie640\profiles\default\sysext_manifes
t_classpath -Dweblogic.management.username=weblogic -Dweblogic.Name=myserver -Dj
ava.security.policy=C:\bea\WLSERV~1.0\server\lib\weblogic.policy weblogic.Serve
r
Error occurred during initialization of VM
Could not reserve enough space for object heap
Stopping PointBase server...
PointBase server stopped.
Regards,
Sam.

Unable to create foreign key: InvalidArgument=Value of '0' is not valid for 'index'. Parameter name: index

I am running an SQL(CE) script to create a DB. All script commands succeed, but the DB get "broken" after creating the last costaint: after running the script, viewing table properties of Table2 and clicking on "Manage relations" gives the following error: Unable to create foreign key: InvalidArgument=Value of '0' is not valid for 'index'. Parameter name: index. Wondering what does that refer to...
Here it is the script. Please note that no error is thrown by running the following queries (even from code that passing the queries by hand, one-by-one to sql server management studio).
CREATE TABLE [table1] (
[id_rubrica] numeric(18,0) NOT NULL
, [id_campo] numeric(18,0) NOT NULL
, [nome] nvarchar(100) NOT NULL
GO
ALTER TABLE [table1] ADD PRIMARY KEY ([id_rubrica],[id_campo]);
GO
CREATE UNIQUE INDEX [UQ__m_campi] ON [table1] ([id_campo] Asc);
GO
CREATE TABLE [table2] (
[id_campo] numeric(18,0) NOT NULL
, [valore] nvarchar(4000) NOT NULL
GO
ALTER TABLE [table2] ADD PRIMARY KEY ([id_campo],[valore]);
GO
ALTER TABLE [table2] ADD CONSTRAINT [campo_valoriFissi] FOREIGN KEY ([id_campo]) REFERENCES [table1]([id_campo]);
GO
Sid (MCP - http://www.sugata.eu)

I know this is kind of old post, but did this realy solved your problem?
I'm getting this same error message after adding a FK constraint via UI on VS2008 Server Explorer.
I can add the constraint with no errors, but the constraint is not created on the DataSet wizard (strongly typed datasets on Win CE 6) and when I click "Manage Relations" on the "Table Properties" this error pop out:
"InvalidArgument=Value or '0' is not valid for 'index'.
Parameter name: index"
Even after vreating my table with the relation in SQL the same occurs:
CREATE TABLE pedidosRastreios (
    idPedidoRastreio INT NOT NULL IDENTITY PRIMARY KEY,
    idPedido INT NOT NULL CONSTRAINT FK_pedidosRastreios_pedidos REFERENCES pedidos(idPedido) ON DELETE CASCADE,
    codigo NVARCHAR(20) NOT NULL

Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state

we have developed packages to do the followings
Extract data from DB2 Source and put it in MS Sql Server 2008 database (Lets Say DatabaseA).From MS Sql Server 2008 (DatabaseA)
we will process the data and place it in another database MS Sql Server 2008 (DatabaseB)
We have created packages in BIDS..We created datasource connection in Datasource folder in BIDS..Which has DB2 Connection and both Ms Sql Server connection (Windows authentication-Let
say its pointing to the server -ServerA which has DatabaseA and DatabaseB).The datasource connections will be used in packages during development.
For deployment we have created Package Configuration which will have both DB2 Connection and MS SqlServer connection in the config
We deployed the packages in different MS SqlServer by changing the connectionstring in the config for DB2 and MS SqlServer...
While runing the package we are getting the following error message
Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for
use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.
ilikemicrosoft

Hi Surendiran,
This is because the package has been created by somebody else and the package is being deployed under sombody else's account. e.g. If you are the creator then the package is encryption set according to your account and the package setup in SQL server is
under a different user account.
This happens because the package protection level is set to EncryptSensitiveWithUserKey which encrypts
sensitive information using creator's account name.
As a solution:
Either you have to set up the package in SQL server under your account (which some infrastructures do not allow).
OR
Set the package property Protection Level to "DontSaveSensitive" and add a configuration file
to the package and set the initial values for all the variables and all the connection manager in that configuration file (which might be tedious of-course).
OR
The third options (which I like do) is to open the package file and delete the password encryption entries from the package. Do note that this is not supported by designer and every time you make changes to the connection managers these encryption entries come
back.
Hope this helps.
Please mark the post as answered if it answers your question

Site behind load balancer - Key not valid for use in specified state

Hi,
I have created a sharepoint application page to access an active end point on ADFS and establish a fedauth session. All works well in single server. But when the page runs behind load balancer with 2 servers, it fails with key not valid for use in specified
state exception. Stickiness is enabled on load balancer. verified that.
I had made few changes to config file in microsoft.identitymodel section to accomodate adfs custom login. This included removing securitytokenhandlers and issuertokenresolvers as well. Is this impacting the encryption/decryption in anyway?
Any pointers would help.
Reference point for my application page : http://blog.helloitsliam.com/Lists/Posts/Post.aspx?ID=76

Hi,
As I understand, you encountered the error “Key not valid for use in specified state” when ADFS custom login.
In order to run in Windows Azure Web Sites a Web application which uses WIF for handling authentication, you must change the default cookie protection method (DPAPI, not available on Windows Azure Web Sites) to something that will work in a farmed environment
and with the IIS’ user profile load turned off.
1. If you are using the Identity and Access Tools for VS2012, just go to the Configuration tab and check the box “Enable Web farm ready cookies”.
2. If you want to do things by hand, add the following code snippet in your system.identitymodel/identityConfiguration element:
   <securityTokenHandlers>
     <add type="System.IdentityModel.Services.Tokens.MachineKeySessionSecurityTokenHandler,
             System.IdentityModel.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
      <remove type="System.IdentityModel.Tokens.SessionSecurityTokenHandler,
            System.IdentityModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
    </securityTokenHandlers>
There is a similar case:
http://stackoverflow.com/questions/19323287/key-not-valid-for-use-in-specified-state-error-for-net-4-5-mvc-4-application
Best regards,
Sara Fan
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Reporting Service Integration mode and Key not valid for use in specified state

I had to uninstall SharePoint Foundation 2013 and reinstall it.
What I have done:
I uninstalled SharePoint and after that I removed all databases.
I reinstalled SharePoint Foundation 2013 and it completed without errors.
Everything else is working, except SSRS in Sharepoint Integrated Mode.
If I check Central Administration - Manage services on server, I can found out that SQL Server Reporting Service Service is
"Started". But if I try to create new service application (SQL Server Reporting Services Service Application), it gives me an error message:
"Key not valid for use in specified state. (Exception from HRESULT: 0x8009000B)"
I uninstalled SSRS in Sharepoint Integrated Mode and I reinstalled it but problems exists.
It seems that "Encryption Keys" cause this problem.
https://support.microsoft.com/kb/955757
https://msdn.microsoft.com/en-us/library/ms156010%28v=sql.110%29.aspx
I tried to Re-create Encryption Keys and Delete keys, but its not working either. It gives me only error message that:
"Unable to locate the Reporting Server Windows service for instance MSSQLSERVER."
I don't have any reporting server databases, because I removed all
databases when I uninstalled SharePoint. Also I don't have Encryption
Keys backups.
I have found several similar question but no answer, example here:
https://social.technet.microsoft.com/Forums/ie/en-US/df02dc05-5ce8-499d-9ba3-ab392a5fc3af/sharepoint-2013-ssrs-application-error-key-not-valid-for-use-in-specified-state-exception?forum=sharepointdevelopment
Any ideas how I can fix this problem?

Hi,
From the Reporting Server Configuration Manager you have to restore the encryption key.
Please try to delete databases(reportserver & reportservertempdb) and delete the reportserver and reports site on IIS. Then you have to start over the configuration again.
If the issue still exists, Please check ULS log to see if anything unexpected occurred.
For SharePoint 2013, by default, ULS log locates in
"C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS"
More information about SQL Reporting services Installation with SharePoint 2013 for your reference:
http://expertsharepoint.blogspot.de/2014/03/sql-reporting-services-installation.html
Best Regards,
Dennis Guo
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

The method getBean() is not valid for metadata object /ex/model/remittance/client/common/bc4j.xcfg

Hi,
I am getting bellow error when i am running my application. I am using JDeveloper 11.1.2.3
<Nov 6, 2013 9:52:57 AM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Nov 6, 2013 9:52:57 AM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<BC4JConfigLifeCycleCallBack> <contextInitialized> MDS-01702: The method getBean() is not valid for metadata object /ex/model/remittance/client/common/bc4j.xcfg - it is allowed on only bean metadata objects.
oracle.mds.exception.MDSRuntimeException: MDS-01702: The method getBean() is not valid for metadata object /ex/model/remittance/client/common/bc4j.xcfg - it is allowed on only bean metadata objects.
at oracle.mds.core.MetadataObject.getBean(MetadataObject.java:327)
at oracle.adf.share.jndi.MDSBackingStore.getMOBean(MDSBackingStore.java:558)
at oracle.bc4j.mbean.RuntimeMXBeanImpl.init(RuntimeMXBeanImpl.java:120)
at oracle.bc4j.mbean.RuntimeMXBeanImpl.<init>(RuntimeMXBeanImpl.java:110)
at oracle.bc4j.mbean.RuntimeMXBeanImpl.<init>(RuntimeMXBeanImpl.java:101)
at oracle.bc4j.mbean.BC4JConfigLifeCycleCallBack.contextInitialized(BC4JConfigLifeCycleCallBack.java:114)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
<Nov 6, 2013 9:53:11 AM AST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\maroof\AppData\Roaming\JDeveloper\system11.1.2.3.39.62.76.1\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log will be rotated. Reop
I seen oracle docs solution
MDS-01702: The method getBean() is not valid for metadata object {0} - it is allowed on only bean metadata objects.
Cause: An attempt was made to access the metadata object using the bean API but the metadata object was not a bean metadata object. The schema for the root element may not have been registered with MDS, or the beans were not available on the classpath.
Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.
Level: 1
Type: ERROR
Impact: Configuration
But i am not getting what i do in my application for removing this error.
Maroof

Do you use MDS in your application?
It's possible that you see a leftover of an earlier deployment.
Do you get the same error if you only start the integrated server (application server navigator->integrated server->debug or run)?
IF you don't get it when you only start the server without running your application, the problem is somewhere in your app. If you get the error it's probably an old deployment or a configuration error of your server. In this case stop jdev, rename the DefaultDomain folder C:\Users\maroof\AppData\Roaming\JDeveloper\system11.1.2.3.39.62.76.1\DefaultDomain tp C:\Users\maroof\AppData\Roaming\JDeveloper\system11.1.2.3.39.62.76.1\xxxDefaultDomain and start jdev again. Then use hte application server navigator to create a new integrated server (you should see this option as the DefaultDomain folder is not present) and once the new integrated server is created test again.
Timo

Key not valid for use in specified state.

Hi. Muse update to 2014.1 will not install, so I uninstalled Muse 2014 and tried again and again, no luck. However, I just updated InDesign and Premiere Pro successfully.
Thank you for any tips.
Error log is as follows:
"Payload: Muse CC (2014.1) 2014.1.0.375 Muse_2014_1_CC_LS24.msi_2014.1.0.375 -----------
ERROR: Key not valid for use in specified state.
ERROR: Install MSI payload failed with error: 1603 - Fatal error during installation.
MSI Error message: Key not valid for use in specified state.
ERROR: Third party payload installer Muse_2014_1_CC_LS24.msi failed with exit code: 1603

I solved the problem by restarting the computer and logging in to an administrator account. Then I was able to install Muse 2014.1
Perhaps, if this makes any sense technically, one part of the install process touched a nerve with a component in the process that required admin privileges that my day-to-day account was denying?
I hope it helps others - and I see there are a few having this problem.
Again, many thanks for your support, kglad.

SQL Server Mgt Studio 2008 installation problem - Key not valid for use in specified state

I'm setting up SQL Server Management Studio 2008 on my laptop. It installed fine, but failed to import a regsrver file exported from another machine. This appears to have been due to the fact that I exported the file with usernames and passwords, although I must admit that's pretty darned inconvenient if it can't be done.
Nevertheless, I exported the file again without usernames and passwords, but the new install now won't let me even see servers, let alone import any new ones.
When I start Studio, it gives me the "Key not valid for use in specified state" error. When I 'continue', I'm delivered to a screen with the 'registered servers' pane crippled. It has no contents at all and no ability to add, select, import, export. Nothing there.
How do I rectify this?
The installation is on Windows 7 Home Premium.
Thanks for any suggestions.

Hi Don,
Since this issue was still not resolved even after you reinstall SQL Server 2008, I think that this issue is probably related to some corrupted files or registry keys. Please refer to the following steps to see if you can resolve this issue:
1. Close your SSMS;
2. Go to the folder %appdata%\Microsoft\Microsoft SQL Server\100\Tools\ and check if there is a Shell folder, if so, rename it to Shell-Copy;
3. Re-open your SSMS to see if the error persists.
Everytime SQL Server 2008 Management Studio starts, it will read information from this folder to retrieve and recover some data. If the information does not exists, it will recreate new ones. Please check if this helps.
Best regards,
Charles Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help
To add to Don's comment, if you are using a different account (for example, an SA account) to run SQL Server management studio then make sure to change the user profile name when you browse to "%appdata%\Microsoft\Microsoft SQL Server\100\Tools\".
I know many of us developers have multiple accounts and I usually have my SA account have logon privileges on databases not my regular AD Account.
Other than that, the reason why this fails is because MS encrypted the regsrvr file on the source computer using the source computer's ID and is therefore unable to decrypt the file on the destination computer. To me that just doesn't make sense since the
whole idea of Export and import was to move this information across computers! And that's why this works when you import without username and passwords - no more encryption/decryption. Since we use integrated windows logon (trusted_connection=true) it works
great. For the few servers that we had SQL Logons I had to manually type them in and save. But all in all, pretty painless.

Authentication denied: Boot identity not valid for Managed Server

Similar Messages

Maybe you are looking for