Error : Connecting to Client

Hi
While connecting to client using server and repository am getting an error : " WinSock error on connect ".
This is happening with particular reporsitory, kindly advise
1. what will be exact reason and
2. how to overcome the same?
thanks
Alexander

Hi Alexander,
Whenever you get WinSock error, try to unload & unmount the repository, stop the server and start server and then mount & load the repository.
Whenever the connection to backend database is lost, this error pops up.
Good Luck.
Rajani Kumar

Similar Messages

Error connecting JCO.Client

Hello!
I've got a little problem with Adaptive RFC calls: After exactly 10 times executing my call I always get the following Exception:
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
Has anybody by any chance got an idea why or how to handle this problem?
Thank you very much in advance!
Best Regards

Hi
Well its a simple problem of connection pooling. In your JCO connection settings change the maximum connections to 200. It will work.
well what i would advice is that After you execute the Model please release the connection. The reason you are getting this JCO Client null is because the connection is not getting released.
When you say the following code
wdContext.current<BAPI_INPUT>.modelObject().execute();
//Get the reference to the model and release the connection
If your Model name is say "MO_Mymodel"
then
MO_Mymodel model = (MO_Mymodel) WDModelFactory.getModelInstance(MO_Mymodel.class);
model.disconnectIfAlive();
This should release your connections. Also ensure you release the connections even if there is a exception :).
Hope that helps you.
regards
ravi

Error connecting to Client Sys. DB

Hi
i am trying to create Datasource in my my localhost for the
client's database.
i am able to connect to through the SQL Server Enterprise
Manager, but when i am creating datasource i am getting following
error:
Connection verification failed for data source: dev1
java.sql.SQLException: [Macromedia][SQLServer JDBC
Driver][Macromedia][SQLServer JDBC Driver]The requested instance is
either invalid or not running.
The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer JDBC Driver][Macromedia][SQLServer JDBC
Driver]The requested instance is either invalid or not
running.

This assumes you have CFMX 7.01 and SQL Server 2000 installed
on Windows 2000/XP/2003
This may help:
• Install SQL2000 SP3 ( or latest patch)
• Create an ODBC DSN within the Microsoft ODBC Manager
to make certain the connections are working at this level.
• Create a new SQL2000 user with administrative
permissions, go to the user/admin properties and allow permissions
at all levels for the applicable database (not all dbs).
• Create the JDBC DSN in Coldfusion, use the server
name that is listed in the Enterprise Manager.

OATS: Error Creating datasource client connection

Hi All
When i try to add montiors in the OATS controller machine i am getting the following error .
Error while creating datasource client connection.
i am trying to monitor a linux machine. I am able to ping that machine from controller.
when i tried to do
plink.exe username@hostname i am getting the following error ...
FATAL error : Network error : Connection timed out..
Can anyone please help me on this??
Thanks

I'm not sure if this is the same problem but the following thread may help (mentioning the ports that may need opening on your firewalls)...
Re: What are the various ports used by OLT?
oracle.port.rmi=4444
oracle.port.http=8088
oracle.port.empstart=9001
oracle.port.uil2=7071
oracle.port.dataCollector=7073
oracle.port.webservice=8083
oracle.port.jndi.rmi=1098
oracle.port.jndi=1099
oracle.port.https=8433
* 9001 (Agent Comunication Port)
* 1099 (Datacollector Comunication Port)
* 8088 (for running OpenScript scripts)

While connecting from Client to EJB , LookUp Error is Comming...

Hi All
I am working with Oracle Application Server 10g.
Here I downloaded one helloworld session bean from oracle site.
I am able to deploy .ear file.
But when I am connecting bean using client...
I am getting following error:
D:\helloworld>ant run
Buildfile: build.xml
init:
setup:
cli-classes:
[javac] Compiling 1 source file to D:\helloworld\build\helloworld\helloworld-client
cli-descriptor:
cli-jar:
[jar] Building jar: D:\helloworld\dist\helloworld-client.jar
run:
[java] client started...
[java] java.lang.InstantiationException: Error communicating with server: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
[java] java.net.ConnectException: Connection refused: connect; nested exception is:
[java] javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
[java] java.net.ConnectException: Connection refused: connect [Root exception is java.net.ConnectException: Connection refused: connect]
[java] at com.evermind.server.ApplicationClientContext.createContext(ApplicationClientContext.java:63)
[java] at com.evermind.server.ApplicationClientInitialContextFactory.getInitialContext(ApplicationClientInitialContextFactory.java:145)
[java] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
[java] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
[java] at javax.naming.InitialContext.init(InitialContext.java:219)
[java] at javax.naming.InitialContext.<init>(InitialContext.java:175)
[java] at hello.HelloClient.main(HelloClient.java:25)
[java] NamingException: Error reading application-client descriptor: Error communicating with server: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
[java] java.net.ConnectException: Connection refused: connect; nested exception is:
[java] javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
[java] java.net.ConnectException: Connection refused: connect [Root exception is java.net.ConnectException: Connection refused: connect]
I used the following JNDI Configurations:
java.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory
java.naming.provider.url=ormi://localhost:23791/helloworld
Pls Post your results....
With Regards
Kumar

Try this:
java.naming.factory.initial=oracle.j2ee.rmi.RMIInitialContextFactory

Error connecting using JCO.Client: null

Hi,
I created a WD app which uses the RFC FM. I followed How-To-build-webdynpro.pdf document to create the WD and trying to deploy and run, I see the view page but when I trigger the action via button UI element I get following error as exception in the try catch block of execute method
In the NWA I see
Could not create JCOClientConnection for logical System: 'WD_MODELDATA_DEST' - Model
An exception has occurred: Erorr accessing cache [region]='XCM_SESSION_SCOPE'.
[EXCEPTION]
com.sap.isa.core.cache.Cache$Exception: Cannot return access for region 'XCM_SESSION_SCOPE'. Cache is not ready
I'm using following existing JCO definition by configuring them with correct parameters. Tested them successfully
WD_RFC_METADATA_DEST
WD_MODELDATA_DEST
What am I missing? In SM04 tcode I see 2 connections are opened with 2 Megabyte not released for a long time. I think if connections are released correctly it should drop to 1 megabyte. Is there anything that I need to do just after execute method as shown below (I have replaced function module with <FM> in below code)
try {
         wdContext.node<FM>_Input().current<FM>_Get_InputElement().modelObject().execute();
     } catch(Exception exception) {
          msgMgr.reportException(exception.getLocalizedMessage(), false);
      wdContext.nodeOutput().invalidate();
      msgMgr.reportSuccess("Success");
The error is in the catch block which is displayed on the view page.
Thanks
Praveen
I modified the above code and put in finally block to close the connections as follows, please let me know if this is OK. I still get error message as "Error connecting using JCO.Client: null" but no additional connections in the SM04 after adding finally block.
try {
         wdContext.node<FM>_Input().current<FM>_Get_InputElement().modelObject().execute();
     } catch(Exception exception) {
          msgMgr.reportException(exception.getLocalizedMessage(), false);
     }finally {
          // disconnect the connection
          wdContext.<FM>_Get_InputElement().modelObject().modelInstance().disconnectIfAlive();
Edited by: Praveen11 on Oct 5, 2009 9:06 AM

Thanks Satish.
The issue is resolved. I think it was to do with permission, as I was running directly from NWDS deploy and run the session didn't have proper authorisation or something that was causing this error.
When I copy pasted the URL in the correct browser session window I got no error and function module was successfully executed.   However the issue now is that values are not showing up in the view may be to do with mapping context or model I'll review and post back as different thread.
Thanks
Praveen

Error connection using JCO.Client

Hello all,
I got the following problem <b>"Error connection using JCO.Client"</b> and don't know what's wrong. All connections works at the content administration when I test the connection.
Can anyone help me please?
Best regards
Petra

Hi,
I almost tested the JCO connection with the 'test' button successfully at the content administrator. I tested again and it still works. And I have a stand alone webdynpro application (no portal).
Now I got the following error message after completing the coding with 'e.printStackTrace().'.
<i>
"Error connection using JCO.Client:null"
"[Ljava.lang.StackTraceElement:@60db08"
"Could not create JCOClientConnection for logical System:WD_MODELDATA_DEST - Model: class impersonalaccout.intro.model.Z_Fh0002_Datenverwaltung.Please assure that you have configured the RFC connections and/or logical System"
"com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException:Error connection using JCO.Client:null"
"com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException: Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model:class impersonalaccout.intro.model.Z_Fh0002_Datenveraltung.Please ***"</i>
Can anyone explaine me what's wrong?
Bye
Petra

Error connection using JCO.Client :null

Hi,
I have small doubt in JCO connection, can any one help me.
In WebDynpro application some time we are getting exception like Error connection using JCO.client : null.
Connection :200 we are maintained in JCO configuration.
If I call one RFC useing JCO it will created a session or connection to ECC server, because we are getting exception in server too many sessions to ECC server.
Write now we are not using any code to close the connection like.
SaveModel svModel = (SaveModel)WDModelFactory.getModelInstance(SaveModel.class);
svModel.disconnectIfAlive();
If we use the above code it will close the connection or sessions.
Is it recommended to write the code in every RFC calls or in final block of all RFC calls ?
Regards,
Satya.

Hi Satya
/message/1944647#1944647 [original link is broken]
/message/8499#8499 [original link is broken]
Please go through this link.Hope it will be helpful for you
Regards
Ruturaj

WDDynamicRFCExecuteException: Error connecting using JCO.Client: null

Hi
This is a common problem,I have seen many threads , but following them did not solve my problem.
I have the JCOs tested successful from WD Admin. When I create a sample WDJ application with RFC model and deploy it to the server, I get
Exception:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecution: Error connecting using JCO.Client: null.
I have checked my binding , I have only one input parameter and the code is
      wdComponentAPI.getMessageManager().reportSuccess("Inside wdInit in Component ctrller");
      Z_Plm44_Obsoleteimpactanalysis_Input input = new Z_Plm44_Obsoleteimpactanalysis_Input();
     wdContext.nodeZ_Plm_Input().bind(input);
     wdContext.createZ_Plm_InputElement(input).setV_Type(wdContext.currentZ_Plm_InputElement().getV_Type());
Also I have implemented closing the connection
disconnectifalive
I contacted the basis team... they tell me that everything is fine from their end. they have tried increasing the JCO connection pools.
Thanks for your help in advance
Karthika

Hi Karthika
Check this pdf and try to catch WDDynamicRFCExecution in catch block.
Please put your code in try catch and also import com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecution in your code;
http://www.sappro.com/downloads/WebDynproJava.pdf
Re: User has no RFC authorization for function group.
Hope this will help you.
thanks
Arun Jaiswal

Error in Connecting to BAPI (Error connecting using JCO.Client: null)

Hi,
    I am trying to connect to a BAPI to extract data. However, I am getting this error
    Error connecting using JCO.Client: null
    Pls explain the meaning of the error and solution to the problem
TIA
Himanshu

Hi,
This means you are getting error while executing your model. its not able to use the JCO's.
as I asked previously check your JCO status... its up and running????
Here are some threads having same problem
URGENT :Error connecting using JCO.Client: null
Model and MetaData configarations in JCO Connection
Exception while executing
PradeeP
Edited by: pradeep bondla on Jul 31, 2008 11:53 AM

Error connecting using JCO.Client: null in xRPM in EP

Hi Friends,
I am getting the following error in xRPM through EP
"Error connecting using JCO.Client: null"
I can't enter xRPM, but I can enter other Business packages iViews.
The problem is intermittant and user specific.
Can you pls provide any input on this ?
thanks in advance and warm regards
Purnendu

Hi Flavio,
Thanks for your reply.
The user is created both in the backend as well as in portal.
The roles are also ok.
The error I am getting only while accessing xRPM iViews.
If I restart the instance the error is removed. But it reappears again may be after few days.
This error is intermittant.
May be it is related to the Maximum Number of JCo connections in the WebDynpro configuration.
But I don't have much idea on that.
Can you pls provide any help on this.
Warm regards
Purnendu

Error connecting to the SAP SRV on Windows 2008 Server platform

Hi All
We have a problem with one of our clients they bought a new sbs windows server 2008 and we loaded sql 2005 and sap b1 SP01 PL07.
When we did the SBO install we experience connection issues and we created odbc connection on the server using named pipes and tcp/ip (used both server name and Ip address).
We also configured the server in configuration manager and we managed to login and solved the slow system connection issue. We also created odbc connection on the client machines. (Machine are on a workgroup and users have administration access on all machines),we also installed native client on all machines.
After the first batch of client installs we managed to have connection, they were other computers which were left out during the first client install and now the client want to do the remaining machines connected to SBO. On every machine that we install now we get the same error :-
*Connection failed:
SQLState:'08001'
SQl Server error:10060
[Microsoft][SQL Native Client] TCP Provider: A connection attempt failed because the connected party didnot properly repsond after a period of time, or established connection failed because connected host has failed to respond.
Connectioin failed:
SQLState:'HYT00'
SQL Server Error:0
[Microsoft][SQL Native Client]Login timeout expired
Connection failed:
SQLState:'08001'
SQL Server Error: 10060
[Microsoft][SQL Native client] An error has occurred while establishing a connection to the server. When connecting to the sql server 2005, this failure may be cause by the that*
Please help as most user who need access can't login and they are the main users.
rgds,
Bongani Dlamini

Hi Eric,
yes we are using Windows 2008 SBS for the SAP EHP4 FOR SAP ERP 6.0/NW7.01 installation.
we tried to create the key but it says access is denied.
Actual thing is we got the server with Windows 2008 server 64 bit SBS (standard FE) with Domain Controller (DC) configuration.
We have removed the DC using dcpromo to convert into Wokgroup and tried the SAP installation.
I hope you got the idea and please let me know any further suggestions or it is the problem with the license.
Thanks & Regards,
Prabhu Reddy.

Connecting Java client to SSL server with existing certificates

I am currently trying to connect my Java client to an existing server application
written in C++. I have been provided the needed certificates (root.pem, server.pem,
and client.pem). My code simply creates a SSLSocket and then attempts to read
from it. Something goes wrong during the handshake process and I get a SSLHandshakeException. The certificates have been added to the keystore
I am using, and I do not know any other action to take.
Here is the debug output:
setting up default SSLSocketFactory
use default SunJSSE impl class: com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
class com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl is loaded
keyStore is :
keyStore type is : jks
keyStore provider is :
init keystore
init keymanager of type SunX509
trustStore is: keystore.jks
trustStore type is : jks
trustStore provider is :
init truststore
adding as trusted cert:
Subject: [email protected], CN=Employee, OU=test, O=company-USA, L=City, ST=AL, C=US
Issuer: [email protected], CN=company Employee, OU=test, O="company, Inc.", L=City, ST=AL, C=US
Algorithm: RSA; Serial number: 0xb40b909f74d167aa
Valid from Tue Sep 12 09:42:01 CDT 2006 until Thu Oct 12 09:42:01 CDT 2006
adding as trusted cert:
Subject: [email protected], CN=Employee, OU=test, O="company, Inc.", L=City, ST=AL, C=US
Issuer: [email protected], CN=ISAC Employee, OU=test, O="company, Inc.", L=City, ST=AL, C=US
Algorithm: RSA; Serial number: 0xb40b909f74d167ab
Valid from Tue Sep 12 09:49:12 CDT 2006 until Thu Oct 12 09:49:12 CDT 2006
adding as trusted cert:
Subject: [email protected], CN=company Employee, OU=test, O="company, Inc.", L=City, ST=AL, C=US
Issuer: [email protected], CN=company, OU=test, O="company, Inc.", L=City, ST=AL, C=US
Algorithm: RSA; Serial number: 0xf6e3ada87dc4004f
Valid from Tue Sep 12 09:40:32 CDT 2006 until Thu Oct 12 09:40:32 CDT 2006
init context
trigger seeding of SecureRandom
done seeding SecureRandom
instantiated an instance of class com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
SSL socket created
%% No cached client session
*** ClientHello, TLSv1
RandomCookie: GMT: 1158089181 bytes = { 138, 112, 170, 91, 246, 86, 216, 146, 160, 188, 243, 154, 238, 132, 33, 219, 251, 3, 93, 25, 191, 247, 41, 14, 99, 135, 130, 23 }
Session ID: {}
Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
Compression Methods: { 0 }
[write] MD5 and SHA1 hashes: len = 79
0000: 01 00 00 4B 03 01 45 07 0A DD 8A 70 AA 5B F6 56 ...K..E....p.[.V
0010: D8 92 A0 BC F3 9A EE 84 21 DB FB 03 5D 19 BF F7 ........!...]...
0020: 29 0E 63 87 82 17 00 00 24 00 04 00 05 00 2F 00 ).c.....$...../.
0030: 35 00 33 00 39 00 32 00 38 00 0A 00 16 00 13 00 5.3.9.2.8.......
0040: 09 00 15 00 12 00 03 00 08 00 14 00 11 01 00 ...............
Client Thread, WRITE: TLSv1 Handshake, length = 79
[write] MD5 and SHA1 hashes: len = 107
0000: 01 03 01 00 42 00 00 00 20 00 00 04 01 00 80 00 ....B... .......
0010: 00 05 00 00 2F 00 00 35 00 00 33 00 00 39 00 00 ..../..5..3..9..
0020: 32 00 00 38 00 00 0A 07 00 C0 00 00 16 00 00 13 2..8............
0030: 00 00 09 06 00 40 00 00 15 00 00 12 00 00 03 02 .....@..........
0040: 00 80 00 00 08 00 00 14 00 00 11 45 07 0A DD 8A ...........E....
0050: 70 AA 5B F6 56 D8 92 A0 BC F3 9A EE 84 21 DB FB p.[.V........!..
0060: 03 5D 19 BF F7 29 0E 63 87 82 17 .]...).c...
Client Thread, WRITE: SSLv2 client hello message, length = 107
[Raw write]: length = 109
0000: 80 6B 01 03 01 00 42 00 00 00 20 00 00 04 01 00 .k....B... .....
0010: 80 00 00 05 00 00 2F 00 00 35 00 00 33 00 00 39 ....../..5..3..9
0020: 00 00 32 00 00 38 00 00 0A 07 00 C0 00 00 16 00 ..2..8..........
0030: 00 13 00 00 09 06 00 40 00 00 15 00 00 12 00 00 .......@........
0040: 03 02 00 80 00 00 08 00 00 14 00 00 11 45 07 0A .............E..
0050: DD 8A 70 AA 5B F6 56 D8 92 A0 BC F3 9A EE 84 21 ..p.[.V........!
0060: DB FB 03 5D 19 BF F7 29 0E 63 87 82 17 ...]...).c...
Client Thread, received EOFException: error
Client Thread, handling exception: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
Client Thread, SEND TLSv1 ALERT: fatal, description = handshake_failure
Client Thread, WRITE: TLSv1 Alert, length = 2
[Raw write]: length = 7
0000: 15 03 01 00 02 02 28 ......(
Client Thread, called closeSocket()
Error: Remote host closed connection during handshake
Thread-4, handling exception: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake

(I am the original poster of this message, I had to create a new username though).
The original problem had to do with incompatibilities with the protocol and/or cipher suites
used. Now, the client and server perform most of the handshake process, but something
goes wrong as the server requests the client certificate. In other words, the server requires
mutual authentication, but for some reason it seems like my JSSE client won't send over
it's client certificate. I don't get any type of bad certificate exceptions, so I'm not sure
where the source of the error lies.
Updated output:
setting up default SSLSocketFactory
use default SunJSSE impl class: com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
class com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl is loaded
keyStore is : keystore
keyStore type is : jks
keyStore provider is :
init keystore
init keymanager of type SunX509
trustStore is: truststore
trustStore type is : jks
trustStore provider is :
init truststore
adding as trusted cert:
Subject: [email protected], CN=Employee, OU=default, O="default Inc.", L=default, ST=AL, C=US
Issuer: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Algorithm: RSA; Serial number: 0xb40b909f74d167ab
Valid from Tue Sep 12 09:49:12 CDT 2006 until Thu Oct 12 09:49:12 CDT 2006
adding as trusted cert:
Subject: [email protected], CN=default-Server, OU=HawkEye, O=default, L=default, ST=AL, C=US
Issuer: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Algorithm: RSA; Serial number: 0xb40b909f74d167ac
Valid from Tue Sep 12 14:42:28 CDT 2006 until Thu Oct 12 14:42:28 CDT 2006
adding as trusted cert:
Subject: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Issuer: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Algorithm: RSA; Serial number: 0xf6e3ada87dc4004f
Valid from Tue Sep 12 09:40:32 CDT 2006 until Thu Oct 12 09:40:32 CDT 2006
init context
trigger seeding of SecureRandom
done seeding SecureRandom
instantiated an instance of class com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
%% No cached client session
*** ClientHello, TLSv1
RandomCookie: GMT: 1158242806 bytes = { 71, 195, 185, 44, 86, 96, 14, 11, 171, 76, 105, 135, 136, 114, 53, 54, 137, 75, 202, 254, 112, 208, 240, 91, 199, 246, 175, 207 }
Session ID: {}
Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
Compression Methods: { 0 }
Client Thread, WRITE: TLSv1 Handshake, length = 79
Client Thread, READ: TLSv1 Handshake, length = 74
*** ServerHello, TLSv1
RandomCookie: GMT: 1158242807 bytes = { 63, 93, 48, 73, 98, 251, 160, 215, 61, 110, 246, 12, 5, 209, 95, 194, 152, 193, 0, 181, 135, 26, 150, 174, 52, 92, 56, 250 }
Session ID: {83, 31, 134, 30, 76, 200, 183, 120, 7, 94, 26, 65, 186, 91, 197, 25, 10, 193, 94, 220, 198, 250, 162, 153, 6, 89, 12, 250, 66, 105, 249, 211}
Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Compression Method: 0
%% Created: [Session-1, TLS_RSA_WITH_AES_128_CBC_SHA]
** TLS_RSA_WITH_AES_128_CBC_SHA
Client Thread, READ: TLSv1 Handshake, length = 1903
*** Certificate chain
chain [0] = [
Version: V3
Subject: [email protected], CN=Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 1024 bits
modulus: 164546130673614659100546464587508805401937082626997447139358150641653094778762702643605529386963945060462618417820295217144739538713137107756847225226998964727905246706969036839701385553183842454061172884072035749790213037240682893878786969498404371282074360019097248835858617183835587887295684928062301303789
public exponent: 65537
Validity: [From: Tue Sep 12 09:49:12 CDT 2006,
               To: Thu Oct 12 09:49:12 CDT 2006]
Issuer: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
SerialNumber: [    b40b909f 74d167ab]
Certificate Extensions: 4
[1]: ObjectId: 2.16.840.1.113730.1.13 Criticality=false
Extension unknown: DER encoded OCTET string =
0000: 04 1F 16 1D 4F 70 65 6E 53 53 4C 20 47 65 6E 65 ....OpenSSL Gene
0010: 72 61 74 65 64 20 43 65 72 74 69 66 69 63 61 74 rated Certificat
0020: 65 e
[2]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: C8 EA 02 93 42 9E 44 D1 55 7D 2D 32 4B 9B 1C 6D ....B.D.U.-2K..m
0010: 63 6B 73 82 cks.
[3]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: 2C BC 66 DC 06 BA 62 79 3B 1A 20 92 E0 81 71 A0 ,.f...by;. ...q.
0010: 0D 05 3C 95 ..<.
[[email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US]
SerialNumber: [    f6e3ada8 7dc4004f]
[4]: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
CA:false
PathLen: undefined
Algorithm: [SHA1withRSA]
Signature:
0000: BF 60 5A 67 3E E6 F0 92 4F E4 81 6D 71 0A 2E E8 .`Zg>...O..mq...
0010: F3 59 A1 87 7B D1 3A 7A CB FF D6 39 63 79 B6 82 .Y....:z...9cy..
0020: 2A 22 D0 46 51 30 6B 2A 61 6B A0 4C F0 3B CE 5B *".FQ0k*ak.L.;.[
0030: 9C 1D 46 CB D7 C2 B2 23 E2 A5 06 CD 12 F8 A9 CB ..F....#........
0040: B5 A2 43 B1 06 4C 42 B5 67 F2 DF 50 6B BC 8A 5E ..C..LB.g..Pk..^
0050: 95 0D F3 2A 73 A8 5A C8 55 77 D7 36 74 16 9E 05 ...*s.Z.Uw.6t...
0060: 85 C6 DC 3C 44 D3 06 5E 47 0C 1F 80 40 30 C7 D8 ...<D..^G...@0..
0070: 8C 27 FF B9 0C 71 EB D4 31 5C 1F 15 A1 23 6F A2 .'...q..1\...#o.
chain [1] = [
Version: V3
Subject: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 1024 bits
modulus: 140862286957037297158683104484469503810921697537964422595574798580128510755934413463045842414762254029728885690233847950678735782281077619629628663140568366247472189890316085560712610474766899389736269383565795688749374256479726939861138704211990111677657317335172626254520371267441364353295155431963634875809
public exponent: 65537
Validity: [From: Tue Sep 12 09:40:32 CDT 2006,
               To: Thu Oct 12 09:40:32 CDT 2006]
Issuer: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
SerialNumber: [    f6e3ada8 7dc4004f]
Certificate Extensions: 3
[1]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: 2C BC 66 DC 06 BA 62 79 3B 1A 20 92 E0 81 71 A0 ,.f...by;. ...q.
0010: 0D 05 3C 95 ..<.
[2]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: 2C BC 66 DC 06 BA 62 79 3B 1A 20 92 E0 81 71 A0 ,.f...by;. ...q.
0010: 0D 05 3C 95 ..<.
[[email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US]
SerialNumber: [    f6e3ada8 7dc4004f]
[3]: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
CA:true
PathLen:2147483647
Algorithm: [SHA1withRSA]
Signature:
0000: AB 84 38 1F 7B 71 D8 87 FF 24 DB C2 7E DC D0 0B ..8..q...$......
0010: 60 60 14 A8 F8 D5 46 AD 6B FC 33 90 6F 43 08 17 ``....F.k.3.oC..
0020: AE 2B EE 6C 2B 29 85 E2 A6 67 EE 5D A4 61 F3 9E .+.l+)...g.].a..
0030: E7 CA B1 27 F9 11 36 ED 93 05 7B E1 20 90 57 B5 ...'..6..... .W.
0040: C6 F9 8A 9D 50 CD B3 4A 54 DC 1B 52 EC EA 7A 0B ....P..JT..R..z.
0050: B6 E6 95 FD DD 80 BE 66 F0 77 F4 E7 9A 8A A3 EF .......f.w......
0060: 9B 68 57 0C 9C 4B 4C C0 24 C5 34 16 D3 8E 45 27 .hW..KL.$.4...E'
0070: CA 23 F1 E0 C5 5E FB FB AA 1C 21 6E CB 5B 57 D9 .#...^....!n.[W.
Found trusted certificate:
Version: V3
Subject: [email protected], CN=Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 1024 bits
modulus: 164546130673614659100546464587508805401937082626997447139358150641653094778762702643605529386963945060462618417820295217144739538713137107756847225226998964727905246706969036839701385553183842454061172884072035749790213037240682893878786969498404371282074360019097248835858617183835587887295684928062301303789
public exponent: 65537
Validity: [From: Tue Sep 12 09:49:12 CDT 2006,
               To: Thu Oct 12 09:49:12 CDT 2006]
Issuer: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
SerialNumber: [    b40b909f 74d167ab]
Certificate Extensions: 4
[1]: ObjectId: 2.16.840.1.113730.1.13 Criticality=false
Extension unknown: DER encoded OCTET string =
0000: 04 1F 16 1D 4F 70 65 6E 53 53 4C 20 47 65 6E 65 ....OpenSSL Gene
0010: 72 61 74 65 64 20 43 65 72 74 69 66 69 63 61 74 rated Certificat
0020: 65 e
[2]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: C8 EA 02 93 42 9E 44 D1 55 7D 2D 32 4B 9B 1C 6D ....B.D.U.-2K..m
0010: 63 6B 73 82 cks.
[3]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: 2C BC 66 DC 06 BA 62 79 3B 1A 20 92 E0 81 71 A0 ,.f...by;. ...q.
0010: 0D 05 3C 95 ..<.
[[email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US]
SerialNumber: [    f6e3ada8 7dc4004f]
[4]: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
CA:false
PathLen: undefined
Algorithm: [SHA1withRSA]
Signature:
0000: BF 60 5A 67 3E E6 F0 92 4F E4 81 6D 71 0A 2E E8 .`Zg>...O..mq...
0010: F3 59 A1 87 7B D1 3A 7A CB FF D6 39 63 79 B6 82 .Y....:z...9cy..
0020: 2A 22 D0 46 51 30 6B 2A 61 6B A0 4C F0 3B CE 5B *".FQ0k*ak.L.;.[
0030: 9C 1D 46 CB D7 C2 B2 23 E2 A5 06 CD 12 F8 A9 CB ..F....#........
0040: B5 A2 43 B1 06 4C 42 B5 67 F2 DF 50 6B BC 8A 5E ..C..LB.g..Pk..^
0050: 95 0D F3 2A 73 A8 5A C8 55 77 D7 36 74 16 9E 05 ...*s.Z.Uw.6t...
0060: 85 C6 DC 3C 44 D3 06 5E 47 0C 1F 80 40 30 C7 D8 ...<D..^G...@0..
0070: 8C 27 FF B9 0C 71 EB D4 31 5C 1F 15 A1 23 6F A2 .'...q..1\...#o.
Client Thread, READ: TLSv1 Handshake, length = 13
*** CertificateRequest
Cert Types: RSA, DSS,
Cert Authorities:
*** ServerHelloDone
*** Certificate chain
*** ClientKeyExchange, RSA PreMasterSecret, TLSv1
Random Secret: { 3, 1, 27, 159, 38, 131, 132, 24, 47, 148, 161, 90, 7, 39, 189, 28, 178, 156, 20, 151, 220, 192, 239, 182, 115, 234, 99, 225, 68, 250, 199, 173, 96, 181, 78, 180, 238, 37, 243, 72, 19, 91, 249, 11, 49, 83, 1, 150 }
Client Thread, WRITE: TLSv1 Handshake, length = 141
SESSION KEYGEN:
PreMaster Secret:
0000: 03 01 1B 9F 26 83 84 18 2F 94 A1 5A 07 27 BD 1C ....&.../..Z.'..
0010: B2 9C 14 97 DC C0 EF B6 73 EA 63 E1 44 FA C7 AD ........s.c.D...
0020: 60 B5 4E B4 EE 25 F3 48 13 5B F9 0B 31 53 01 96 `.N..%.H.[..1S..
CONNECTION KEYGEN:
Client Nonce:
0000: 45 09 62 F6 47 C3 B9 2C 56 60 0E 0B AB 4C 69 87 E.b.G..,V`...Li.
0010: 88 72 35 36 89 4B CA FE 70 D0 F0 5B C7 F6 AF CF .r56.K..p..[....
Server Nonce:
0000: 45 09 62 F7 3F 5D 30 49 62 FB A0 D7 3D 6E F6 0C E.b.?]0Ib...=n..
0010: 05 D1 5F C2 98 C1 00 B5 87 1A 96 AE 34 5C 38 FA .._.........4\8.
Master Secret:
0000: 0E 63 38 16 86 A1 84 72 33 2C D7 07 D7 C3 AC E0 .c8....r3,......
0010: AD 5B CD 3B 2E 2A 02 91 1E FE 17 97 4E 3B 56 C3 .[.;.*......N;V.
0020: 5D 0F 7A 99 90 0D 3D 4E 5F 39 C5 EB 6E AD DA 71 ].z...=N_9..n..q
Client MAC write Secret:
0000: 99 32 FA 60 0B 88 36 CD 88 02 D5 4A CA D2 A6 49 .2.`..6....J...I
0010: 69 60 42 B6 i`B.
Server MAC write Secret:
0000: 43 3F 85 72 FB 6D 28 1C BA 1E 8A 26 56 DE 18 FB C?.r.m(....&V...
0010: 01 83 20 7F .. .
Client write key:
0000: 6F 58 29 AB B3 8C F5 75 3C 70 04 DF 9D 01 43 F5 oX)....u<p....C.
Server write key:
0000: 4A D7 E9 63 53 32 78 DF E0 99 89 60 A4 1A 3C E7 J..cS2x....`..<.
Client write IV:
0000: 24 FB 0E 12 AB D2 70 6D 80 B1 B2 BC 78 1A 55 88 $.....pm....x.U.
Server write IV:
0000: E4 75 62 25 46 95 0F 7A 44 16 E2 39 38 AD 29 CD .ub%F..zD..98.).
HawkEye Client Thread, WRITE: TLSv1 Change Cipher Spec, length = 1
*** Finished
verify_data: { 98, 254, 245, 75, 252, 23, 91, 164, 67, 197, 69, 44 }
Client Thread, WRITE: TLSv1 Handshake, length = 48
Client Thread, READ: TLSv1 Alert, length = 2
Client Thread, RECV TLSv1 ALERT: fatal, handshake_failure
Client Thread, called closeSocket()
Client Thread, handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
Error: Received fatal alert: handshake_failure
Thread-4, handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

Error Connecting to database URL jdbc:oracle:oci:@rmsdbtst as user rms13 java.lang.Exception:UnsatisfiedLinkError encountered when using the Oracle driver

Trying to Install RMS application 13.2.2 and I get past the pre-installation checks and when I get to the Data Source details and enter the data source details with the check box checked to validate the schema/Test Data Source I get the following error:
Error Connecting to database URL jdbc:oracle:oci:@rmsdbtst as user rms13 java.lang.Exception:UnsatisfiedLinkError encountered when using the Oracle driver. Please check that the library path is set up properly or switch to the JDBC thin client oracle/jdbc/driver/T2CConnection.getLibraryVersioNumber()
Checks performed:
RMS Application code location and directory contents:
[oracle@test-rms-app application]$ pwd
/binary_files/STAGING_DIR/rms/application
[oracle@test-rms-app application]$ ls -ltr
total 144
-rw-r--r-- 1 oracle oinstall   272 Dec 7 2010 version.properties
-rw-r--r-- 1 oracle oinstall   405 Jan 16 2011 expected-object-counts.properties
-rw-r--r-- 1 oracle oinstall   892 May 13 2011 ant.install.properties.sample
-rw-r--r-- 1 oracle oinstall 64004 Jun 6 2011 build.xml
drwxr-xr-x 9 oracle oinstall 4096 Jun 16 2011 rms13
drwxr-xr-x 3 oracle oinstall 4096 Jun 16 2011 installer-resources
drwxr-xr-x 3 oracle oinstall 4096 Jun 16 2011 antinstall
drwxr-xr-x 2 oracle oinstall 4096 Jun 16 2011 ant-ext
drwxr-xr-x 5 oracle oinstall 4096 Jun 16 2011 ant
-rw-r--r-- 1 oracle oinstall 11324 Dec 18 09:18 antinstall-config.xml.ORIG
-rwxr-xr-x 1 oracle oinstall 4249 Dec 18 10:01 install.sh
drwxr-xr-x 4 oracle oinstall 4096 Dec 18 10:06 common
-rw-r--r-- 1 oracle oinstall 16244 Dec 19 10:37 antinstall-config.xml
-rw-r--r-- 1 oracle oinstall   689 Dec 19 10:37 ant.install.log
[oracle@test-rms-app application]$
Application installation:
[oracle@test-rms-app application]$ ./install.sh
THIS IS the driver directory
Verified $ORACLE_SID.
Verified SQL*Plus exists.
Verified write permissions.
Verified formsweb.cfg read permissions.
Verified Registry.dat read permissions.
Verified Java version 1.4.2.x or greater. Java version - 1.6.0
Verified Tk2Motif.rgb settings.
Verified frmcmp_batch.sh status.
WARNING: Oracle Enterprise Linux not detected. Some components may not install properly.
Verified $DISPLAY - 172.16.129.82:0.0.
This installer will ask for your "My Oracle Support" credentials.
Preparing installer. This may take a few moments.
Your internet connection type is: NONE
Integrating My Oracle Support into the product installer workflow...
     [move] Moving 1 file to /binary_files/STAGING_DIR/rms/application
Installer preparation complete.
MW_HOME=/u01/app/oracle/Middleware/NewMiddleware1034
ORACLE_HOME=/u01/app/oracle/Middleware/NewMiddleware1034/as_1
ORACLE_INSTANCE=/u01/app/oracle/Middleware/NewMiddleware1034/asinst_1
DOMAIN_HOME=/u01/app/oracle/Middleware/NewMiddleware1034/user_projects/domains/rmsClassDomain
WLS_INSTANCE=WLS_FORMS
ORACLE_SID=rmsdbtst
JAVA_HOME=/u01/app/oracle/jrockit-jdk1.6.0_45-R28.2.7-4.1.0
Launching installer...
To make sure I have connectivity from the app server to the database (on a database server) here are the steps followed:
[oracle@test-rms-app application]$ tnsping rmsdbtst
TNS Ping Utility for Linux: Version 11.1.0.7.0 - Production on 19-DEC-2013 10:41:40
Copyright (c) 1997, 2008, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = test-rms-db.vonmaur.vmc)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SID = rmsdbtst)))
OK (0 msec)
[oracle@test-rms-app application]$
[oracle@test-rms-app application]$ sqlplus rms13@rmsdbtst
SQL*Plus: Release 11.1.0.7.0 - Production on Thu Dec 19 10:46:18 2013
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@test-rms-app application]$
[oracle@test-rms-app application]$ ping test-rms-db
PING test-rms-db.vonmaur.vmc (192.168.1.140) 56(84) bytes of data.
64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=1 ttl=64 time=0.599 ms
64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=2 ttl=64 time=0.168 ms
64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=3 ttl=64 time=0.132 ms
64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=4 ttl=64 time=0.158 ms
64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=5 ttl=64 time=0.135 ms
--- test-rms-db.vonmaur.vmc ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 0.132/0.238/0.599/0.181 ms
[oracle@test-rms-app application]$
[oracle@test-rms-app application]$ uname -a
Linux test-rms-app.vonmaur.vmc 2.6.18-128.el5 #1 SMP Wed Jan 21 08:45:05 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
[oracle@test-rms-app application]$
[oracle@test-rms-app application]$ cat /etc/*-release
Enterprise Linux Enterprise Linux Server release 5.3 (Carthage)
Red Hat Enterprise Linux Server release 5.3 (Tikanga)
[oracle@test-rms-app application]$
The database is created and all the batch file scripts have been successfully deployed. Now working on the application server. The Weblogic server is installed and 11g forms and reports are installed successfully.
Any help would be helpful.
Thanks,
Ram.

Please check MOS Notes:
FAQ: RWMS 13.2 Installation and Configuration (Doc ID 1307639.1)

CCM.LOG Showing Errors Connecting to Server (Error 5 - Access Denied) to \\\admin$ Share

Hi All!
We are encountering what I think would be a normal error in most cases if a client is unavailable or offline. During client push, we are receiving errors connecting to a NULL value in the log (\\\admin$) as opposed to an actual client:
Under normal circumstances, the log should read as follows:
Attempting to connect to administrative share
\\<machine_name>\admin$ using <Client Push Account>.
What we are running into is a repeating error (with some processed CCR records in between) that shows as follows:
~ Doing Account Cleanup Operation .... SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:14 AM 8612 (0x21A4)
~ Processing domain DOMAIN1 SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:14 AM 8612 (0x21A4)
~ Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:14 AM 8612 (0x21A4)
~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN3\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN3\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN3\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN2\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN2\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN2\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN1\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN1\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN1\clientpush_service_account (00000775) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Attempting to connect to administrative share '\\\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Failed to get token for current process (5) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ ERROR: Failed to connect to the \\\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Failed to connect to Server. Error 5 SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Processing domain DOMAIN2 SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN3\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN3\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN3\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN2\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN2\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN2\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN1\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN1\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN1\clientpush_service_account (00000775) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Attempting to connect to administrative share '\\\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Failed to get token for current process (5) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ ERROR: Failed to connect to the \\\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Failed to connect to Server. Error 5 SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Processing domain DOMAIN3 SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN3\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN3\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN3\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN2\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN2\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN2\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Attempting to connect to administrative share '\\\admin$' using account 'DOMAIN1\clientpush_service_account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN1\clientpush_service_account (000004b3) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account DOMAIN1\clientpush_service_account (00000775) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Attempting to connect to administrative share '\\\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Failed to get token for current process (5) SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ ERROR: Failed to connect to the \\\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Failed to connect to Server. Error 5 SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
~ Account Cleanup Operation Completed successfully. SMS_CLIENT_CONFIG_MANAGER 10/2/2013 10:46:15 AM 8612 (0x21A4)
We have Three Domains (Domain1, Domain2, and Domain3) with service accounts specified in the Client Push Installation Client properties.
I don't know if there is an entry (or entries) in the SCCM database that are NULL or blank that is generating these errors.
\\\admin$ indicates, to me, that there is a missing machine name that should follow the two \\ and before the \admin$. Obviously we aren't going to be able to connect to a machine with no name (hence the Failed to Connect to Server. Error
5).
Is there a way to clean the database of these empty records and fix this recurring error? It repeats every 15 minutes.
Thank you!

Yes, I know this is an old post, but I’m trying to clean them up.
I would review the CM07 console to see if there are any device without a netbios name. It will be these device that are cause you problems.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Error : Connecting to Client

Similar Messages

Maybe you are looking for