JMX Connector URL
I am trying to connect to 10.1.3 using the following sample code from
http://www.oracle.com/technology/tech/java/oc4j/1013/release_notes/release-notes-1013-preview.htm
String url= "service:jmx:rmi:///opmn://stadp334:6003/home";
JMXServiceURL serviceUrl= new JMXServiceURL(url);
Hashtable env= new Hashtable();
// specify Oracle's implementation
env.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES, "oracle.oc4j.admin.jmx.remote");
Hashtable credentials= new Hashtable();
credentials.put("login", "oc4jadmin");
credentials.put("password", "<password>");
JMXConnector connector = JMXConnectorFactory.connect(serviceUrl, env);
MBeanServerConnection connection = connector.getMBeanServerConnection();
But I get following exception ....
java.net.MalformedURLException: URL path must begin with /jndi/ or /stub/ or /ior/: /opmn://localhost:12401/home
at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1785)
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:259)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:207)
Any idea why?
Also, am I using the right port #? The output of "opmnctl.exe status -l"
jms:12601,default-web-site:8888,rmi:12401
tells me the RMI port is 12401. Is that the right one to use?
Thanks
Cool, a JMX question! :-)
This is usually due to not having the right classpath setup where you are running the client.
See this blog entry for details:
http://buttso.blogspot.com/2006/06/client-setup-for-connecting-to-oc4j.html
When connecting via OPMN you need to use the OPMN request port as the value. It'll dispatch the actual ORMI port of the target OC4J instance to the client.
To get the OPMN request port use
opmnctl status -port6003 is the default port value for a first install.
cheers
-steve-
Similar Messages
-
Hi,
I have an multi MBean servers running on diffrent JBoss(not JBoss Mbean server).(server)
I have another MBean server running also on another JBoss (client)
Server Side
private CSAPLMBeanFactory()
// aachour for SSL enabling
// Get the JBoss MBean Server -- Note the JBOSS specific locator ...
log_.info("Instantiate the CSAPL MBean factory");
// localMBeanServer_ = org.jboss.mx.util.MBeanServerLocator.locateJBoss();
try
String cSAPLMbsHost = CSAPLConfiguration.getInstance().getHost();
int cSAPLMbsPort = CSAPLConfiguration.getInstance().getCsaplMBSPort_();
String address = cSAPLMbsHost + ":" + cSAPLMbsPort;
MBeanServer mbs = MBeanServerFactory.createMBeanServer();
HashMap env = new HashMap();
RMIClientSocketFactory csf = new SslRMIClientSocketFactory();
RMIServerSocketFactory ssf = new SslRMIServerSocketFactory();
env.put(RMIConnectorServer.RMI_CLIENT_SOCKET_FACTORY_ATTRIBUTE, csf);
env.put(RMIConnectorServer.RMI_SERVER_SOCKET_FACTORY_ATTRIBUTE, ssf);
try
LocateRegistry.createRegistry(cSAPLMbsPort);
System.out.println("RMI registry ready.");
catch (Exception e)
System.out.println("Exception starting RMI registry:");
e.printStackTrace();
JMXServiceURL url = new JMXServiceURL("service:jmx:rmi:///jndi/rmi://" + address + "/CSAPL");
JMXConnectorServer cs = JMXConnectorServerFactory.newJMXConnectorServer(url, env, mbs);
cs.start();
localMBeanServer_ = mbs;
catch (Exception e)
e.printStackTrace();
plLogName_ = CSAPLConfiguration.getInstance().getPLLogicalName();
}Client side :method to connect to the MBean server
public synchronized MBeanServerConnection getMBeanServer() throws CSAPLException
if (server == null)
String address = host + ":" + port;
if (log.isTraceEnabled())
log.trace("Getting reference to mbean server connection in " + address);
try
Hashtable env = new Hashtable();
if (certifPath != null)
env.put("javax.net.ssl.trustStore", certifPath);
JMXServiceURL url = new JMXServiceURL("service:jmx:rmi:///jndi/rmi://" + address + "/CSAPL");
JMXConnector jmxc = JMXConnectorFactory.connect(url, env);
server = jmxc.getMBeanServerConnection();
catch (Exception e)
log.error("cannot get reference to mbean server connection");
if (e instanceof javax.naming.NameNotFoundException)
log.error("Could not contact server address " + host);
}The problem is that I have this exception on client side:
java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
I don't want to use the
System.setProperty ("javax.net.ssl.trustStore", certifPath)because I have other application running on the same JVM using diffrent SSL certificate .
Please help me it is very urgent1. Note:250532.1 Configuring HTTP Server to Use SSL in Oracle Application Server 10g (9.0.4)
2. Note:250648.1 Configuring Web Cache with SSL in Oracle Application Server 10G (9.0.4)
3. Note:251046.1 How to Configure SSL for Single-Sign On Applications in Oracle Application Server 10g (9.0.4)
4. Also, see: Oracle OID administrator's Guide, Oracle SSO Administration Guide, Oracle SCA Guide, Oracle Portal Configuration Guide and Oracle Application Server Administrator's Guide. -
Hi
Can any one post the URL of AD connector for OIM version 9.1.0.0 and JDK version 1.4.2
I've downloaded AD connector 9.1.1.5 but seems like it is not compatible with my OIM instance.
Thankshttp://www.oracle.com/technetwork/middleware/id-mgmt/downloads/connectors-101674.html
-
Securing the Peoplesoft JMS listening connector URL
In order to start or stop the JMS listening connector we execute a URL on the browser; the URL looks like..
http://<WEBSERVER>:<PORT>/PSIGW/JMSListeningConnectorAdministrator?Activity=START
http://<WEBSERVER>:<PORT>/PSIGW/JMSListeningConnectorAdministrator?Activity=STOP
Problem with this is that any one who knows this can playaround with the listening connector of the production instance; and moreover if he can access the peoplesoft signon page, he can easily know the webserver URL.
Is there any means that this can be secured; for example executing this URL should first take the user to an authentication page..
-Sudriptaon the webserver u can find the .class file here
PS_HOME\webserv\domain_name\applications\peoplesoft\PSIGW\WEB-INF\classes\com\peoplesoft\pt\integrationgateway\listeningconnector
u open this .class file u need a java compiler (or) hex editor to read the content.
Thnks! -
Vibe connector .6210.
The following error is recorded in the default.pipeline.vibe-Application
log.
URLError: <urlopen error [Errno 1] _ssl.c:482: error:140770FC:SSL
routines:SSL23_GET_SERVER_HELLO:unknown protocol>
Obviously this is a protocol error, but what is it actually telling me?
Besides the fact that the connector never completes startup.
JoeKOriginally Posted by JKress
Vibe connector .6210.
The following error is recorded in the default.pipeline.vibe-Application
log.
URLError: <urlopen error [Errno 1] _ssl.c:482: error:140770FC:SSL
routines:SSL23_GET_SERVER_HELLO:unknown protocol>
Obviously this is a protocol error, but what is it actually telling me?
Besides the fact that the connector never completes startup.
JoeK
Have not setup the Vibe connector before... so not sure. But it could be that there is an issue with the supplied SSL certificates, or the site is not listening on 443 (hinting to Vibe defaulting to 8080 and 8444).
Have you set the 8443 port and if not, if port 443 listening for Vibe services?
Cheers,
Willem -
Web Services Connector for JMX available
We are glad to announce that the Reference Implementation of our Web-Services Connector for JMX Agents, being defined by JSR 262, is available in Early Access on http://ws-jmx-connector.dev.java.net/. This major milestone is aligned with the second Early Draft Review of the Specification in the Java Community Process.
The WS-Connector for JMX is based on the WS-Management protocol, defined by the DMTF. Its greatest benefit is to provide interoperability between a variety of client applications compliant with this standard, including those not based on the Java platform, and any JMX-based instrumentation.
This week, at JavaOne, we will demonstrate examples of this interoperability on stage during the technical session "TS 2656 - JMX Technology: Who's Doing What". We will show in particular how Windows Vista's management tools can use the JVM telemetry instrumentation. Join Eamonn McManus and Jean-Francois Denise, or watch their blogs, for more details on this.
We encourage you to use and provide feedback on the WS-Connector RI early access, which is fully functional and, we believe, already pretty stable.
Note that our implementation of the WS-Management protocol is based on the Wiseman open source project, which lives at http://wiseman.dev.java.net/.
The JMX Team.We are glad to announce that the Reference Implementation of our Web-Services Connector for JMX Agents, being defined by JSR 262, is available in Early Access on http://ws-jmx-connector.dev.java.net/. This major milestone is aligned with the second Early Draft Review of the Specification in the Java Community Process.
The WS-Connector for JMX is based on the WS-Management protocol, defined by the DMTF. Its greatest benefit is to provide interoperability between a variety of client applications compliant with this standard, including those not based on the Java platform, and any JMX-based instrumentation.
This week, at JavaOne, we will demonstrate examples of this interoperability on stage during the technical session "TS 2656 - JMX Technology: Who's Doing What". We will show in particular how Windows Vista's management tools can use the JVM telemetry instrumentation. Join Eamonn McManus and Jean-Francois Denise, or watch their blogs, for more details on this.
We encourage you to use and provide feedback on the WS-Connector RI early access, which is fully functional and, we believe, already pretty stable.
Note that our implementation of the WS-Management protocol is based on the Wiseman open source project, which lives at http://wiseman.dev.java.net/.
The JMX Team. -
New Web Services Connector for JMX available
A new Early Access (EA3) of the Connector is out. It implements the JSR 262 Public Review Specification (http://jcp.org/aboutJava/communityprocess/pr/jsr262/index.html).
You can download the RI auto-extractible jar file from http://ws-jmx-connector.dev.java.net
For more information on the content of this release, you can have a look to this blog entry : http://blogs.sun.com/jmxnetbeans/entry/web_services_connector_for_jmx
Best Regards.
Jean-Fran�ois Denise
http://blogs.sun.com/jmxnetbeans/A new Early Access (EA3) of the Connector is out. It implements the JSR 262 Public Review Specification (http://jcp.org/aboutJava/communityprocess/pr/jsr262/index.html).
You can download the RI auto-extractible jar file from http://ws-jmx-connector.dev.java.net
For more information on the content of this release, you can have a look to this blog entry : http://blogs.sun.com/jmxnetbeans/entry/web_services_connector_for_jmx
Best Regards.
Jean-Fran�ois Denise
http://blogs.sun.com/jmxnetbeans/ -
JMX server connector on port 3997 error
Hi,
When i execute " dsccagent start " command, i am facing this error
**** Server encountered the following error: Failed to start JMX connector serve
r on port 3997: Invalid host Hostname
The agent C:\sun\dsee7\var\dcc\agent has not been started
Please help me.
Thanks,
SantoshThis issue has been resolved. The solution was to enable the fax connector (Exchange management Console/Server Configuration/Hub Transport/Receive Connectors/Windows SBS Fax Sharepoint Receive [Servername] = Enable.
Useful general reference:
http://blogs.technet.com/b/sbs/archive/2009/07/01/sbs-2008-introducing-the-pop3-connector.aspx
me -
JMX, Firewall and javaagent option
Hey all,
I'm working on setting up JMX monitoring on the JVMs running in our environment. Most of those JVMs are running third party applications supplied by our customers and are heavily protected by firewalls. So i needed to use the JavaAgent strategy to be able to set a fixed port for the JMX agent. (see: http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html)
This all works very nice except that the JVM will never exit. The RMI Reaper is a non-daemon thread and will have to be stopped manually before the JVM will shutdown. The application has no knowledge of the RMI Reaper (as it is started from the premain method). A ShutdownHook doesn't work because those are called after the JVM decided to shutdown or when an external event is triggered (Ctrl-C) for example.
For now i have this horrible workaround. I create a thread that checks if there is still a main thread in the JVM. If there isn't it shuts down the JMX server and that allows the JVM to close down. Is there a better way of doing this? below is the code:
public class JMXAgent {
private static JMXConnectorServer cs;
private static Logger logger;
public static void premain(String agentArgs, Instrumentation inst) {
/** snip */
JMXServiceURL url =
new JMXServiceURL("service:jmx:rmi://0.0.0.0:" + RMIConnectorPort + "/jndi/rmi://:" + RMIRegistryPort + "/jmxrmi");
cs = JMXConnectorServerFactory.newJMXConnectorServer(url, env, mbs);
// Setup the failsafe
Thread failsafeThread = new MainCheckerThread();
failsafeThread.start();
logger.fine("MainChecker Thread created.");
// Setup the shutdown hook
Thread shutdownThread = new ShutdownThread();
Runtime.getRuntime().addShutdownHook(shutdownThread);
logger.fine("SchutdownHook implemented.");
public static void stop() {
try {
logger.info("Stop called");
cs.stop();
} catch (IOException ex) {
ex.printStackTrace();
* Shutdown thread that allows the tracer to write out any final
* information.
private static class ShutdownThread extends Thread {
@Override
public void run() {
JMXAgent.stop();
Runtime.getRuntime().halt(0);
private static class MainCheckerThread extends Thread {
@Override
public void run() {
boolean found = true;
while (found) {
Logger.getLogger(this.getClass().getName()).finest("Ping!");
ThreadGroup root = Thread.currentThread().getThreadGroup();
while (root.getParent() != null) {
root = root.getParent();
Thread[] list = new Thread[400];
int threads = root.enumerate(list, true);
found = false;
for (int i=0; i<threads; i++) {
if (!list.isDaemon()) {
if (list[i].getName().equals("main")) {
found = true;
if (!found) {
/** No main found, stop the RMI server */
JMXAgent.stop();
} else {
try {
Thread.sleep(10000);
} catch (InterruptedException ex) {
JMXAgent.stop();
found=false;Hi Hugo,
This is a very interesting question.
What happens here is that the RMI object exported by the JMX connector server prevents
the RMIReaper thread from terminating: as long as the JMX connector server is active, its
exported RMIServer object will remain active, and the RMI Reaper thread will stay there
waiting for the RMIServer object to be unexported.
This is in fact a feature: JMX connector servers where designed to be controlled by
the application itself. In the usual way of using JMX Connector Server, you would start your
server in main() (or some application equivalent of main) and stop it later on before exiting
your application.
Things got a little more complex when we introduced the 'out-of-the-box management'.
In the 'out-of-the-box management' the default connector is not controlled by the application
but by the VM - or more exactly by an agent loaded in the VM. As you rightly noticed, the
agent has no idea as to when the application (the main) will exit.
The default 'out-of-the-box management' agent is thus conspiring with RMI (using sun
private APIs) to export its RMIServer object, so that its exported RMIServer doesn't
prevent the RMI Reaper thread to terminate. These APIs are unfortunately private and
non portables (and low-level).
Maybe we should think of supporting some kind of 'daemon connector servers' for the future.
The ability of starting JMX Connectors servers in premain agents obviously makes this desirable.
Concerning your 'hack' that detects the end of the main thread I will make two observations:
1) such a hack might work if indeed the application is expected to exit when the main thread
terminates. This is not always the case - for instance consider this:
public void main(String[] args) {
final Thread myMainThread = new Thread("My real main thread") {
public void run() {
try {
System.out.println("Strike <return> to exit: ");
System.in.read();
} catch(Exception x) {
x.printStackTrace();
myMainThread.start();
}Such an application will wait for the user to strike enter to exit, although the main thread is
already terminated and gone. So the termination of main thread doesn't necessarily means
that the application is finished.
2) The concept of detecting a main thread is tenuous. What happens if an application does
new Thread("main") ?
This being said - detecting the absence of "main" thread might be sufficient to your needs in
most of the case. If you simply call JMXConnectorServer.stop() when you detect that the
main thread is no longer there - the only risk you will be taking is stopping the
JMXConnectorServer ahead of time, before the application actually exits. If you want
to implement such a hack - you might wish to use the following logic:
// Attempts to find a "main" thread
public static Thread findmain() {
// When the premain agent is loaded from the command line the
// current thread is the main thread....
final Thread current = Thread.currentThread();
if (current.getName().equals("main")) return current;
// If the premain agent was loaded from the attach API, or by some
// other means, the current thread might not be the main thread.
// Try to find a main thread using Thread.enumerate()
// The main thread should be already there, allocate some
// more space than needed just to be sure we do get it, even if
// new threads are created in between.
final Thread[] all = new Thread[Thread.activeCount()+100];
final int count = Thread.enumerate(all);
// Try to find the main thread
for (int i=0;i<count;i++) {
if (all.getName().equals("main")) return all[i];
return null;
public static void premain(String agentArgs)
throws IOException {
final JMXConnectorServer cs = .....
cs.start();
final Thread main = findmain();
final Thread clean = new Thread("JMX Agent Cleaner") {
public void run() {
try {
if (main != null) main.join();
System.out.println("main thread exited...");
} catch (Exception x) {
x.printStackTrace();
} finally {
try {
System.out.println("cleaning up JMX agent...");
cs.stop();
} catch (Exception x) {
x.printStackTrace();
clean.setDaemon(true);
clean.start();
If you really want your JMXConnectorServer to stop() at the latest possible time, you could
for instance modify this logic to find the first non daemon thread (excluding RMI Reaper and
DestroyJavaVM threads), join it, and loop over this until the only non daemon thread that
remains is/are the RMI Reaper threads, in which case you would close the
JMXConnectorServer.
This would not be completely foolproof either because the normal behavior of the application
could precisely be to be held alive by an exported object, and waiting on some
external communication to stop. So even counting the non-daemon thread until only
the RMI Reaper threads remain doesn't necessarily means that the application is
finished...
Here is an example of CleanThread class that implements the logic above:
public class JMXAgent {
public static class CleanThread extends Thread {
private final JMXConnectorServer cs;
public CleanThread(JMXConnectorServer cs) {
super("JMX Agent Cleaner");
this.cs = cs;
setDaemon(true);
public void run() {
boolean loop = true;
try {
while (loop) {
final Thread[] all = new Thread[Thread.activeCount()+100];
final int count = Thread.enumerate(all);
loop = false;
for (int i=0;i<count;i++) {
final Thread t = all;
// daemon: skip it.
if (t.isDaemon()) continue;
// RMI Reaper: skip it.
if (t.getName().startsWith("RMI Reaper")) continue;
if (t.getName().startsWith("DestroyJavaVM")) continue;
// Non daemon, non RMI Reaper: join it, break the for
// loop, continue in the while loop (loop=true)
loop = true;
try {
System.out.println("Waiting on "+t.getName()+
" [id="+t.getId()+"]");
t.join();
} catch (Exception ex) {
ex.printStackTrace();
break;
// We went through a whole for-loop without finding any thread
// to join. We can close cs.
} catch (Exception ex) {
ex.printStackTrace();
} finally {
try {
// if we reach here it means the only non-daemon threads
// that remain are reaper threads - or that we got an
// unexpected exception/error.
cs.stop();
} catch (Exception ex) {
ex.printStackTrace();
public static void premain(String agentArgs)
throws IOException {
final JMXConnectorServer cs = .....
cs.start();
final Thread clean = new CleanThread(cs);
clean.start();
Thanks for bringing this to my attention! I'm probably going to have to update my entry
on this subject at
http://blogs.sun.com/jmxetc/entry/connecting_through_firewall_using_jmx
Hope this helps,
-- daniel
http://blogs.sun.com/jmxetc -
Hi all
As many others I am facing also connection problems with Windows Server 2012 Essentials R2 and a windows client pc.
The client pc in question, with windows 8 pro, has been successfully joined through the essentials connector to the domain.
All things went good: media streaming, shared folders, a successfull backup has been started through the essentials launchpad, the client appeared as online in the devices tab of the essentials dashboard.
Then I upgraded the pc to windows 8.1 pro.
Now the client can't connect to the server. Following issues appear:
The client pc is showed as offline the the dashboard when it is online.
Backups (from launchpad or server) aren't possible -> no connection to the windows server essentials adminitration service.
Dashboard not available from launchpad
The message "the server is not available" appears, when I try to reconnect the client by the essentials connector.
BUT:
ping to the server's ip address works.
media streaming is also ok
shared folders are still available.
Any ideas what changed with the upgrade to 8.1 Pro? Is the a firewall problem on the client pc?
Many thanks for your help.
PS. If anyone needs a specific log file from the server or the client, please let me know.Hi Justin
I executed all you instructions, but nothing helped.
I add here the ClientDeploy.log and the ComputerConnector.log
The ClientDeploy stopps after a registry insert error.
The user executing the connector is member of the Administrators Group on the Client pc.
I started the connector even with "Run as Administrator" but nothing helped.
Any ideas why this registry insert failes?
Thanks for you help and best regards
Hans
[5692] 140604.211748.1774: ClientSetup: Start of ClientDeploy
[5692] 140604.211748.3181: General: Initializing...C:\WINDOWS\system32\Essentials\ClientDeploy.exe
[5692] 140604.211748.3337: ClientSetup: Create client deployment registry subkey if necessary
[5692] 140604.211748.3493: ClientSetup: The initial launching way: -LaunchedFrom:installer
[5692] 140604.211748.3493: ClientSetup: The initial state is set
[5692] 140604.211748.3493: ClientSetup: The initial serverName: 192.168.3.21
[5692] 140604.211748.3493: ClientSetup: Loading Wizard Data
[5692] 140604.211748.3649: ClientSetup: Saving Wizard Data
[5692] 140604.211748.3649: ClientSetup: Current DeploymentStatus=Start
[5692] 140604.211748.7400: ClientSetup: Showing the Client Deployment Wizard
[5692] 140604.211748.8493: ClientSetup: Machine name:PCFA, length:4
[5692] 140604.211748.8650: ClientSetup: The input server name is 192.168.3.21
[2156] 140604.211748.8806: ClientSetup: Entering ConnectorWizardForm.RunTasks
[2156] 140604.211748.8806: ClientSetup: Running Task with Id=ClientDeploy.PreConfiguration
[5692] 140604.211748.8962: ClientSetup: InitWizard, The currrent stage is ConnectingToServer
[5692] 140604.211748.8962: ClientSetup: Set the Deployment Sync Event
[2156] 140604.211748.8962: ClientSetup: The configuration cab will be downloaded from 192.168.3.21
[2156] 140604.211748.9118: ClientSetup: Download file Setup.cab from server
[2156] 140604.211748.9275: ClientSetup: Making web request:
https://192.168.3.21//connect/default.aspx?Get=Setup.cab&LanguageId=1031&64bit=1
[2156] 140604.211748.9743: ClientSetup: Failed to download Setup.cab from server: System.Net.WebException: Die zugrunde liegende Verbindung wurde geschlossen: Für den geschützten SSL/TLS-Kanal konnte keine Vertrauensstellung hergestellt werden.. ---> System.Security.Authentication.AuthenticationException:
Das Remotezertifikat ist laut Validierungsverfahren ungültig.
bei System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
bei System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
bei System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
bei System.Net.ConnectStream.WriteHeaders(Boolean async)
--- Ende der internen Ausnahmestapelüberwachung ---
bei System.Net.HttpWebRequest.GetResponse()
bei Microsoft.WindowsServerSolutions.ClientSetup.CSCommon.DownloadFileFromConnectSite(String outputDirectory, Uri serverUrl, String fileName, Int32 languageId, Boolean is64bit)
[2156] 140604.211748.9743: ClientSetup: Cannot get configuration file with https, will try http...
[2156] 140604.211748.9743: ClientSetup: Download file Setup.cab from server
[2156] 140604.211748.9743: ClientSetup: Making web request:
http://192.168.3.21//connect/default.aspx?Get=Setup.cab&LanguageId=1031&64bit=1
[2156] 140604.211749.0369: ClientSetup: Downloaded file C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
[2156] 140604.211749.0369: ClientSetup: The configuration cab is downloaded to C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
[2156] 140604.211749.1775: ClientSetup: Adding Server Info data in the Product Registry
[2156] 140604.211749.1931: DnsEnvironmentDetector: GetHostAddresses() returned 192.168.3.21, normal environment
[2156] 140604.211749.1931: ClientSetup: Exiting PreConfigTask.Run()
[2156] 140604.211749.1931: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has TaskStatus=Success
[2156] 140604.211749.1931: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has RebootStatus=NoReboot
[2156] 140604.211749.1931: ClientSetup: Exting ConnectorWizardForm.RunTasks
[5792] 140604.211758.0217: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred
[5792] 140604.211758.0373: ClientSetup: Entering ConnectorWizardForm.RunTasks
[5792] 140604.211758.0373: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask
[5792] 140604.211758.0373: ClientSetup: Entering InstallRootCertTask.Run
[5792] 140604.211758.0373: ClientSetup: Install root cert to local trusted store
[5792] 140604.211758.0373: ClientSetup: Exiting InstallRootCertTask.Run
[5792] 140604.211758.0373: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success
[5792] 140604.211758.0373: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot
[5792] 140604.211758.0373: ClientSetup: Exting ConnectorWizardForm.RunTasks
[5792] 140604.211758.0373: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred
[5792] 140604.211758.0373: ClientSetup: Entering ConnectorWizardForm.RunTasks
[5792] 140604.211758.0373: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask
[5792] 140604.211758.0529: ClientSetup: Entering SetupVpnAndDATask.Run
[5792] 140604.211758.0685: ClientSetup: Deploy VPN profile
[5792] 140604.211758.0998: ClientSetup: Exting SetupVpnAndDATask.Run
[5792] 140604.211758.0998: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Success
[5792] 140604.211758.0998: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot
[5792] 140604.211758.0998: ClientSetup: Exting ConnectorWizardForm.RunTasks
[5792] 140604.211758.0998: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
[5792] 140604.211758.0998: ClientSetup: Entering ConnectorWizardForm.RunTasks
[5792] 140604.211758.0998: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
[5792] 140604.211758.0998: ClientSetup: Entering ValidateUserTask.Run
[5792] 140604.211758.0998: ClientSetup: Validating User
[5792] 140604.211758.0998: ClientSetup: Call MachineIdentityManager.GetMachineStatus
[5792] 140604.211758.1779: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:NetworkError ErrorCode:-1
BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus ---> System.ServiceModel.Security.SecurityNegotiationException: Es konnte keine Vertrauensstellung für den sicheren SSL/TLS-Kanal
mit Autorität mars01:65500 eingerichtet werden. ---> System.Net.WebException: Die zugrunde liegende Verbindung wurde geschlossen: Für den geschützten SSL/TLS-Kanal konnte keine Vertrauensstellung hergestellt werden.. ---> System.Security.Authentication.AuthenticationException:
Das Remotezertifikat ist laut Validierungsverfahren ungültig.
bei System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
bei System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
bei System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
bei System.Net.ConnectStream.WriteHeaders(Boolean async)
--- Ende der internen Ausnahmestapelüberwachung ---
bei System.Net.HttpWebRequest.GetResponse()
bei System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
--- Ende der internen Ausnahmestapelüberwachung ---
Server stack trace:
bei System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
bei System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
bei System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
bei System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
bei System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
bei System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
bei System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
bei System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
bei Microsoft.WindowsServerSolutions.Devices.Identity.CertWebService.ICertService.GetMachineStatus(GetMachineStatusRequest request)
bei Microsoft.WindowsServerSolutions.Devices.Identity.CertWebService.CertServiceClient.GetMachineStatus(String userName, String password, String machineName, MachineStatus& status, Boolean& isAdmin, Int32& maxClientNum, Int32& currentClientNum)
bei Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
--- Ende der internen Ausnahmestapelüberwachung ---
bei Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
bei Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)
[5792] 140604.211758.1779: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\WINDOWS\system32\ipconfig.exe" /all
[2156] 140604.211758.2092: ClientSetup: Standard Ouptput:
[2156] 140604.211758.2092: ClientSetup: Standard Ouptput: Windows-IP-Konfiguration
[2156] 140604.211758.2092: ClientSetup: Standard Ouptput:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Hostname . . . . . . . . . . . . : PCFA
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Prim„res DNS-Suffix . . . . . . . : mydomain.local
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Knotentyp . . . . . . . . . . . . : Hybrid
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: IP-Routing aktiviert . . . . . . : Nein
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: WINS-Proxy aktiviert . . . . . . : Nein
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: DNS-Suffixsuchliste . . . . . . . : mydomain.local
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Drahtlos-LAN-Adapter LAN-Verbindung* 11:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Medienstatus. . . . . . . . . . . : Medium getrennt
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Verbindungsspezifisches DNS-Suffix:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Beschreibung. . . . . . . . . . . : Virtueller Microsoft-Adapter fr direktes WiFi
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Physische Adresse . . . . . . . . : 16-
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: DHCP aktiviert. . . . . . . . . . : Ja
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Autokonfiguration aktiviert . . . : Ja
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Ethernet-Adapter LAN-Verbindung:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Verbindungsspezifisches DNS-Suffix:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Beschreibung. . . . . . . . . . . : Broadcom NetLink (TM)-Gigabit-Ethernet
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Physische Adresse . . . . . . . . : DC-
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: DHCP aktiviert. . . . . . . . . . : Ja
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Autokonfiguration aktiviert . . . : Ja
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: IPv4-Adresse . . . . . . . . . . : 192.168.2.6(Bevorzugt)
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Subnetzmaske . . . . . . . . . . : 255.255.255.0
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Lease erhalten. . . . . . . . . . : Mittwoch, 4. Juni 2014 18:03:36
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Lease l„uft ab. . . . . . . . . . : Freitag, 6. Juni 2014 20:49:17
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Standardgateway . . . . . . . . . : 192.168.2.1
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: DHCP-Server . . . . . . . . . . . : 192.168.2.1
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: DNS-Server . . . . . . . . . . . : 192.168.3.21
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
192.168.1.52
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: NetBIOS ber TCP/IP . . . . . . . : Aktiviert
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Drahtlos-LAN-Adapter WiFi:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Medienstatus. . . . . . . . . . . : Medium getrennt
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Verbindungsspezifisches DNS-Suffix: Home
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Beschreibung. . . . . . . . . . . : Qualcomm Atheros AR5B97-Funknetzwerkadapter
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Physische Adresse . . . . . . . . : 94-
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: DHCP aktiviert. . . . . . . . . . : Ja
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Autokonfiguration aktiviert . . . : Ja
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Tunneladapter isatap.{8F57A34A-FE47-429C-97D0-AA777D79C23F}:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Medienstatus. . . . . . . . . . . : Medium getrennt
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Verbindungsspezifisches DNS-Suffix:
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: DHCP aktiviert. . . . . . . . . . : Nein
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Autokonfiguration aktiviert . . . : Ja
[1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
[4504] 140604.211758.2092: ClientSetup: Standard Error:
[5792] 140604.211758.2248: ClientSetup: The exit code of the process (C:\WINDOWS\system32\ipconfig.exe) is: 0
[5792] 140604.211758.2248: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\WINDOWS\system32\route.exe" print
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: ===========================================================================
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: Schnittstellenliste
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 9...16 39 e5 4c c5 f2 ......Virtueller Microsoft-Adapter fr direktes WiFi
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 4...dc 0e a1 06 1f c9 ......Broadcom NetLink (TM)-Gigabit-Ethernet
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 3...94 39 e5 4c c5 f2 ......Qualcomm Atheros AR5B97-Funknetzwerkadapter
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 1...........................Software Loopback Interface 1
[1344] 140604.211758.2404: ClientSetup: Standard Error:
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 5...00 00 00 00 00 00 00 e0 Microsoft-ISATAP-Adapter
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: ===========================================================================
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput:
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: IPv4-Routentabelle
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: ===========================================================================
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: Aktive Routen:
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: Netzwerkziel Netzwerkmaske Gateway Schnittstelle Metrik
[5792] 140604.211758.2404: ClientSetup: The exit code of the process (C:\WINDOWS\system32\route.exe) is: 0
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 0.0.0.0 0.0.0.0 192.168.2.1
192.168.2.6 10
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 127.0.0.0 255.0.0.0 Auf Verbindung 127.0.0.1
306
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 127.0.0.1 255.255.255.255 Auf Verbindung 127.0.0.1 306
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 127.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 306
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 192.168.2.0 255.255.255.0 Auf Verbindung 192.168.2.6 266
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 192.168.2.6 255.255.255.255 Auf Verbindung 192.168.2.6 266
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 192.168.2.255 255.255.255.255 Auf Verbindung 192.168.2.6 266
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 224.0.0.0 240.0.0.0 Auf Verbindung 127.0.0.1
306
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 224.0.0.0 240.0.0.0 Auf Verbindung 192.168.2.6
266
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 255.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 306
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 255.255.255.255 255.255.255.255 Auf Verbindung 192.168.2.6 266
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: ===========================================================================
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: St„ndige Routen:
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: Keine
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput:
[5792] 140604.211758.2404: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\WINDOWS\system32\nslookup.exe" mars01
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: IPv6-Routentabelle
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: ===========================================================================
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: Aktive Routen:
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: If Metrik Netzwerkziel Gateway
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 1 306 ::1/128 Auf Verbindung
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: 1 306 ff00::/8 Auf Verbindung
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: ===========================================================================
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: St„ndige Routen:
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput: Keine
[2156] 140604.211758.2404: ClientSetup: Standard Ouptput:
[1344] 140604.211758.2560: ClientSetup: Standard Ouptput: Server: UnKnown
[1344] 140604.211758.2560: ClientSetup: Standard Ouptput: Address: 192.168.3.21
[1344] 140604.211758.2560: ClientSetup: Standard Ouptput:
[1344] 140604.211758.2560: ClientSetup: Standard Ouptput: Name: mars01.mydomain.local
[1344] 140604.211758.2560: ClientSetup: Standard Ouptput: Addresses: 192.168.3.21
[1344] 140604.211758.2560: ClientSetup: Standard Ouptput: 192.168.1.131
[1344] 140604.211758.2560: ClientSetup: Standard Ouptput: 192.168.4.31
[1344] 140604.211758.2560: ClientSetup: Standard Ouptput:
[4504] 140604.211758.2560: ClientSetup: Standard Error:
[1344] 140604.211758.2560: ClientSetup: Standard Ouptput:
[5792] 140604.211758.2560: ClientSetup: The exit code of the process (C:\WINDOWS\system32\nslookup.exe) is: 0
[5792] 140604.211758.2717: ClientSetup: Set CD Fail reason 10 for SQM in ClientDeployment.exe
[5792] 140604.211758.2717: ClientSetup: RecordClientDeploymentFailReason: Save registry failed in ClientDeployment.exe : System.UnauthorizedAccessException: In den Registrierungsschlüssel kann nicht geschrieben werden.
bei Microsoft.Win32.RegistryKey.EnsureWriteable()
bei Microsoft.Win32.RegistryKey.CreateSubKeyInternal(String subkey, RegistryKeyPermissionCheck permissionCheck, Object registrySecurityObj, RegistryOptions registryOptions)
bei Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck)
bei Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RecordClientDeploymentFailReason(UInt32 failReason)
[5792] 140604.211758.2717: ClientSetup: Exiting ValidateUserTask.Run
[5792] 140604.211758.2717: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed
[5792] 140604.211758.2717: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
[5792] 140604.211758.2717: ClientSetup: Exting ConnectorWizardForm.RunTasks
[06/04/2014 20:23:38 1730] --------------------------------------------------------------------------------------------------
[06/04/2014 20:23:38 1730] wmain: Start of Computerconnector
[06/04/2014 20:23:38 1730] GlobalData::Initialize (192.168.3.10, C:\Users\johndoe.mydomain\Downloads\ComputerConnector(192.168.3.10).exe)
[06/04/2014 20:23:38 1730] =================================
[06/04/2014 20:23:38 1730] Current Os information:
[06/04/2014 20:23:38 1730] Suite = [256]
[06/04/2014 20:23:38 1730] Type = [1]
[06/04/2014 20:23:38 1730] Architecture = [9]
[06/04/2014 20:23:38 1730] IsStarterEdition = [0]
[06/04/2014 20:23:38 1730] IsHomeSku = [0]
[06/04/2014 20:23:38 1730] Major = [6]
[06/04/2014 20:23:38 1730] Minor = [3]
[06/04/2014 20:23:38 1730] Build = [9600]
[06/04/2014 20:23:38 1730] SPMajor = [0]
[06/04/2014 20:23:38 1730] SPMinor = [0]
[06/04/2014 20:23:38 1730] =================================
[06/04/2014 20:23:38 1730] ExpandEnvironmentStrings return (C:\WINDOWS\Temp\ClientDeploymentTempFiles\)
[06/04/2014 20:23:38 1730] SetPackageDlcUrl: .NET url is set to
http://go.microsoft.com/?linkid=9816306
[06/04/2014 20:23:38 1730] SetPackageDlcUrl: Connector url is set to
http://go.microsoft.com/fwlink/p/?LinkId=275102
[06/04/2014 20:23:38 1730] wmain: Calling Computerconnector::ShowWizard()
[06/04/2014 20:23:38 1730] CComputerconnector::ShowWizard: Initializing common controls
[06/04/2014 20:23:38 1730] CComputerconnector::ShowWizard: Done initializing common controls
[06/04/2014 20:23:38 1730] Displaying the wizard
[06/04/2014 20:23:38 1730] CComputerconnector::WelcomeDlgProc: IDD_PROPPAGE_WELCOME Page Initialization
[06/04/2014 20:23:38 1730] Current user default UI lang setting is 1031
[06/04/2014 20:23:38 c8] CComputerconnector::Run: Installation is ready to run
[06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: IDD_PROPPAGE_TASKS Page Initialization
[06/04/2014 20:23:42 1774] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Die aktuellen Systemanforderungen werden ermittelt... Index= 0
[06/04/2014 20:23:42 1774] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {21E49794-7C13-4E84-8659-55BD378267D5} returned -1
[06/04/2014 20:23:42 1774] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {46DCED50-3A1D-4EF4-94F0-45F2681E3D70} returned -1
[06/04/2014 20:23:42 1774] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {C1E4D639-4A33-4314-809E-89BD0EF48522} returned -1
[06/04/2014 20:23:42 1774] Connector installation state is 1
[06/04/2014 20:23:42 1774] CComputerconnector::RunTasks: Running Task: Id=-1 Description=.NET Framework 4.5 wird heruntergeladen... Index= 1
[06/04/2014 20:23:42 1774] CComputerconnector::RunTasks: Running Task: Id=-1 Description=.NET Framework 4.5 wird installiert... Index= 2
[06/04/2014 20:23:42 1774] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Der Connector wird heruntergeladen... Index= 3
[06/04/2014 20:23:42 1774] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Windows Server Essentials Connector wird installiert... Index= 4
[06/04/2014 20:23:42 1774] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Die Einrichtung von Windows Server Essentials Connector wird gestartet... Index= 5
[06/04/2014 20:23:42 1774] RunShellExecute: ShellExecute [C:\WINDOWS\system32\Essentials\ClientDeploy.exe] with parameters [ -Server:192.168.3.10 -LaunchedFrom:installer]
[06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Running
[06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Die aktuellen Systemanforderungen werden ermittelt...
[06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: .NET Framework 4.5 wird heruntergeladen...
[06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: .NET Framework 4.5 wird installiert...
[06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Der Connector wird heruntergeladen...
[06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Windows Server Essentials Connector wird installiert...
[06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Die Einrichtung von Windows Server Essentials Connector wird gestartet...
[06/04/2014 20:23:42 1774] CComputerconnector::Run: Waiting upto 60secs for Sync Event to be signaled
[06/04/2014 20:23:43 1774] CComputerconnector::Run: WaitForSingleObject RetVal = 0
[06/04/2014 20:23:43 1730] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Success
[06/04/2014 20:23:43 1730] wmain: End of Computerconnector: hr=0x0
[06/04/2014 20:54:06 1220] --------------------------------------------------------------------------------------------------
[06/04/2014 20:54:06 1220] wmain: Start of Computerconnector
[06/04/2014 20:54:06 1220] GlobalData::Initialize (192.168.3.10, C:\Users\johndoe.mydomain\Downloads\ComputerConnector(192.168.3.10)(1).exe)
[06/04/2014 20:54:06 1220] =================================
[06/04/2014 20:54:06 1220] Current Os information:
[06/04/2014 20:54:06 1220] Suite = [256]
[06/04/2014 20:54:06 1220] Type = [1]
[06/04/2014 20:54:06 1220] Architecture = [9]
[06/04/2014 20:54:06 1220] IsStarterEdition = [0]
[06/04/2014 20:54:06 1220] IsHomeSku = [0]
[06/04/2014 20:54:06 1220] Major = [6]
[06/04/2014 20:54:06 1220] Minor = [3]
[06/04/2014 20:54:06 1220] Build = [9600]
[06/04/2014 20:54:06 1220] SPMajor = [0]
[06/04/2014 20:54:06 1220] SPMinor = [0]
[06/04/2014 20:54:06 1220] =================================
[06/04/2014 20:54:06 1220] ExpandEnvironmentStrings return (C:\WINDOWS\Temp\ClientDeploymentTempFiles\)
[06/04/2014 20:54:06 1220] SetPackageDlcUrl: .NET url is set to
http://go.microsoft.com/?linkid=9816306
[06/04/2014 20:54:06 1220] SetPackageDlcUrl: Connector url is set to
http://go.microsoft.com/fwlink/p/?LinkId=275102
[06/04/2014 20:54:06 1220] wmain: Calling Computerconnector::ShowWizard()
[06/04/2014 20:54:06 1220] CComputerconnector::ShowWizard: Initializing common controls
[06/04/2014 20:54:06 1220] CComputerconnector::ShowWizard: Done initializing common controls
[06/04/2014 20:54:06 1220] Displaying the wizard
[06/04/2014 20:54:06 1220] CComputerconnector::WelcomeDlgProc: IDD_PROPPAGE_WELCOME Page Initialization
[06/04/2014 20:54:06 1220] Current user default UI lang setting is 1031
[06/04/2014 20:54:06 1404] CComputerconnector::Run: Installation is ready to run
[06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: IDD_PROPPAGE_TASKS Page Initialization
[06/04/2014 20:54:09 e90] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Die aktuellen Systemanforderungen werden ermittelt... Index= 0
[06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Running
[06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Die aktuellen Systemanforderungen werden ermittelt...
[06/04/2014 20:54:09 e90] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {21E49794-7C13-4E84-8659-55BD378267D5} returned -1
[06/04/2014 20:54:09 e90] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {46DCED50-3A1D-4EF4-94F0-45F2681E3D70} returned -1
[06/04/2014 20:54:09 e90] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {C1E4D639-4A33-4314-809E-89BD0EF48522} returned -1
[06/04/2014 20:54:09 e90] Connector installation state is 1
[06/04/2014 20:54:09 e90] CComputerconnector::RunTasks: Running Task: Id=-1 Description=.NET Framework 4.5 wird heruntergeladen... Index= 1
[06/04/2014 20:54:09 e90] CComputerconnector::RunTasks: Running Task: Id=-1 Description=.NET Framework 4.5 wird installiert... Index= 2
[06/04/2014 20:54:09 e90] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Der Connector wird heruntergeladen... Index= 3
[06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: .NET Framework 4.5 wird heruntergeladen...
[06/04/2014 20:54:09 e90] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Windows Server Essentials Connector wird installiert... Index= 4
[06/04/2014 20:54:09 e90] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Die Einrichtung von Windows Server Essentials Connector wird gestartet... Index= 5
[06/04/2014 20:54:09 e90] RunShellExecute: ShellExecute [C:\WINDOWS\system32\Essentials\ClientDeploy.exe] with parameters [ -Server:192.168.3.10 -LaunchedFrom:installer]
[06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: .NET Framework 4.5 wird installiert...
[06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Der Connector wird heruntergeladen...
[06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Windows Server Essentials Connector wird installiert...
[06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Die Einrichtung von Windows Server Essentials Connector wird gestartet...
[06/04/2014 20:54:09 e90] CComputerconnector::Run: Waiting upto 60secs for Sync Event to be signaled
[06/04/2014 20:54:13 e90] CComputerconnector::Run: WaitForSingleObject RetVal = 0
[06/04/2014 20:54:13 1220] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Success
[06/04/2014 20:54:13 1220] wmain: End of Computerconnector: hr=0x0 -
Windows Server Essentials Connector issue
I cannot get the computer connector program to complete successfully. Had to add my 6 Pcs manually through the Properties screen on the PCs. As a result, Computers are not listed on the Anywhere Access screen and no-one can remote into their PC.
I have both, a self-signed certificate for the servername.domainname.local and a purchased certificate for the public domain on the server.
here is the computerconnector log and the clientdeployment log:
[05/27/2014 21:28:21 117c] --------------------------------------------------------------------------------------------------
[05/27/2014 21:28:21 117c] wmain: Start of Computerconnector
[05/27/2014 21:28:21 117c] GlobalData::Initialize (192.168.0.3, C:\Users\mmorton.MARCHITECTS\AppData\Local\Microsoft\Windows\INetCache\IE\8M2RXD56\ComputerConnector(192.168.0.3).exe)
[05/27/2014 21:28:21 117c] =================================
[05/27/2014 21:28:21 117c] Current Os information:
[05/27/2014 21:28:21 117c] Suite = [256]
[05/27/2014 21:28:21 117c] Type = [1]
[05/27/2014 21:28:21 117c] Architecture = [9]
[05/27/2014 21:28:21 117c] IsStarterEdition = [0]
[05/27/2014 21:28:21 117c] IsHomeSku = [0]
[05/27/2014 21:28:21 117c] Major = [6]
[05/27/2014 21:28:21 117c] Minor = [3]
[05/27/2014 21:28:21 117c] Build = [9600]
[05/27/2014 21:28:21 117c] SPMajor = [0]
[05/27/2014 21:28:21 117c] SPMinor = [0]
[05/27/2014 21:28:21 117c] =================================
[05/27/2014 21:28:21 117c] ExpandEnvironmentStrings return (C:\Windows\Temp\ClientDeploymentTempFiles\)
[05/27/2014 21:28:21 117c] SetPackageDlcUrl: .NET url is set to
http://go.microsoft.com/?linkid=9816306
[05/27/2014 21:28:21 117c] SetPackageDlcUrl: Connector url is set to
http://go.microsoft.com/fwlink/p/?LinkId=275102
[05/27/2014 21:28:21 117c] wmain: Calling Computerconnector::ShowWizard()
[05/27/2014 21:28:21 117c] CComputerconnector::ShowWizard: Initializing common controls
[05/27/2014 21:28:21 117c] CComputerconnector::ShowWizard: Done initializing common controls
[05/27/2014 21:28:21 117c] Displaying the wizard
[05/27/2014 21:28:21 117c] CComputerconnector::WelcomeDlgProc: IDD_PROPPAGE_WELCOME Page Initialization
[05/27/2014 21:28:21 117c] Current user default UI lang setting is 1033
[05/27/2014 21:28:21 1340] CComputerconnector::Run: Installation is ready to run
[05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: IDD_PROPPAGE_TASKS Page Initialization
[05/27/2014 21:28:25 cf0] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Detecting the current system requirements... Index= 0
[05/27/2014 21:28:25 cf0] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {21E49794-7C13-4E84-8659-55BD378267D5} returned -1
[05/27/2014 21:28:25 cf0] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {46DCED50-3A1D-4EF4-94F0-45F2681E3D70} returned -1
[05/27/2014 21:28:25 cf0] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {C1E4D639-4A33-4314-809E-89BD0EF48522} returned -1
[05/27/2014 21:28:25 cf0] Connector installation state is 1
[05/27/2014 21:28:25 cf0] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading .NET Framework 4.5... Index= 1
[05/27/2014 21:28:25 cf0] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing .NET Framework 4.5... Index= 2
[05/27/2014 21:28:25 cf0] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading the Connector... Index= 3
[05/27/2014 21:28:25 cf0] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing Windows Server Essentials Connector... Index= 4
[05/27/2014 21:28:25 cf0] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Starting the Windows Server Essentials Connector setup... Index= 5
[05/27/2014 21:28:25 cf0] RunShellExecute: ShellExecute [C:\Windows\system32\Essentials\ClientDeploy.exe] with parameters [ -Server:192.168.0.3 -LaunchedFrom:installer]
[05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Running
[05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Detecting the current system requirements...
[05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading .NET Framework 4.5...
[05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing .NET Framework 4.5...
[05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading the Connector...
[05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing Windows Server Essentials Connector...
[05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Starting the Windows Server Essentials Connector setup...
[05/27/2014 21:28:25 cf0] CComputerconnector::Run: Waiting upto 60secs for Sync Event to be signaled
[05/27/2014 21:28:26 cf0] CComputerconnector::Run: WaitForSingleObject RetVal = 0
[05/27/2014 21:28:26 117c] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Success
[05/27/2014 21:28:26 117c] wmain: End of Computerconnector: hr=0x0
[3808] 140527.212825.8067: ClientSetup: Start of ClientDeploy
[3808] 140527.212825.8267: General: Initializing...C:\Windows\system32\Essentials\ClientDeploy.exe
[3808] 140527.212825.8317: ClientSetup: Create client deployment registry subkey if necessary
[3808] 140527.212825.8367: ClientSetup: The initial launching way: -LaunchedFrom:installer
[3808] 140527.212825.8367: ClientSetup: The initial state is set
[3808] 140527.212825.8367: ClientSetup: The initial serverName: 192.168.0.3
[3808] 140527.212825.8367: ClientSetup: Loading Wizard Data
[3808] 140527.212825.8467: ClientSetup: Saving Wizard Data
[3808] 140527.212825.8467: ClientSetup: Current DeploymentStatus=Start
[3808] 140527.212826.0317: ClientSetup: Showing the Client Deployment Wizard
[3808] 140527.212826.1167: ClientSetup: Machine name:M16, length:3
[3808] 140527.212826.1267: ClientSetup: The input server name is 192.168.0.3
[5052] 140527.212826.1417: ClientSetup: Entering ConnectorWizardForm.RunTasks
[5052] 140527.212826.1417: ClientSetup: Running Task with Id=ClientDeploy.PreConfiguration
[3808] 140527.212826.1417: ClientSetup: InitWizard, The currrent stage is ConnectingToServer
[3808] 140527.212826.1417: ClientSetup: Set the Deployment Sync Event
[5052] 140527.212826.1467: ClientSetup: The configuration cab will be downloaded from 192.168.0.3
[5052] 140527.212826.1517: ClientSetup: Download file Setup.cab from server
[5052] 140527.212826.1567: ClientSetup: Making web request:
https://192.168.0.3//connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1
[5052] 140527.212826.1767: ClientSetup: Failed to download Setup.cab from server: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException:
The remote certificate is invalid according to the validation procedure.
at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.WindowsServerSolutions.ClientSetup.CSCommon.DownloadFileFromConnectSite(String outputDirectory, Uri serverUrl, String fileName, Int32 languageId, Boolean is64bit)
[5052] 140527.212826.1767: ClientSetup: Cannot get configuration file with https, will try http...
[5052] 140527.212826.1767: ClientSetup: Download file Setup.cab from server
[5052] 140527.212826.1767: ClientSetup: Making web request:
http://192.168.0.3//connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1
[5052] 140527.212826.2418: ClientSetup: Downloaded file C:\Windows\Temp\ClientDeploymentTempFiles\Setup.cab
[5052] 140527.212826.2418: ClientSetup: The configuration cab is downloaded to C:\Windows\Temp\ClientDeploymentTempFiles\Setup.cab
[5052] 140527.212826.3118: ClientSetup: Adding Server Info data in the Product Registry
[5052] 140527.212826.3218: DnsEnvironmentDetector: GetHostAddresses() returned 192.168.0.3, normal environment
[5052] 140527.212826.3218: ClientSetup: Exiting PreConfigTask.Run()
[5052] 140527.212826.3218: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has TaskStatus=Success
[5052] 140527.212826.3218: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has RebootStatus=NoReboot
[5052] 140527.212826.3218: ClientSetup: Exting ConnectorWizardForm.RunTasks
[5192] 140527.212859.6040: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred
[5192] 140527.212859.6040: ClientSetup: Entering ConnectorWizardForm.RunTasks
[5192] 140527.212859.6040: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask
[5192] 140527.212859.6141: ClientSetup: Entering InstallRootCertTask.Run
[5192] 140527.212859.6191: ClientSetup: Install root cert to local trusted store
[5192] 140527.212859.6290: ClientSetup: Exiting InstallRootCertTask.Run
[5192] 140527.212859.6290: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success
[5192] 140527.212859.6290: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot
[5192] 140527.212859.6290: ClientSetup: Exting ConnectorWizardForm.RunTasks
[5192] 140527.212859.6290: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred
[5192] 140527.212859.6290: ClientSetup: Entering ConnectorWizardForm.RunTasks
[5192] 140527.212859.6290: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask
[5192] 140527.212859.6340: ClientSetup: Entering SetupVpnAndDATask.Run
[5192] 140527.212859.6491: ClientSetup: Deploy VPN profile
[5192] 140527.212859.6891: ClientSetup: Exting SetupVpnAndDATask.Run
[5192] 140527.212859.6891: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Success
[5192] 140527.212859.6991: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot
[5192] 140527.212859.6991: ClientSetup: Exting ConnectorWizardForm.RunTasks
[5192] 140527.212859.6991: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
[5192] 140527.212859.6991: ClientSetup: Entering ConnectorWizardForm.RunTasks
[5192] 140527.212859.6991: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
[5192] 140527.212859.7041: ClientSetup: Entering ValidateUserTask.Run
[5192] 140527.212859.7041: ClientSetup: Validating User
[5192] 140527.212859.7041: ClientSetup: Call MachineIdentityManager.GetMachineStatus
[5192] 140527.212859.7491: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:NetworkError ErrorCode:-1
BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus ---> System.ServiceModel.Security.SecurityNegotiationException: Could not establish trust relationship for the SSL/TLS secure
channel with authority 'marchsbs:65500'. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote
certificate is invalid according to the validation procedure.
at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.WindowsServerSolutions.Devices.Identity.CertWebService.ICertService.GetMachineStatus(GetMachineStatusRequest request)
at Microsoft.WindowsServerSolutions.Devices.Identity.CertWebService.CertServiceClient.GetMachineStatus(String userName, String password, String machineName, MachineStatus& status, Boolean& isAdmin, Int32& maxClientNum, Int32& currentClientNum)
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
--- End of inner exception stack trace ---
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)
[5192] 140527.212859.7491: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\Windows\system32\ipconfig.exe" /all
[5840] 140527.212859.7641: ClientSetup: Standard Ouptput:
[5840] 140527.212859.7641: ClientSetup: Standard Ouptput: Windows IP Configuration
[5840] 140527.212859.7641: ClientSetup: Standard Ouptput:
[5840] 140527.212859.7641: ClientSetup: Standard Ouptput: Host Name . . . . . . . . . . . . : M16
[5840] 140527.212859.7641: ClientSetup: Standard Ouptput: Primary Dns Suffix . . . . . . . : MARCHITECTS.local
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Node Type . . . . . . . . . . . . : Hybrid
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: IP Routing Enabled. . . . . . . . : No
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: WINS Proxy Enabled. . . . . . . . : No
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: DNS Suffix Search List. . . . . . : MARCHITECTS.local
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput:
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Ethernet adapter Ethernet:
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput:
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Connection-specific DNS Suffix . : MARCHITECTS.local
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Description . . . . . . . . . . . : Intel(R) Ethernet Connection I217-LM
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Physical Address. . . . . . . . . : 34-17-EB-9A-DF-A4
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: DHCP Enabled. . . . . . . . . . . : Yes
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Autoconfiguration Enabled . . . . : Yes
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: IPv4 Address. . . . . . . . . . . : 192.168.0.52(Preferred)
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Subnet Mask . . . . . . . . . . . : 255.255.255.0
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Lease Obtained. . . . . . . . . . : Tuesday, May 27, 2014 3:40:29 PM
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Lease Expires . . . . . . . . . . : Wednesday, June 4, 2014 3:40:52 PM
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Default Gateway . . . . . . . . . : 192.168.0.1
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: DHCP Server . . . . . . . . . . . : 192.168.0.3
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: DNS Servers . . . . . . . . . . . : 192.168.0.3
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: NetBIOS over Tcpip. . . . . . . . : Enabled
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput:
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Tunnel adapter isatap.MARCHITECTS.local:
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput:
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Media State . . . . . . . . . . . : Media disconnected
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Connection-specific DNS Suffix . : MARCHITECTS.local
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: DHCP Enabled. . . . . . . . . . . : No
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Autoconfiguration Enabled . . . . : Yes
[5840] 140527.212859.7691: ClientSetup: Standard Ouptput:
[5340] 140527.212859.7691: ClientSetup: Standard Error:
[5192] 140527.212859.7691: ClientSetup: The exit code of the process (C:\Windows\system32\ipconfig.exe) is: 0
[5192] 140527.212859.7691: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\Windows\system32\route.exe" print
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: ===========================================================================
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: Interface List
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 3...34 17 eb 9a df a4 ......Intel(R) Ethernet Connection I217-LM
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 1...........................Software Loopback Interface 1
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 6...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: ===========================================================================
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput:
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: IPv4 Route Table
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: ===========================================================================
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: Active Routes:
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: Network Destination Netmask Gateway Interface Metric
[6116] 140527.212859.7841: ClientSetup: Standard Error:
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.52
10
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 127.0.0.0 255.0.0.0 On-link
127.0.0.1 306
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 127.0.0.1 255.255.255.255 On-link 127.0.0.1
306
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 192.168.0.0 255.255.255.0 On-link 192.168.0.52 266
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 192.168.0.52 255.255.255.255 On-link 192.168.0.52 266
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 192.168.0.255 255.255.255.255 On-link 192.168.0.52 266
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 224.0.0.0 240.0.0.0 On-link
127.0.0.1 306
[5192] 140527.212859.7841: ClientSetup: The exit code of the process (C:\Windows\system32\route.exe) is: 0
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 224.0.0.0 240.0.0.0 On-link 192.168.0.52
266
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 255.255.255.255 255.255.255.255 On-link 192.168.0.52 266
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: ===========================================================================
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: Persistent Routes:
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: None
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput:
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: IPv6 Route Table
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: ===========================================================================
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: Active Routes:
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: If Metric Network Destination Gateway
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 1 306 ::1/128 On-link
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: 1 306 ff00::/8 On-link
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: ===========================================================================
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: Persistent Routes:
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput: None
[3080] 140527.212859.7841: ClientSetup: Standard Ouptput:
[5192] 140527.212859.7841: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\Windows\system32\nslookup.exe" MARCHSBS
[5340] 140527.212859.7991: ClientSetup: Standard Ouptput: Server: marchsbs.marchitects.local
[5340] 140527.212859.7991: ClientSetup: Standard Ouptput: Address: 192.168.0.3
[5340] 140527.212859.7991: ClientSetup: Standard Ouptput:
[5340] 140527.212859.7991: ClientSetup: Standard Ouptput: Name: MARCHSBS.MARCHITECTS.local
[5340] 140527.212859.7991: ClientSetup: Standard Ouptput: Address: 192.168.0.3
[5340] 140527.212859.7991: ClientSetup: Standard Ouptput:
[6116] 140527.212859.7991: ClientSetup: Standard Error:
[5340] 140527.212859.7991: ClientSetup: Standard Ouptput:
[5192] 140527.212859.7991: ClientSetup: The exit code of the process (C:\Windows\system32\nslookup.exe) is: 0
[5192] 140527.212859.7991: ClientSetup: Set CD Fail reason 10 for SQM in ClientDeployment.exe
[5192] 140527.212859.8041: ClientSetup: RecordClientDeploymentFailReason: Save registry failed in ClientDeployment.exe : System.UnauthorizedAccessException: Cannot write to the registry key.
at Microsoft.Win32.RegistryKey.EnsureWriteable()
at Microsoft.Win32.RegistryKey.CreateSubKeyInternal(String subkey, RegistryKeyPermissionCheck permissionCheck, Object registrySecurityObj, RegistryOptions registryOptions)
at Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RecordClientDeploymentFailReason(UInt32 failReason)
[5192] 140527.212859.8041: ClientSetup: Exiting ValidateUserTask.Run
[5192] 140527.212859.8041: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed
[5192] 140527.212859.8041: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
[5192] 140527.212859.8041: ClientSetup: Exting ConnectorWizardForm.RunTasks
[3808] 140527.212910.2736: ClientSetup: Back from the Client Deployment Wizard
[3808] 140527.212910.2786: ServerDiscovery:HostsFileUpdater: Removing hosts file entry: MARCHSBS
[3808] 140527.212910.2836: ClientSetup: Saving Wizard Data
[3808] 140527.212910.2836: ClientSetup: End of ClientDeploy: ErrorCode=1603Hooray!
testing the certificates and not finding any errors, I stumbled across the Basic Settings button that highlighted an authorization problem. I manually set the authorization to the admin account and by problems disappeared. I am now able to successfully
join client PCs to the domain thru the //Server/connect method. -
Hi,
I have enabled ssl on my mysql server and am using useSSL=true&requireSSL=true in my jdbc connector url.
I am getting the following error:
The root cause was that: com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** com.mysql.jdbc.CommunicationsException MESSAGE: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** javax.net.ssl.SSLHandshakeException MESSAGE: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target STACKTRACE: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1591) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187) at
If anyone had any success connecting to mysql via ssl I would appreciate any help.
Thanks!I used the mysql odbc connector with the certificate and it worked fine so
the problem is not the certificate.
2009/4/8 Alexei Yakovenko <[email protected]>
drieh,
>
A new message was posted in the thread "mysql connector & ssl":
>
http://forums.adobe.com/message/1877560#1877560
>
Author : Alexei Yakovenko
Email : [email protected]
Profile : http://forums.adobe.com/people/injun%20%5B576871%5D
>
Message: -
I have been reading a little into JMX but I am not sure if it is what I am looking for. What I am looking to do is have a Server in my network and a set of clients running on different PC's within my network. I want to monitor things the client apps are doing and send the data off the my server which will do something with the collected data (ie write to file or DB).
is JMX the right type of solution for something like this?JConsole is an example (perhaps the best known and most commonly used example) of a JMX Client that is capable of remotely accessing instrumented JMX MBeans hosted on a remote JMX server. You are correct that you'd essentially replace JConsole with your own client code for accessing these JMX MBeans. A thorough introduction to how to do this is available in the [JMX Tutorial|http://java.sun.com/javase/6/docs/technotes/guides/jmx/tutorial/tutorialTOC.html] under the section [JMX Connectors|http://java.sun.com/javase/6/docs/technotes/guides/jmx/tutorial/connectors.html#wp5529]. Wherever you see reference to an "RMI Client" or "JMX Client," you can think of it as being the same role JConsole plays but with your own code. A resource that I found particularly useful when learning about developing my own JMX Client is the [Java Tutorial - JMX: Remote Management|http://java.sun.com/docs/books/tutorial/jmx/remote/index.html] lesson. While the section [Creating a Custom JMX Client|http://java.sun.com/docs/books/tutorial/jmx/remote/custom.html] is what you're specifically looking for, I recommend reading the entire "Remote Management" lesson because it is fairly small, very straight-forward, and gives a complete picture. You'll likely want to download the associated code to get an overall picture of how it all goes together.
-
URL for posting Orders to XI system.
Could somebody send me an example of the <u>simpliest possible way</u> that a (external) URL would look like for a Customer to send an XML Order to my XI system ?
For instance in our Business Connector we give this URL to our Customers
https: / /<bcserver.xyz.com>:9999/invoke/XML/Handle_XCBL_Post
the content-type header is text/xml and it contains an XML document in the body.
What is the equivalent in XI ? Do I need the Customer to build a large URL with namespaces, servicenames, party,clients etc etc. Notice that the Business Connector URL currently being used by our various different Customer is nice and simple (as once the Order is received by that service the contents are interrogated for routings etc).Hi ,
If you want to send from remote sever you will have to create URL like the following which includes namespace and sender service etc...
http://172.16.17.22:8001/sap/xi/adapter_plain?namespace=http%3A//swift.com/us/GenericJMS&interface=MIOA_GenericJMS_v1&service=HTTP_Service_Swift&party=&agency=&scheme=&QOS=EO&sap-user=USERNAME&sap-password=PASSWORD&sap-client=100&sap-language=EN
The above URL directly sends the XML file data to XI Integration Engine.
If you want to send the XML data from the Webservice...
The general format of the url is:
http://url:port/XISOAPAdapter/MessageServlet?channel=:service:channel
Regards, -
In Admin log file , i get an error
"The administration server was unable to establish JMS connectivity with the managedserver at the JMX service URL of serviceURL"
The managed server state are unknown.
how do i fix this to control my managed server through admin server.So your managed servers were originally started by nodemanager from the original admin server, but now can't be reached from the backup admin server ?
I'm not sure that you can "transfer" control of the domain - while its managed servers are running - from one admin server to another without restarting the managed servers.
But here's what I would try:
remove the boot.properties and startup.properties files from the managed server's data/nodemanager directory
then kill the java process of the managed server to allow the nm process to perform a restart
Maybe you are looking for
-
ASA 5505 version 9.1 in extended access-list I can add interface name as destination??
Hi All, I'm adding extended ACL on the ASA 5505 version 9.1 and found that in the source or destination field I can specify interface name instead of object, host/network but can't find it documented anywhere and what is the behavior of that? access-
-
Error -54 - can't find any reference to this but it's the error I'm getting!
I am running Mac OSX 10.7.5 and iTunes 11.0.3 (42). Suddenly my iTunes is giving the following error message: Unable to save iTunes file -error 54 I have searched for this error code and don't see any other users talking about it. Does anyone know wh
-
RFWT0010 withholding tax type and tax code change in vendor master problem
Hi Due to some reasons I need to change the withholding tax type and tax code in vendor master. When i am running the report RFWT010,After changing the tax type and tax code in vendor master...the list contains no items. eventhough there are 14 line
-
Upgrade from 4.6C to ECC-6 Points will be awarded.
Dear Guys Can any body provide me documentation for the preparation of upgrade from 4.6C to ECC-6.We have done many modification in standard system and exits how can we upgrade those in ECC6. Thanks
-
Black line sketch renderings printing with teal or magenta
Aloha, When I print architectural drawings with my DesignJet 110 I sometime place computer generated sketch renderings in with the architectural plans which are vector line drawings. The architectural line drawings and the sketch renders are compute