Cisco desktop agent fail to connect to CCX7.0

Hello,
Please we occure a problem that the Cisco desktop agent fail to connect to CCX 7.0 extension Agent ID not found.
regards

We're currently seeing the same issue with only two Agents. When you look at the Agent's call log, it shows a reason code of Ring No Answer. This would lead me to believe that UCCX is attempting to pass calls to the Agents, but the phone never rings. Anyone else seeing this?
We're running UCCX 8.0.2 and CAD ver 8.0.2.300.

Similar Messages

Cisco desktop agent and MWI

Is there a way with Cisco Desktop agent to have a popup or an icon so if there are voicemails the agents will know they are there?

Hi
Not sure what you are asking for here?
If an agent has VM, then they should get the normal MWI/red light on the handsets.
If you are talking about VM for the 'queue' (i.e. a shared voicemail box), then I normally configure like so:
1) Create a line on the system (with a new, unused DN)
2) CFwdAll the line to Voicemail
3) When you send a call to VM for the queue, send it to the new line, which forwards to voicemail
4) Configure a VM box with the new line DN as it's extension
5) Configure the new DN as a second line on all the agent phones that you wish to receive notification.
Now, when a VM is left, the envelope icon on the VM line appears on the phone and the MWI can be lit so all users are aware of it.
Regards
Aaron
Please rate helpful posts...

Desktop App Failed to Connect (Mac)

So I was just using Adobe Story offline to make a script, then I restarted my MacPro (running Lion), all of my software is up-to-date, always, then when I went to log into Story on the desktop, the second I hit "enter" to log it, it just said "Failed to connect. Please try again later.", however, when I log in with my old Adobe account (I got a new one because my old E-Mail was deleted, so I couldn't verify my E-Mail), it loads for two seconds then says that it sent a verification to my E-Mail! However, when I log into https://www.adobe.com with my E-Mail, it connects just fine! Why can't I log on? Or can someone at least tell me where I can find my saved script files? Thank you.

I have the same problem woith my Torch 9800. The Desktop Software tells me it is not connected. My local Mac dealer cannot help, neither can my carrier. My Mac (Lion) is standalone and my BB has not been touched by any IT guy or girl. Result: I'm unable to synchronise my BB with my Mac.
What is truly disappointing is that my carrier has contacted RIM on this subject, but the latter did not react. No wonder their sales and stock price are down. They should realise that Mac sales are up, and that the iPhone is superbly simple to synchronise via iTunes.
Wake up, RIM!
Ole

Cisco Desktop Agent\Supervisor & Windows 7 Compatibility

We are on Customer Response Solutions V 5.0(2). In order to install the Desktop Agent on Windows 7 we need to install DA v 7.5(8). We have been told by our VAR that we need to upgrade not only our CRA but also our CallManager to verison 8. This is going to be a big expense especially since we just upgraded four Cisco Servers less than two years ago.
Does anyone have any experience with the Desktop Agent on Windows 7? If so what version works?
Thanks

Hi Sandy,
Here is the page which has the compatibilities listed for Windows 7.
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/product_bulletin_c25-563280_ps427_Products_Bulletin.html
Here is the snippet that concerns UCCX. Which is what I think you are running, but you haven't actually stated that.
Version 7.0(2), Q4CY10
Version 8.0(1), FCS Q1CY10
If you upgraded to UCCX 8, you could still keep your CallManager at 7, provided it's on a supported version.
To know that, you need to look at the compatibility guide for UCCX:
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_compatibility/matrix/crscomtx.pdf
I hope this helps.

Cisco Desktop Agent application

How do you change the default URL links in the Ciscao Agent application? Is it done in CM or UCCX consoles?
We have a few agents that want to reset the default links in the Agent application?

You need to use the Cisco Desktop Workflow Administrator application. You can download this through the /appadmin UI under Tools > Plugins.
Cisco Desktop Administrator User Guide/CAD 8.5 for Unified CM

SQL Server Agent fails to connect to DB after enabling mirror on failover cluster

Hello:
We have multiple databases running in a Failover Cluster instance: SQL 2012SP1 on Server 2008 R2 failover cluster (NOT AlwaysOn). We are trying to add a high-performance mirror in a standalone instance for DR. My understanding is that should be a perfectly
normal, supported configuration.
The mirroring is working properly; however, the clustered SQL Server agent is unable to run jobs that run in the mirrored databases.
We get the following in the job log: Unable to connect to SQL Server 'VIRTUALSERVERNAME\INSTANCE'. The step failed.
There is a partner message in the agent log: [165] ODBC Error: 0, Connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported. [SQLSTATE IMH01]
The cluster is not a mulitsubnet cluster. All hosts are connected to the same subnets and there is no storage replication. I can not find any place where I can adjust the connect string options for SQL Agent.
Any guidance or suggestions on how to resolve this would be appreciated.
~joe

SQL Team - MSFT:
Thank you for taking the time to research and provide a clear answer.
This seems very much a workaround and very unsatisfactory.
You are correct, there is an IP dependency with OR condition. Moving to an AND condition is not viable for us. The whole point is to provide network redundancy. With an AND condition, if EITHER network interface fails, the service will go offline or fail
to come online without manual intervention. This is arguably worse for uptime than having a single interface available.
We are in process of rewriting all our SQL jobs to start in tempdb before transitioning to the appropriate target database. If this works for all of our jobs, I will mark the above response as answer.
Again, thank you for the answer.
Regards,
Joe M.

Cisco Desktop Agent Time out?

Can someone tell me if there is a "Time out" feature that knocks users out of the call agent group after a certain perioud of inactivity or could there be a limit to how many users can be in the agent group?
Thanks ,Chet

Yes to both quests.
There is a time out feature you set for agent desktop. There is also a user license limitation for number of agents signed on given moment.
in ICM under configuration manager list tools, list agent desk setting see details.
may want to post this in contact center forum.
please rate if it helps.
Baseer.

VPN fails to connect

Does anyone know if the VPN option works? It is under setting, wireless network, VPN settings. I have a PPTP connection that works fine from my desktop but "fails to connect to server" when tried on my phone.

Sorry to say that showing the scrreen shots does not make it work. The bottom line is the the ROM supplied by Verizon/Samsung/Google - whoever you want to blame does not support VPN connections.
Here is a log and one VPN vendors answer.
11-18 21:27:41.648 E/VpnService(7616)onError()
11-18 21:27:41.648 E/VpnService(7616)java.io.IOException: Connecting timed out
11-18 21:27:41.648 E/VpnService(7616)at com.android.server.vpn.VpnService.waitUntilConnectedOrTimedout(VpnService.java:206)
11-18 21:27:41.648 E/VpnService(7616)at com.android.server.vpn.VpnService.onConnect(VpnService.java:136)
11-18 21:27:41.648 E/VpnService(7616)at com.android.server.vpn.VpnServiceBinder$2.run(VpnServiceBinder.java:108)
11-18 21:27:41.648 E/VpnService(7616)at java.lang.Thread.run(Thread.java:1096)
11-18 21:27:41.728 I/VpnService(7616)disconnecting VPN...
11-18 21:27:41.793 D/VpnActor(7580)vpn disconnecting!
We think the reason behind this error is that, either your phone not support VPN or the ROM u r using have VPN problem.( from my own experience, I think it's the ROM problem)

Database patched 10.2.0.3-10.2.0.4 Error on Grid Control :Failed to connect

HI my patch was laready on 10.2.0.4 and just upgraded by databse from 10.2.0.3 to 10.2.0.4
though database and listener and agent are up and running at the OS
but on Grid Control I'm getting the error under
'Agent'
Failed to connect to database instance: ORA-01034: ORACLE not available.
Any Idea guys
Thanks
Gagan

I would check whether Oracle was still available. With the current state of Oracle software you never know.
If Oracle was available I would try to use sqlplus to connect to the database using the dbsnmp account.
If that works, it is SR time.
As you don't specify any O/S information, it is difficult to tell you more, especially as some releases of Oracle on some processors are flaky, and Oracle can not always reproduce the problems in house.
Sybrand Bakker
Senior Oracle DBA

Remote desktop connection blocked by cisco security agent

Hi,
I have a deployment of a Management Center for Cisco Security Agents 6.0.2 and i just noticed that the agent is blocking the remote desktop connection to the hosts, the agent installed on the server shows me the event but i'm not able to see it logged on the Management Center (i can see logged any other events), i'm not sure what rule should i enable in order to allow this connection.
Do you have any ideas???
Thanks in advance...

Hi,
Remote desktop connection uses the highest possible security level encryption method between the source and destination.
In Windows Vista or later versions of Windows, the remote desktop connection uses the SSL (TLS 1.0) Protocol and the encryption is Certificate-based.
TS Gateway can also make the connection more secure, enhance security, see detailed information in this link
http://technet.microsoft.com/en-us/library/cc731264(WS.10).aspx
Don't forget some known offical antii-virus software, they can also protect the connetion from network attack.
Yolanda Zhu
TechNet Community Support

Cisco Unified CCX desktop agents were all logged off this morning

Hi All,
We have CCX with 23 Premium seats running System version: 8.0.2.11002-3.
This morning, all of the desktop agents were all logged offf at the same time with the exception of one agent who was on a call when the problem occurred.
All agents were able to log back into the system.
Some had to tick a box "log the other user off" and some had to reboot their pcs.
Does anyone have any tips for me to troubleshoot this sort of problem?
The fact that when the users tried to log back in and the system said they were already logged in on that user id tells me that something unuaual has happened with the software.
Thanks so much for any assistance
Regards,
Amanda Lalli-Cafini

Hi Amanda,
There could be several reasons here.
1. CUCM or CM Telephony service getting restarted.
2. UCCX or any of its desktop related services getting restatred. Failover\Failback happening in case of HA system.
3. Network connectivity issues.
To find out the exact reason for failure, you need to check the logs from both the UCCXand CAD side.
And also if you login into UCCX serviceability page and navigate to control center, you could see since how long each of the UCCX services are up and running, try to see which is the service running from least time, which will give you an indication of this service restart.
CAD logs path,
C:\Program Files\Cisco\Desktop\log
UCCX logs can be downloaded from the RTMT tool, please see the MIVR, MCVD logs in this time duration.
Hope it helps.
Anand
Please rate helpful posts by clicking on the stars below the right answers !!

OBIEE 11g agents are failed to connect to Essbase

OBIEE 11g agents are failed to connect to Essbase. We are using :USER & :PASSWORD (SSO) in connection pool setting to connect to Essbase.
User account exists in both OBIEE and Essbase. OBIEE dashboards which are based on Essbase are working fine. Essbase variables in RPD are upto date.
Only agents are failing and error says invalid credentials, but dashboard pages are running without any issue.
OBIEE: 11.1.1.5 (BP4)
Essbase: 11.1.2.1
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 96002] Essbase Error: Login fails due to invalid login credentials (HY000)
Essbase and OBIEE services are up and running.
Any help will be appreciated.

We finally implemented CSS Token option and ended up with this error. We are unable to connect to essbase with CSS Token option.
We followed the Oracle document to implement this.
[nQSError: 43119] Query Failed: EPMCSS-00301: Failed to authenticate user. Invalid credentials. Enter valid credentials. (HY000)
We did update this property:
JAVA_PROPERTIES="-Dplatform.home=${WL_HOME} -Dwls.home=${WLS_HOME} -Dweblogic.home=${WLS_HOME} -Didstore.identityAttribute=objectguid"
Any help will be appreciated!

SMD agent not starting correctly FAIL: NIECONN_REFUSED (Connection refused)

I am getting the following message when I start the agent. I don't see any errors except for this, and when I try to connect it in agent_adminstration, it never connects. Just eventually times out after 30 mins.
FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
cat jvm_SMDAgent.out
LoadBalanceRestricted=no
P4ClassLoad=P4Connection
SAPDBHOST=
SAPINFO=SMD_98_server
SAPMYNAME=ssmsap_SMD_98
SAPSTARTUP=1
SAPSYSTEM=98
SAPSYSTEMNAME=SMD
application.home=/usr/sap/SMD/exe
com.ibm.cpu.endian=little
com.ibm.oti.configuration=scar
com.ibm.oti.jcl.build=20080922_1143
com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
com.ibm.oti.vm.library.version=23
com.ibm.util.extralibs.properties=
com.ibm.vm.bitmode=64
file.encoding=UTF-8
file.separator=/
ibm.signalhandling.rs=false
ibm.signalhandling.sigchain=true
ibm.signalhandling.sigint=true
ibm.system.encoding=UTF-8
j2ee.dbhost=
java.assistive=ON
java.awt.fonts=
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
java.class.version=48.0
java.compiler=j9jit23
java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC   - 200809_04
java.home=/opt/IBMJava2-amd64-142/jre
java.io.tmpdir=/tmp
java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=2.3
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.4
java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
java.vendor=IBM Corporation
java.vendor.url=http://www.ibm.com/
java.version=1.4.2
java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC   - 200809_04
java.vm.name=IBM J9 VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=IBM Corporation
java.vm.version=2.3
jstartup.debuggable=yes
jstartup.mode=JCONTROL
jstartup.ownHardwareId=F2143454721
jstartup.ownProcessId=17393
jstartup.whoami=server
jxe.current.romimage.version=9
jxe.lowest.romimage.version=9
line.separator=
memory.manager=256M
os.arch=amd64
os.name=Linux
os.version=2.6.9-89.ELsmp
path.separator=:
sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
sun.io.unicode.encoding=UnicodeLittle
sun.java2d.fontpath=
sys.global.dir=/usr/sap/SMD/SYS/global
user.country=US
user.dir=/usr/sap/SMD/J98/SMDAgent
user.home=/home/smdadm
user.language=en
user.name=smdadm
user.timezone=
user.variant=
Running SMD Agent ...
[p4://ssmsap:50004] Agent ready.
Initialization done.
cat jvm_SMDAgent.out
LoadBalanceRestricted=no
P4ClassLoad=P4Connection
SAPDBHOST=
SAPINFO=SMD_98_server
SAPMYNAME=ssmsap_SMD_98
SAPSTARTUP=1
SAPSYSTEM=98
SAPSYSTEMNAME=SMD
application.home=/usr/sap/SMD/exe
com.ibm.cpu.endian=little
com.ibm.oti.configuration=scar
com.ibm.oti.jcl.build=20080922_1143
com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
com.ibm.oti.vm.library.version=23
com.ibm.util.extralibs.properties=
com.ibm.vm.bitmode=64
file.encoding=UTF-8
file.separator=/
ibm.signalhandling.rs=false
ibm.signalhandling.sigchain=true
ibm.signalhandling.sigint=true
ibm.system.encoding=UTF-8
j2ee.dbhost=
java.assistive=ON
java.awt.fonts=
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
java.class.version=48.0
java.compiler=j9jit23
java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC   - 200809_04
java.home=/opt/IBMJava2-amd64-142/jre
java.io.tmpdir=/tmp
java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=2.3
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.4
java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
java.vendor=IBM Corporation
java.vendor.url=http://www.ibm.com/
java.version=1.4.2
java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC   - 200809_04
java.vm.name=IBM J9 VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=IBM Corporation
java.vm.version=2.3
jstartup.debuggable=yes
jstartup.mode=JCONTROL
jstartup.ownHardwareId=F2143454721
jstartup.ownProcessId=17393
jstartup.whoami=server
jxe.current.romimage.version=9
jxe.lowest.romimage.version=9
line.separator=
memory.manager=256M
os.arch=amd64
os.name=Linux
os.version=2.6.9-89.ELsmp
path.separator=:
sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
sun.io.unicode.encoding=UnicodeLittle
sun.java2d.fontpath=
sys.global.dir=/usr/sap/SMD/SYS/global
user.country=US
user.dir=/usr/sap/SMD/J98/SMDAgent
user.home=/home/smdadm
user.language=en
user.name=smdadm
user.timezone=
user.variant=
Running SMD Agent ...
[p4://ssmsap:50004] Agent ready.
Initialization done.

cat dev_SMDAgent
trc file: "/usr/sap/SMD/J98/work/dev_SMDAgent", trc level: 1, release: "701"
node name   : smdagent
pid         : 17393
system name : SMD
system nr. : 98
started at : Wed Oct 7 08:56:32 2009
arguments         :
          arg[00] : /usr/sap/SMD/J98/../exe/jlaunch
          arg[01] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
          arg[02] : -DSAPINFO=SMD_98_server
          arg[03] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
JStartupReadInstanceProperties: read instance properties [/usr/sap/SMD/J98/profile/smd.properties]
-> ms host    :
-> ms port    : 36
-> OS libs    : /usr/sap/SMD/exe
-> Admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : /usr/sap/SMD/J98/profile/smd.properties
Instance properties
-> ms host    :
-> ms port    : 36
-> os libs    : /usr/sap/SMD/exe
-> admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
Worker nodes
-> [00] smdagent             : /usr/sap/SMD/J98/profile/smd.properties
[Thr 182894174624] Wed Oct 7 08:56:32 2009
[Thr 182894174624] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 182894174624] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
[Thr 1085282656] WaitSyncSemThread: Thread 1085282656 started as semaphore monitor thread.
[Thr 182894174624] SigISetDefaultAction : default handling for signal 17
[Thr 182894174624] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 182894174624] CPIC (version=701.2009.01.26)
[Thr 182894174624] [Node: SMDAgent] java home is set by profile parameter
        Java Home: /opt/IBMJava2-amd64-142
[Thr 182894174624] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SMD/J98/../exe/jvmx.jar
JStartupIReadSection: read node properties [smdagent]
-> node name          : SMDAgent
-> node type          : server
-> node id            : 1
-> node execute       : yes
-> java path          : /opt/IBMJava2-amd64-142
-> java parameters    : -DP4ClassLoad=P4Connection -Xj9 -Xmn50m -Xgcpolicy:gencon
-> java vm version    : J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
-> java vm vendor     : IBM J9 VM (IBM Corporation)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 256M
-> init heap size     : 256M
-> root path          : ../SMDAgent
-> class path         : ../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
-> OS libs path       : /usr/sap/SMD/exe
-> main class         : com.sap.smd.agent.launcher.SMDAgentLauncher
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : /usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar
-> parameters         : run jcontrol
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 58981
-> shutdown timeout   : 20000
[Thr 182894174624] JLaunchISetDebugMode: set debug mode [no]
[Thr 1086335328] JLaunchIStartFunc: Thread 1086335328 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [SMDAgent]
-> stack   : 1048576 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -DP4ClassLoad=P4Connection
-> arg[ 4]: -Xj9
-> arg[ 5]: -Xmn50m
-> arg[ 6]: -Xgcpolicy:gencon
-> arg[ 7]: -Dsys.global.dir=/usr/sap/SMD/SYS/global
-> arg[ 8]: -Dapplication.home=/usr/sap/SMD/exe
-> arg[ 9]: -Djava.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
-> arg[ 10]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
-> arg[ 11]: -Dmemory.manager=256M
-> arg[ 12]: -Xmx256M
-> arg[ 13]: -Xms256M
-> arg[ 14]: -DLoadBalanceRestricted=no
-> arg[ 15]: -Djstartup.mode=JCONTROL
-> arg[ 16]: -Djstartup.ownProcessId=17393
-> arg[ 17]: -Djstartup.ownHardwareId=F2143454721
-> arg[ 18]: -Djstartup.whoami=server
-> arg[ 19]: -Djstartup.debuggable=yes
-> arg[ 20]: -DSAPINFO=SMD_98_server
-> arg[ 21]: -DSAPSTARTUP=1
-> arg[ 22]: -DSAPSYSTEM=98
-> arg[ 23]: -DSAPSYSTEMNAME=SMD
-> arg[ 24]: -DSAPMYNAME=ssmsap_SMD_98
-> arg[ 25]: -DSAPDBHOST=
-> arg[ 26]: -Dj2ee.dbhost=
[Thr 1086335328] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
-> arg[ 0]: run
-> arg[ 1]: jcontrol
[Thr 1086335328] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 1086335328] Wed Oct 7 08:56:35 2009
[Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]
[Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 1086335328] Wed Oct 7 08:56:38 2009
[Thr 1086335328] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 1086335328] JLaunchISetState: change state from [Starting (2)] to [Running (3)]
[Thr 1101334880] Wed Oct 7 08:56:43 2009
[Thr 1101334880] JLaunchISetState: change state from [Running (3)] to [Starting applications (10)]
[Thr 1101334880] Wed Oct 7 08:56:48 2009
[Thr 1101334880] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]

Running an SQL Server Agent Job to execute a package but the job FAILS on Connections

I have created a package which basically imports data from one database to another, The database where it collects the data from the job is failing on connecting reporting the following message:
Source: ****** Connection manager "Source - *****"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft
OLE DB Provider for SQL Server" Hresult: 0x80040E4D Description: "Login failed for user '*ConnectionONE*'.". End Error Error: 2015-02-18 11:36:04.94     Code: 0xC020801C
Source: Data Flow Task Get Revenue Data [1]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Source - *****" failed with error
code 0xC0202009.
The package runs fine if executed within the package but fails from the SQL Agent Job.
NB * is to hide confidential data. *ConnectionONE* is the database which the package is attempting to get data from.
Completely puzzled on what to do as i have tried reading other forumns but they dont seem to be helping.
Any Help would be great thankyou!

That is because package is set to "EncryptSensitiveWithUserKey". Please change that to "EncryptSensitiveWithPassword" and the provide password to protect sensitive data.
More information
here.
Regards,
Vishal Patel
Blog: http://vspatel.co.uk
Site: http://lehrity.com

SCOM 2012 ACS agent Failed connecting to collector

Hi,
We are using SCOM 2012 on Windows 2012, when installing the SCOM agent with Audit Collection Services the ACS forwarder will report in as healthy until reboot, after reboot the forwarder state changes to failed to connect to collector. (XXX's are redacted
system information).
Forwarder unsuccessfully tried to connect to the following collector(s): XXXXXXXX:51909, status: 0x80090322 (TCP connect), source: registry addresses tried: XXX.XXX.XXX.XXX:51909 If the list of collectors is blank, then AdtAgent was unable to locate a collector.
Common reasons for this message are: The machine(s) listed is not online AdtServer is not running on the machine(s) listed AdtServer on the machine(s) listed is not listening on the specified port TCP connectivity to the AdtServer machine is blocked by firewall,
IPSec, or other filtering mechanism AdtServer on the machine(s) listed actively refused the connection (due to policy or current activity load) For detailed failure information, enable trace logging using the TraceFlags registry key and examine the AdtAgent.log
in the \temp subdirectory of the Windows directory.
Enabling trace logging repeats the same error, unable to connect to server. We have verified, the IP is correct, the FQDN is correct and has a forward and reverse lookup record. We have also verified via telnet that port 51909 is open in both directions.
Any help would be appreciated.

If you are 100% sure port 51909 is open at Collector's side (you don't need to open it on ACS forwarder) and there's no additional firewall somewhere at the middle use wireshark and capture what's going on.
--- Jeff (Netwrix)

Cisco desktop agent fail to connect to CCX7.0

Similar Messages

Maybe you are looking for