Attendant Console supported on a thin client station ?

Does somebody know if it's possible to install the attendant console on a diskless HP station (thin client station) working with the RDP protocol ?
I'm using CCM 4.1(3)

We run attendant console on our windows 2003 terminal server. You will need to have 1 copy of the installation for each user (just install it on a normal pc and copy the folder to the terminal server).

Similar Messages

  • Font Smoothing CE 6.0 Thin Clients

    We need to handle Font Smoothing on HP Thin Clients. This is supported on newer Thin Clients with RDP7 and Font Smoothing settings.
    Older Win CE 6.0 do not appear to support Font Smoothing.
    Is there a way to set up Font Smoothothing or can these thin clients be updated with RDP option to support Font Smoothing?
    Thanks Lex

    I too had the same problem just last night. It happened when I was changing the font and font size. It seemed that everytime I switched the font and font size, the text got more and more pixelated and less smooth (identical to the screenshot you just posted).
    I backed up my Torch, did a security wipe and then restored the backup file back onto the device. That didn't work, as the text still looked horrible.
    So what I did next was do a device switch from my Torch back onto my Bold 9000, security wiped the Torch then did a device switch from the Bold 9000 back onto the Torch and the text was back to normal! It was a long process but it seemed to do the trick. So if you have another BlackBerry sitting around it might be worth trying, just remember to back up your Torch before hand.
    My Torch is also running v6.0.0.246, Platform 6.4.0.105 through Rogers. Hope this helps you out.
    Good Luck!
    Ed

  • What files do I need to download iPhone photos to a thin client (HP)? Apple Mobile Support gives 4 dll files to enable the iPhone to be detected and charged but the thin client doesn't see the camera or hard drive.

    The iTunes Installation files include 4 driver dlls that I can install on a Windows thin client to enable the iPhone to be charged.
    The iPhone hard drive or photos are not detected.  I guess I need scanner driver support to cope with the camera.
    Can anyone tell me which files from the iTune installation set are needed.
    It is not practical (or even possible?) to install the whole iTunes package.
    I've seen this question asked by a lot of people but never seen an answer. 
    Please, can someone help... 

    Thanks for the reply. 
    A thin client is used to connect to a Terminal Server, or in my customer's case, a Citrix Server.  I need the thin client to see the iPhone as a camera and pass it to the Citrix Client so the photos can THEN be either stored on a network storage device, or e-mailed.
    Because the thin client doesn't even SEE a camera (i.e. the iPhone) it won't be able to connect to iCloud to do anything useful. 
    I think the question I should be asking, is how do I give the thin client Camera Support.
    I've just seen a 2008 forum comment that said the iPhone DOESN'T handle photos through iTunes, but the PC (Scanner support) or MAC (iPhoto) handles them directly.  I should be putting the question to HP.
    This is still a good place for THIS question, because I've seen so many iPhone users asking it...
    If I get a satisfactory answer I'll post it back here.

  • HELP!!! Does LabView support a thin client or dumb terminal (diskless workstation) type of deployment

    Hello,
    Does LabView support a thin client or dumb terminal (diskless workstation) type of deployment? I have a need to run LabView on some sort of dumb terminal / diskless workstation.  If someone has deployed LabView in this matter, please provide me all the details on how this was accomplished (software, hardware, etc.)
    Thanks

    Sorry, can't call you.
    My first suggestion has nothing to do with LV. It is simply connecting as a remote client to the windows server and controlling the windows session on the server.
    My second suggestion involved writing a program which will contact the PLCs directly using Modbus and get the data from them. As mentioned, you can find some Modbus client implementations for LV by searching the web (or, if you have LV 8 and the DSC module, I think it should come built in).
    My third was writing 2 programs - one would run on the server and one on the client\s. The server program would be responsible for sending the data to the client and the client would be responsible for interacting with the user and sending the appropriate messages to the server. I already gave you pointers on what to search for (the example finder can be found by going to Help>>Find Examples and the site can be searched from the box at the top of the page, but make sure you don't search just the forums).
    In both cases, you would need to design the program and the interface for the user.
    Wi-Fi also has nothing to do with LV and is simply a way to form a wireless network. Any mobile device would almost definitely have support for it and buying an access point to form the wireless network is easy and cheap.
    To learn more about LabVIEW, I suggest you try searching this site and google for LabVIEW tutorials. Here, here, here and here are a few you can start with and here are some tutorial videos. You can also contact your local NI office and join one of their courses.
    In addition, I suggest you read the LabVIEW style guide and the LabVIEW user manual (Help>>Search the LabVIEW Bookshelf).
    Try to take over the world!

  • Unified Communications Attendant console: queue does not show in the client

    Hello,
    I have Cisco Unified Attendant Console - Department Edition 9.1.1.10 in conjunction with CUCM 9.1.1.
    My problem is that when I login with the operator account to the client the queue does not show up as expected.
    I have configured the queue, synchronized with CUCM, i can see it in CUCM under device/CTI route point, i have associated the queue to the operator in user configuration queue association.
    but when i login as the opeartor to the client i can not see it.
    any help is apreciated.
    thanks

    Hi,
    This is working correctly, as you can only associated a single queue (department), this is not displayed in the operator console client.
    You only see the queue list in Business, Enterprise or Premium Edition.
    Jamie

  • Rights required to open attendant console client

    I'm running attendant console 1.4.1.11 with CCM 4.1(3)sr3c. I can download the attendant console client to an XP machine and run the appplication as long as the user has admin or power user rights. I can't run the app when the user is given only user rights. Is this appropriate behavior for the attendant console client? I don't want to give my receptionists admin rights if I can avoid it.

    I handle this by giving the Authenticated Users group full access to the C:\program Files\Cisco\Call Manager Attendant Console folder. The logged in user just needs to be able to read and write to this folder.
    Hope this helps. If so, please rate the post.
    Brandon

  • Thin Client Support

    I am using MAC Mini Leopard. How can I provide Thin Client Support ? Is there any version which already have the Thin Client support ?

    Mac OS X does not natively provide "thin client" support except via X11 or UNIX command line. There is a third-party product that purports to provide such support:
    http://www.aquaconnect.net/
    but I don't know how well it works, and their FAQ says only that it works with Mac OS X 10.4, not with Leopard. You can contact them and ask if they have, or will have soon, a version that works with Mac OS X 10.5.

  • Unified Attendant Console - License and Remote Site

    I need  an Attendant Console solution for a 6 site IPT design.  I have CUCMBE at the corporate site with 5 remote locations.  I want to have an Attendant Console in each location.  I was going to use the Business Attendant version, but  see it only support 3 Queues, thoguht I had read it was 6 queues, so I guess I need to go with the Enterprise version.
    1.  To support 6 active clients, I need to order 6 licenses at $2950.00?  Seems awful expensive compared to the old Attendant Console...
    2.  Queues would need to be created for each site, Business only has 3, but Enterprise has 50?

    Hehe Chris, you're right. I've always thought that this is only the language for the installation details, but I've just tried it on my PC.
    Thanks a lot.
    regards
    Marc

  • Setting up oracle thin client for 9i?

    Does anyone have experience stting up data pools using oracle's 9i thin client that ships with BEA WLS 6.1? I am on a Sun Solaris box running Solaris 8 and oracle client 9i. I have followed all of the instrcutions (that I can find anyway) and it does not seem to work. Can someone please tell me exactly what to put in each field on the console for the Data Pool and in the classpath?
    Thanks in advance!!
    Adam

    Hi Adam,
    Configuration of a connection pool for oracle 9 is the same
    as for oracle 8.
    The only thing you should do is downloading a new
    classes12.zip that supports oracle 9, and putting it in to
    weblogic class path.
    You can download classes12.zip from otn.oracle.com.
    To put it to the weblogic classpath you need to modify
    weblogic startup script.
    Regards,
    Slava Imeshev
    "adam landefeld" <[email protected]> wrote in message
    news:[email protected]..
    Does anyone have experience stting up data pools using oracle's 9i thinclient that ships with BEA WLS 6.1? I am on a Sun Solaris box running
    Solaris 8 and oracle client 9i. I have followed all of the instrcutions
    (that I can find anyway) and it does not seem to work. Can someone please
    tell me exactly what to put in each field on the console for the Data Pool
    and in the classpath?
    >
    Thanks in advance!!
    Adam

  • Attendant Console 6.1.2 (yeah, I know it is unsupported)

    So knowing full well that this is an unsupported software, I am reaching out anyway.  I find myself in a pickle at my new company.  We are still running Call Manager 6.1.5.11900-13 (don't ask) and we have many users using Attendant Console.
    Last week, the line status of all the consoles changed to blue question marks.  The phone control function of the application works great, just no line status.
    We have restarted AC and CTI services on entire cluster, pointed the AC clients to multiple servers for testing, and uninstalled and reinstalled the AC client.  Tonight we are punting and rebooting the Publisher.
    Anyone out there unfortunate enough to be running this, and maybe have a suggestion to fix?
    A suggestion to upgrade would be sound, but won't be happening for now.
    Commence the laughing!

    They usually do not simply "die" like this.  Id check for any replication issues with your cluster first off. 
    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00809643e8.shtml
    Next, I would simply build an entire new AC in CUCM and try to use this one.  I have had luck in the past with this where the only way I could get it to work was to delete everything off it that AC used.  Pilot points, RPs, etc.  Then rebuild it.Sounds odd, yes.
    I find it odd though it stopped working with no changes in the network, CUCM configurations, etc.   

  • Problem using Weblogic 6 and Weblogic 8.1 thin clients from same applicatio

    We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
    First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
    Exceptions:
    Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
    Result : connects successfully with ?Weblogic 6.1 SP7?.
         throws following exception while connecting to ?Weblogic 8.1?.
    weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
         at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
         at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
         at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
         at weblogic.kernel.Kernel.initialize(Kernel.java:138)
         at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
         at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
    java.lang.InternalError: error initializing kernel
         at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
         at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
    Case 2: ?Weblogic 8.1? thin client jar first in class-path.
    Result : connects successfully with ?Weblogic 8.1?.
         throws following exception while connecting to ?Weblogic 6.1 SP7?.
    avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
    at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
    at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
    at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
    at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
    at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
    at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
    ... 16 more
    Couldn't connect to any host
    Cause: {1}
    javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
    Cause: {1}
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
    at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
    at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
    at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
    at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
    at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
    at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
    ... 16 more

    uday naik <> writes:
    The thin-client isn't supported on 6.1, I'm not sure what you are doing.
    andy
    We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
    First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
    Exceptions:
    Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
    Result : connects successfully with ?Weblogic 6.1 SP7?.
         throws following exception while connecting to ?Weblogic 8.1?.
    weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
         at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
         at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
         at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
         at weblogic.kernel.Kernel.initialize(Kernel.java:138)
         at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
         at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
    java.lang.InternalError: error initializing kernel
         at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
         at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
    Case 2: ?Weblogic 8.1? thin client jar first in class-path.
    Result : connects successfully with ?Weblogic 8.1?.
         throws following exception while connecting to ?Weblogic 6.1 SP7?.
    avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
    at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
    at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
    at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
    at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
    at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
    at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
    ... 16 more
    Couldn't connect to any host
    Cause: {1}
    javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
    Cause: {1}
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
    at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
    at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
    at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
    at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
    at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
    at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
    ... 16 more

  • Installing Adobe Reader on a Thin Client

    I have 27 Thin clients (HP t5639w) to set up in the next day or two... the problem: right out of the box, I am unable to install Adobe Reader on them. I have made room to install by using a flash drive to increase RAM, and Reader appears to have successfully loaded, but each time I try to open after install I get the following error message: "Font Capture: AcroRd32.exe Application Error.... The exception unknown software. Exception (0xc06d007e) occurred in the application at location 0x7c812afb."
    I've tried to contact HP customer support - unfortunately, they refer me to the HP website and tell me to download the version there. It's the same version I've tried to install - no luck. I have installed other software on the Thin Clients successfully, but I'm only having an issue with Reader.
    Anyone else have a similar issue? Any ideas?

    Here's the process:
    ·         Download Adobe to USB drive
    ·         Remove write filter – reboot
    ·         Create temporary TEMP and TMP folders on C: drive
    ·         Change Windows TEMP variables (both TEMP and TMP) to a folder on the “Hard Disk” – Reboot (Make a note of values before changing).
    ·         Install Adobe Reader – Reboot
    ·         Run Adobe Reader – If runs reboot
    ·         Replace TEMP and TMP variable entries (Usually Z:\TEMP and Z:\TMP respectively) – Reboot
    ·         Delete temporary TEMP and TMP folders – reboot
    ·         Re-enable write filter
    This worked for me!

  • How to identify inbound location on a centralized Attendant Console?

    I'm trying to find a way to be able to identify for our centralized receptionists the location of the inbound calls.
    We have 16 sites set up with Cisco routers as h323 gateways each pointing all incoming calls to the main phone line to a separate AC pilot point in CCM 4.13sr3b. Is it possible to have the dialpeer put some sort of description tag that the receptionists can see on attendant console when the call comes in that says where/which site this phone call is coming in from? Or display the queue it is coming in on?
    Any ideas on this would be appreciated. I'm trying to avoid going down the IPCC path to provide this functionality since Cisco won't support IPCC and attendant console running simultaneously.
    Bottom line is we have a multi site CM deployment where all inbound calls going to a central group of folks running attendant console and we need to be able to discern which pilot point or voice gateway the call is coming in on.
    I appreciate any thoughts on this!!
    Ryan

    One way to do this if you don't care about the caller ID of the calling party, would be to tranform the calling number to DN of the Pilot DN by using Translation Patterns. Basically the GW's CSS would not have access to the AC Pilot, but to a TP that transforms the calling party and redirects to the AC Pilot.
    HTH, please rate all posts!
    Chris

  • Attended Xfer on A SPA500S 32 Button Attendant Console

    I have a CISCO 504G with a SPA500S 32-Button Attendant Console.  I had this all configured just the way I like it, when I had to remove the Attendant Console for a recent move.  Now I have my console all programed with all my speed dials (employee extensions and cell numbers) but I can't transfer a call.  When I called my VoIP carrier, Vocalocity, they said it can't be done.  When I first got my sidekick, they told me the same thing.  I then called Cisco and they told me exactly how to configure it to be able to perform an Announced transfer so I know its possible.  I need to be able to let my employee know who is calling before I transfer the call.  Can anyone help me?

    We just installed an new system with the SPA508g phones and the SPA 500s Side Car and are having the same monitoring issues. We have notified our support and they have been tweeking our system quite a  bit. If this is a known issue why is CISCO not resolving it. Does CISCO monitor these forums?

  • Problem with Cisco Attendant console

                       Hi
    We Have Cisco attendant console 8.x at site .
    As per user they are
    " able to log into the “Attendant Console” and access the outgoing numbers located at the bottom of the screen. As far as the internal directory, it does not allow them to access due to the database connection issue. They are getting error “database not connected” on Attendant Console.
    Can you please suggest solution to resolve this . Thanks
    RJ

    Have a look at this link on page 33 and 34:
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucmac/arc/CiscoTSGv8_6_x.pdf
    Directory Issues
    Directory will not display and C
    onsole shows "Database not connected"
    message
    On the Attendant Console PC:
    Verify that the Windows User has Full Control access to the following registry key and it’s child
    objects: HKEY_LOCAL_MACHINE\Softwar
    e\Arc Solutions (See, the section
    “Client preferences
    do not save / are not retained” section on page
    4-4
    which shows how the permissions can be found
    and changed). (If version is older than 8.0.3 verify HKEY_LOCAL_MACHINE\Software\Borland
    as w
    ell)
    Verify that the CUEAC Server can be pinged from the command line by IP Address and Hostname
    If it cannot be reached via hostname, have this ad
    ded to DNS or to the host file on the machine.
    On the CUEAC Server:
    Ensure that the contact database is populated:
    Open a synchronization log file in C:\Program
    Files\Cisco\Logging\LDAP\Log\SSLog_xxxx.txt
    Check that contacts have been inserted or updated:

Maybe you are looking for