Device management process

Hi experts,
I have mannul process of device management.
now i want to use SAP so kindly tell me all the process by which i can convert it into SAP(data uploading all)
(about  end to end implementation)
Regards
Ankur

Hey Matt, thanks, but I think this is not the source of that problem.
As shown in the figure, "Device Management" will never change do "Enabled", no matter how much I click on configure.
The configure process is always successful but the state remains "Disabled". 

Similar Messages

  • Processes of device management of SAP ISU

    Can any one tell me all the processes and sub processes of device management of SAP ISU. Thanks in advance for your help.
    Moderator Note - thread locked due to rules violation - no generic postings
    Edited by: William Eastman on Mar 12, 2010 2:16 PM

    Hi,
    Organizational Management is useful in a business transaction like activity, sales order etc. You can determine the org. structure or Business Partners (like employee responsible) for a business transaction.
    Organization Model can be used for different functions like Sales, Service, Marketing (You can check this by clicking on "Function" tab in the Org Model screen). If you click Sales function and go to Attributes tab you will see particular set of attributes, while if you click service function you will see different set of attributes and also if you click marketing function you will see another different set of attributes. These attributes are helpful in determination of BPs based on these attributes through Organizational data determination.
    Refer the Document CR100 and refer teh below help Doc also.
    http://help.sap.com/saphelp_crm60/helpdata/en/bb/bdb3d9575911d189240000e8323d3a/frameset.htm

  • [solved] Digital Camera not recognized in device-manager

    My digital camera "Canon Powershot SX120 is" is not recognized by the devicemanager. I have read Digital Cameras.
    $ groups
    wheel storage users printadmin
    The "camera"-Group isn't needed anymore and this group doesn't exist on my system.
    The Powershot SX 120 has a  MTP/PTP connection mode (as the manual says). But:
    # mtp-detect
    Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
    Listing raw device(s)
    No raw devices found.
    gphoto succeed:
    $ gphoto2 --auto-detect
    Modell Port
    Canon PowerShot SX120 IS usb:002,019
    A gphoto --summary could be found here
    There is no udev-rule for this camera. If i create one while copying a rule from a similar camera from /etc/udev/rules.d/69-libmtp.rules, and store it into /etc/udev/rules.d/69-canon.rules, the device-manager shows up. My udev-rule:
    # Canon PowerShot SX120AX (PTP/MTP mode)
    ATTR{idVendor}=="04a9", ATTR{idProduct}=="31e0", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
    The device-manager shows me only the option to open with a file-manager. Doing so will result in an error:
    The file or folder udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:02.1/usb2/2-8/ do not exist.
    With my udev-rule:
    solid-hardware listen
    Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
    Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
    Listening to add/remove events:
    Device Added:
    udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:02.1/usb2/2-8'
    Without the active udev-rule, "solid-hardware listen" produces nothing, but
    udevadm monitor
    monitor will print the received events for:
    UDEV - the event which udev sends out after rule processing
    KERNEL - the kernel uevent
    KERNEL[5077.662572] add /devices/pci0000:00/0000:00:02.1/usb2/2-8 (usb)
    KERNEL[5077.662655] add /devices/pci0000:00/0000:00:02.1/usb2/2-8/2-8:1.0 (usb)
    UDEV [5077.681178] add /devices/pci0000:00/0000:00:02.1/usb2/2-8 (usb)
    UDEV [5077.693035] add /devices/pci0000:00/0000:00:02.1/usb2/2-8/2-8:1.0 (usb)
    Don't know what to do ... is a udev-rule necessary to bring up the message from device-manger? Or is the Camera not recognized as a mtp-device (the Camera has no such settings)? How could i figure it out?
    With Digikam i could import Fotos, but i would do so with gwenview. I've tried to check it out with gwenview_importer:
    $ gwenview_importer --udi '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:02.1/usb2/2-8'
    QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    gwenview_importer: Missing required source folder argument.
      (don't care about the different udi, i took this example from a former try) but i don't know, how to find out where the "source folder" is ...
    Last edited by quiqueck (2014-02-26 20:10:25)

    I have solved this by making an extra udev-rule for my camera. See my adventure on forum.kde.org for details

  • Questions on mobile device management

    Hi All,
    I'm not sure where to post this question since I couldn't find a forum specific to Afaria, so thought someone here might be able to help.
    1. Afaria mobile device management solution claims that data and content is backed up and can be deleted if a device is stolen or lost. Can this deletion be done if the mobile is switched off of the SIM card has been removed? What is the mechanism of the data deletion process when the device is either ON/OFF?
    2. How does Afaria handle online and offline user authentication? If a mobile app is opened, can Afaria be configured to force the user to enter credentials for authentication? Or should there be a separate login page as a part of the mobile app? (The user's credentials are needed to find his role from LDAP and the rest of the app to work properly, which is y the question).
    Thanks & Regards,
    Vaishnavi

    This forum is fine for Afaria discussions and questions, no worries. 
    1.  If mobile device is switched off or not network connected then Afaria is not able to do anything with that device.  The content though would be secured, encrypted etc. so that there should be no risk as long as the device is switched off.  The "kill device" command that can be sent from Afaria will work if device is turned on and connected to a network.
    2.  Afaria can force quite a lot of things and one of them is regarding the device itself, forcing a password/pin type of unlocking.  The mobile app normally has it's own mechanism for authentication, user name and password.  That is a SUP function and has little to do with Afaria, I don't believe Afaria can force that part of authentication. 
    You can get a good overview of the technical part of Afaria here:  [Afaria Technical White paper|http://www.sybase.com/files/White_Papers/Afaria-Technical-WP.pdf]

  • The Ultimate Guide to Resolving Profile and Device Manager Issues

    The following article also applies to issues after re-setting the severs' hostname. It also applies to situations where re-setting the Code Signing Certifictateas described by Apple has not resolved the issue.
    Hello,
    I have been plagued with Profile Manager and Device Manager issues since day one.
    I would like to share my experience and to suggest a way how to resolve issues such as device cannot be enrolled or Code Signing Certificate not accepted.
    I shall try to be as brief as possible, just giving an overview of the steps that resolved my issues. The individual steps have been described elsewhere in this forum. For users who have purchased commercial SSL certs the following may not apply.
    In my view many of these issues are caused by missing or faulty certificates. So let us first touch on the very complex matter of certificates.
    Certificates come in many flavours such as CA (Certificate Authority), Code Signing Certificate, S/MIME and Server Identification.
    (Mountain?) Lion Server creates a so-called Intermediate CA certificate (IntermediateCA_hostname_1") and Server Identification Certificate ("hostname") when it installs first. This is critical for the  operation of many server functionalities, including Open Direcory. These certs together with the private/public keys can be found in your Keychain. Profile  and Device Manager may need a Code Signing Certificate.
    The most straightforward way to resolve the Profile Manaher issues is in my view to reset the server created certicates.
    The bad news is that this procedure involves quite a few steps and at least 2 hours of your precious time because it means creating a fresh Direcory Master.
    I hope that I have not forgotten to mention an important step. Readers' comments and addenda are welcome.
    I shall outline a sensible strategy:
    1. Clone your dysfunctional server to an external harddrive (SuperDuper does a reliable job)
    2. Start the server fom the clone and shut down ALL services.
    3. It may be sensible to set up a root user access.
    4. Back-up all user data such as addess book, calendar and other data that you *may* need to set up your server.
    5. Open Workgroup Manager and export all user and workgroup accounts to the drive that you using to re-build your server (it may cause problems if you back-up to an external drive).
    6. Just in case you may also want to back-up the Profile Manager database and erase user profiles:
    In Terminal (this applies to Lion Server - paths may be diferent in Mountain Lion !)
    Backup: sudo pg_dump -U _postgres -c device_management > $HOME/device_management.sql
    Erase database:
    sudo /usr/share/devicemgr/backend/wipeDB.sh
    7. Note your Directory (diradmin) password for later if you want to re-use it.
    8. Open Open Server Admin and demote OD Master to Standalone Directory.
    9. In Terminal delete the old Certificate Authority
    sudo rm -R /var/root/Library/Application\ Support/Certificate\ Authority/
    This step is crucial because else re-building you OD Master will fail.
    9. Go back to Server Admin and promote the Standalone Directory to OD Master. You may want to use the same hostname.
    10. When the OD Master is ready click on Overview and check that the LDAP and Keberos Realm reflect your server's hostname.
    11. Go back to Workgroup Manager and re-import users and groups.
    NOTE: passwords are not being exported. I do not know how to salvage user passwords. (Maybe passwords can be recovered by re-mporting an OD archive - comments welcome! ).
    12. Go to Server App and reset passwords and (not to forget) user homefolder locations, in particular if you want to login from a network account!
    If the home directory has not been defined you cannot login from a network account.
    13. You may now want to restore Profile Manager user profiles in Terminal. Issue the following commands:
    sudo serveradmin stop devicemgr
    sudo serveradmin start postgres
    sudo psql -U _postgres -d device_management -f $HOME/device_management.sql
    sudo serveradmin start devicemgr
    14. You can now switch back on your services, including Profile Manager.
    In Profile Manager you may have to configure Device Management. This creates a correct Code Signng Certicate.
    15. Check the certificate settings in Server App -> Hadware -> Settings-> SSL Certificates.
    16. Check that Apple Push Notifications are set.(you easily check if they are working later)
    17. You may want to re-boot OS Server from the clone now.
    18. After re-boot open Server App and check that your server is running well.
    19. Delete all profiles in System Preferences -> Profiles.
    19. Login to Profile Manager. You should have all users and profiles back. In my experience devices have to be re-enrolled before profiles can be pushed and/or devices be enrolled. You may just as well delete the displayed devices now.
    20. Grab one of your (portable) Macs that you want to enrol and go to (yourhostname)/mydevices and install the server's trust profile. The profile's name  should read "Trust Profile for...) and underneath in green font "Verified".
    21. Re-enrol that device. At this stage keep your finger's crossed and take a deep breath.
    22. If the device has been successfully enrolled you may at last want to test if pushing profiles really works. Login to Profile Manager as admin, select the newly enrolled device. Check that Automatic Push is enabled (-> Profile -> General). Create a harmless management profile such as defining the dock's position on the target machine. (Do not forget to click SAVE at the end - this is easily missed here). If all is well Profile Manager will display an active task (sending) and the dock's position on the target will have changed in a few seconds if you are on a LAN (Note: If sending seems to take forever: check on the server machine and/or on your router that the proper ports are open and that incoming data is not intercepted by Little Snitch or similar software).
    Note: if you intend to enrol an Apple iPhone you may first need to install the proper Apple Configuration software.
    Now enjoy Profile and Device Manager !
    Regards,
    Twistan

    HI
    1. In Action profiles, logon to system and recheck correcion are available in action definition as well in condition configuration and the schedule condition is also maintained. but the display is not coming(i.e in the worklist this action is not getting displayed).
    You can check the schedule condition for the action and match the status values...or try recreating the action with schedule condition again....for customer specific ....copy the standard aciton with ur zname and make a schedule condition and check the same.
    2, In suppport team of incident when i give individual processor it throwing a warning that u r not the processor. but when i give org unit it is working perfectly. Could anyone guide on this.
    You need to have the empolyee role for BP ..goto BP and got here dropdown for ur bp and choose role Employee and then enter ur userid
    also make sure that u have the message processing role
    Hope it clarifies ur doubt and resolve ur prob
    Regards
    Prakhar

  • Device Manager error

    I have a MS-7582 motherboard and I'm getting a device error with this location.
    PCI bus 5, device 0, function 0
    Device manager says....
    The drivers for this device are not installed. (Code 28)
    There is no driver selected for the device information set or element.
    I have no idea what this is or what driver I should be looking for.
    Anyone have any idea?

    Added signature.... guess I'll see if it worked with this post.
    Badboy.   I've been to that download page before I just wasn't sure it was the one listed as lan driver.
    Anyway.   I downloaded that one and in the process of installing discovered it may still not be the driver I need.
    By that I mean the problem one is not listed under my "Network drivers" its the next tab down under the "other drivers" tab.   
    Its listed as a PCI Device with a location of  PCI bus 5, device 0, function 0
    And this is the status.
    The drivers for this device are not installed. (Code 28)
    There is no driver selected for the device information set or element.

  • Can no longer use HP device manager to scan to OCR

    Today I tried to use the HP device manager with an HP J4550 all in one to scan a document to OCR.  Not only could the scanner not be found, but the HP device manager also crashed...  I used to be able to do this prior to upgrading to Lion.  Is there a fix somehow or somewhere?
    24" iMac with 2.8Ghz Intel Core 2 and 4Gb of ram...OS X 10.7.2.  I should add that printing works fine, I can just no longer scan using Photoshop Elements 8 or the HP scanning software inside of the hp device manager..

    No I didn't but I finally DID try HP scan instead of Scan Pro in the Hewlett Packard folder located in the application folder and was able to scan to an RTF file with the OCR doing quite well in the process.  I haven't done this in some time and perhaps before I also used HP scan to do OCR scanning.  Bottom line, I am able to do again what I wanted to do...

  • My dvd drive not recognized in device manager,ge​tting the yellow explanatio​n mark.

    my dvd drive not recognized in device manager,getting the yellow explanation mark. Tried uninstallingdevice drive and scanning for new hardware. scanned for updates, etc. I getting no results. The laptop is a Pavilion DV5. Thanks 

    Hi,
    It could be that the drive has a Hardware issue, but try the following.
    From the Start Menu, open All Programs, open Accessories, right click the Command Prompt and select 'Run as Administrator'.  In to the prompt type the following command and hit enter.
    sfc /scannow                 ( note that there is a space between sfc and the / )
    Let the process complete, then type exit and hit enter.  
    Next, open Device Manager, right click the DVD drive and select Uninstall.  When this has completed, restart the notebook and let Windows rediscover the device and check.
    Regards,
    DP-K
    ****Click the White thumb to say thanks****
    ****Please mark Accept As Solution if it solves your problem****
    ****I don't work for HP****
    Microsoft MVP - Windows Experience

  • Java ME SDK 3.0-"Cannot connect to device manager" on port 1299 error HELP!

    Hello,
    I am running Vista 32 bit. I just downloaded the Java ME sdk 3.0. It installed "successfully". I just tried to launch it several times and it gets stuck in the error below. In summary, something about "Connection refused to host: localhost; DeviceManagerConnection error". Why am I getting that error? This is the first time I installed this.
    I run netstat -an, and nothing shows that something is taking up my 1299 port. Also "ping localhost" returns ::1:. And my hosts file looks good. Windows Defender and Firewall are both off. Does anyone have had this issue in the past? If so, please kindly let me know how you resolved it. Thank you.
    [ 1052] INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://localhost:1299/device-manager
    [ 2189] WARN - mpl.ObjectServerConnectionImpl - Remote object server is not running at service:jmx:rmi:///jndi/rmi://localhost:1299/device-manager
    [ 2297] INFO - l.process.GenericProcessRunner - Starting process: C:\Java_ME_platform_SDK_3.0/bin/device-manager.exe
    [ 23372] ERROR - un.jme.toolkit.bootstrap.Batch - Problem calling start() on DeviceManagerConnection
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.jme.toolkit.bootstrap.Batch.invoke(Unknown Source)
    at com.sun.jme.toolkit.bootstrap.Batch.tryInvoke(Unknown Source)
    at com.sun.jme.toolkit.bootstrap.Batch.startObjects(Unknown Source)
    at org.netbeans.modules.javame.common.container.Module.start(Module.java:21)
    at org.netbeans.modules.javame.common.container.ContainerSupport.startModule(ContainerSupport.java:67)
    at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManagerConnection(DevicemanagerHelper.java:41)
    at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.ensureConnected(DevicemanagerHelper.java:48)
    at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManager(DevicemanagerHelper.java:84)
    at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.ensureDMStarted(AutoInstaller.java:292)
    at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.restored(AutoInstaller.java:63)
    at org.netbeans.core.startup.NbInstaller.loadCode(NbInstaller.java:421)
    at org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:342)
    at org.netbeans.ModuleManager.enable(ModuleManager.java:906)
    at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:428)
    at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:364)
    at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:276)
    at org.netbeans.core.startup.Main.getModuleSystem(Main.java:165)
    at org.netbeans.core.startup.Main.start(Main.java:312)
    at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
    java.net.ConnectException: Connection refused: connect]
    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
    at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
    at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.connect(Unknown Source)
    at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.start(Unknown Source)
    ... 24 more
    Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
    java.net.ConnectException: Connection refused: connect]

    Hi there,
    I believe I am having the problem reported by the first person in this thread.
    In fact, I installed NetBeans and ran a Java ME sample and it gave me the following error
    Jad URL for OTA execution: http://localhost:8082/servlet/org.netbeans.modules.mobility.project.jam.JAMServlet/C%3A/Users/Afamefuna/Documents/NetBeansProjects/CurrencyConverter3/dist//CurrencyConverter3.jad
    Starting emulator in execution mode
    +{color:#ff0000}*C:\Users\Afamefuna\Documents\NetBeansProjects\CurrencyConverter3\nbproject\build-impl.xml:889:*{color} Execution failed with error code 1.+
    BUILD FAILED (total time: 26 seconds)
    Of course, I went to the file but the stipulated line didn't make much sense. Eventually, I seperately installed Java(TM) ME Platform SDK 3.0, but when I doubled clicked on its icon to open it, the initial splashscreen showed up, but when the progress bar got to "+{color:#ff0000}starting modules....{color}+", it gave me a java.net.ConnectionException error.
    When I went to the generated log file, amongst other things, it also contained the following snippet
    +Connecting to service:jmx:rmi:///jndi/*{color:#ff0000}rmi://localhost:1299/device-manager{color}< </strong>[  23398] ERROR - un.jme.toolkit.bootstrap.Batch - Problem calling start() on DeviceManagerConnection java.lang.reflect.InvocationTargetException+
    + at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
    + at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
    + at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
    From the above I can only imagine there is a problem with the device manager set-up for SDK, but how can it be solved?
    The device manager icon shows up in the windows toolbar, however, the "device manager" menu choice is greyed out.
    This same problem was replicated in my friend's PC, so I am certain this has to do with low-grade packaging/programming from the vendor end.
    Please how do I solve this problem? I am hoping that solving one problem, resolves the other.
    thanks
    ABCDEFGH1JKLMNOPQRSTUVWXYZ

  • Fatal Error with Java ME Device Manager and SDK Updates

    I recently installed the Java ME 3 EA SDK Platform which looks promising. Everything seem to work fine. In the process of new updates and the desire to remove some older versions of Java, I installed a new Java versions (1.6.0_11) and removed some old ones (1.6_0_04 and 1.6_0_10).
    Following this whenever I startup my machine, following the attempted start of the Java ME Device Manager, I get a "Fatal Error: Cannot start child. Error code: 0" dialog.
    Following this I get an exception indicating:
    java.net.ConnectException: Connection refused: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
         at java.net.Socket.connect(Socket.java:519)
         at java.net.Socket.connect(Socket.java:469)
         at java.net.Socket.<init>(Socket.java:366)
         at java.net.Socket.<init>(Socket.java:180)
         at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
         at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
    Caused: java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
         java.net.ConnectException: Connection refused: connect
         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
         at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
         at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
         at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
         at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
         at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97)
    Caused: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
         java.net.ConnectException: Connection refused: connect]
         at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
         at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1871)
         at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1841)
         at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
    Caused: java.io.IOException: Failed to retrieve RMIServer stub
         at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:323)
         at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
         at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.connect(Unknown Source)
         at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.start(Unknown Source)
         at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.lookupMBean(Unknown Source)
         at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.findObject(Unknown Source)
         at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.openConnection(DevicemanagerHelper.java:56)
         at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManager(DevicemanagerHelper.java:73)
         at org.netbeans.modules.j2me.cdc.platform.jme_sdk.autoinstaller.AutoInstaller.ensureDMStarted(AutoInstaller.java:228)
         at org.netbeans.modules.j2me.cdc.platform.jme_sdk.autoinstaller.AutoInstaller.restored(AutoInstaller.java:65)
         at org.netbeans.core.startup.NbInstaller.loadCode(NbInstaller.java:419)
         at org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:340)
         at org.netbeans.ModuleManager.enable(ModuleManager.java:888)
         at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:428)
         at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:364)
         at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:276)
         at org.netbeans.core.startup.Main.getModuleSystem(Main.java:163)
         at org.netbeans.core.startup.Main.start(Main.java:315)
         at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110)
    [catch] at java.lang.Thread.run(Thread.java:619)
    When I try to start the SDK itself, I also get "Cannot find java.exe in specified jdkhome. Neither E:\java\jdk1.6.0_10\jre\bin\java.exe or E:\java\jdk11.6.0.0_10\bin\java.exe exists. Do you want to try to use default version?". This also happens with I try starting Netbeans as well.
    When I say No, it appears to not start at all. When I say Yes, it appears to try to start but I continually get errors as listed above for the Java ME Device Manager startup error.
    After reinstalling the _10 version, things started to work again, so I suspect this is due to my removal of the an older version of the JDK.
    How is the proper way to "update" without causing similar errors? Are the environment variable JAVA_HOME, JAVA2_HOME, or some other variable used to specify the JDK/JRE in use? I would rather not be forced to change my startup each time to specify a -jdkhome related parameter.
    Should I install the new version, find install the "Java Platform" in the SDK/Netbeans, set it as
    Also...
    How do you set the default version from within the SDK/Netbeans?
    And is there a way to prevent the Device Manager from starting?
    Eric

    You can try this link to see if it solves your problem.
    [http://java.lillegutt.com/?p=3]
    Cheers,

  • I've found 'Blackberry Device Manager' running in the background of my Mac? But its been deleted? How do I get rid?

    I've just upgraded my MacBook Pro to a new Retina model, and while looking at the activity monitor I've noticed I still have an app running in the background that I thought had been deleted? Its the 'Blackberry Device Manager'? (See photo)
    I've tried doing a spotlight search to try and find the program and delete? It's not in my apps list?
    So I'm stuck and need some help? Thank you

    That is a LaunchAgent. You will find it in the /Home/Library/LaunchAgents/ or /Library/LaunchAgents/ folder. To delete it you will have to first kill the process in Activity Monitor, then drag the file to the Trash and delete it. If the process reappears, then drag the item to the Trash and restart the computer, after which you can Empty the Trash.
    Exposing the /Home/Library/ Folder
    Pick one of the following methods:
    A. This method will make the folder visible permanently. Open the Terminal application in your Utilities folder and paste the following at the command prompt:
    chflags nohidden ~/Library
    Press RETURN.
    B. Click on the Desktop, press the OPTION (⌥) button, select Library from the Finder's Go menu.
    C. Select Go To Folder from the Finder's Go menu. Paste the following in the path field:
    ~/Library
    Press the Go button.

  • PCI-6221 fails self-test in MAX but device manager says it's working

    Hi everyone,
    I bought a few PCI-6221 (37-pin) data acquisition cards and have been able to get one to work but 3 others don't work.
    Device Manager sees them and says they work.  MAX sees them and when I run Self Test, they fail with error number
    -50002.  Motherboards in non-working systems are PC Chips M957G and P25G.  OS is Windows XP Pro with SP2.
    I already tried uninstalling SW and the board, reinstalling SW and the
    board...autodetect etc works fine.  I even reformatted
    the HD on one of the computers and reinstalled the OS.  Anyone have any ideas?  Thanks in advance.  Halden
    [email protected]

    Thanks Tom for your suggestion to try NI-DAQ 8.0.  I just saw it today.  Yesterday,
    I was able to isolate 3 PCI-6221-37 boards as defective because they all wouldn't work in another computer while
    one other identical model card did work in that same computer.  I called to arrange to return them to NI and learned
    that for these 3, I needed NI-DAQ 8.0.  The fourth one was okay
    with NI-DAQ 7.5.  Apparently, this was a known problem. 
    I wish NI would have simply notified me that my boards would
    not work with the software sent with them and sent the NIDAQ 8.0 CD as soon as they knew rather than have me
    waste a day of my engineering time trying to figure it all out.  Booo NI.
    One of the boards has worked for almost a day under NIDAQ 8.0.  I was able to make some progress on the
    system I am building.  But then it stopped working.  LabVIEW
    (version 7.0 executable) programs would not open completely
    or would open slowly.  One that accessed the COM port only (no
    data acquisition) did work.  MAX opened very slowly or not at all
    and when I click on
    Devices and Interfaces, the hourglass is up for a long time and finally the + icon goes away indicating that MAX is not
    aware of any devices being present.  The Windows Device Manager says the board is present and working.  Windows
    Task Manager lists LabVIEW Runtime and MAX when only MAX is open and indicates that MAX is Not Responding.
    I shut down the computer, removed the PCI-6221 board, booted it up again, and MAX is the same way.  I uninstalled
    MAX and NI-DAQ LabVIEW 7.0 support and then reinstalled them.
    Now the MAX loading window is up for more than a minute and NIMAX.exe is listed in Task Manager's processes.  After
    the first minute, LabVIEW Runtime appears in the Task Manager's
    Applications list.  After a while longer, the MAX window finally
    opens
    and MAX is listed in the Applications.  I click on the + icon by Devices and Interfaces in MAX and the hourglass appears
    and Windows Task Manager says MAX is Not Responding.  Eventually, the + icon and the hourglass go away and
    the Task Manager lists LabVIEW Runtime and MAX as Running.
    I shut the computer off for several minutes, started it up again, and MAX is still takes a long, long time to open. 
    I haven't put the PCI-6221 card back in because MAX still isn't working.
    What do you suggest I do next?
    Thanks
    Halden

  • "Device Manager is running in read-only mode because you are running it on a remote computer" when local

    Hello - since configuring a Windows Web Server 2008 R2 x64 to be hardened for an internet-facing deployment I receive this:
    "Device Manager is running in read-only mode because you are running it on a remote computer."
    when entering Device Manager.
    I have tried reversing the changes I have made, such as:
    - Re-adding Client for Microsoft Networks
    - Re-enabling NetBIOS over TCP-IP
    - Re-adding File and Printer Sharing
    - Disabling the Windows Firewall in all profiles (public, domain, private)
    I get no joy. It looks like a Microsoft ballsup. I'll try and use Process Monitor to have a look. Google returns only 1 page for this error.
    Luke

    Got it.
    After my changes to DHCP and static IPs the machine picked up the IP address of another server on my little home LAN. The hostname in IPCONFIG was different to the actual server computer name and so this led Device Manager to think the connection and the
    local machine were different.
    What an odd and infuriating problem. My thoughts on this are that Microsoft should be more verbose with error messages and their causes. For example, displaying the values of the assertion would help diagnose a problem; "The host-name www02.farm.brand.com
    that you are connecting from does not match the local host-name rest01.dev.farm.brand.com. Connections from remote computers can only use Device Manager in read-only mode; some options will be disabled."
    When troubleshooting, the main thing on an engineer's mind is "what has led Windows to its [unexpected] conclusion?"
    Luke

  • How to specify a wildcard in LMS 4.2 Device Manager

                       I am in the process of transitioning from LMS 3.2 to LMS 4.2.    Device Manager in LMS 3.2 uses asterisk as a wildcard when searching for a device.   When I use the asterisk in LMS 4.2 it does not work.   For instance I enter VCG1* and get "The device is not available in the Device Credential Repository, or you are not authorized to view the device details."   VCG100-IT-AX is visible, selectable, and editable if I select the icon to list the devices available.    How do wildcards work in LMS 4.2 Device Manager?

    You're welcome. Thanks for the rating.
    Here's an example:
    LMS01/sysadmin# show version
    Cisco Application Deployment Engine OS Release: 2.0
    ADE-OS Build Version: 2.0.1.043
    ADE-OS System Architecture: x86_64
    Copyright (c) 2005-2010 by Cisco Systems, Inc.
    All rights reserved.
    Hostname: LMS01
    Version information of installed applications
    Cisco Prime LAN Management Solution
    Version  : 4.2.1
    Vendor   : Cisco Systems, Inc.
    LMS01/sysadmin# shell
    Enter shell password :
    Starting shell...
    [LMS01/root-ade ~]# uname -a
    Linux LMS01 2.6.18-238.1.1.el5 #1 SMP Tue Jan 4 13:32:19 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
    [LMS01/root-ade ~]#ls -a
    .   .bash_history  .bash_profile  .cshrc    .rnd  .tcshrc          bin          install.log.syslog
    ..  .bash_logout   .bashrc        .lesshst  .ssh  anaconda-ks.cfg  install.log
    [LMS01/root-ade ~]# pwd
    /root
    [LMS01/root-ade ~]#

  • IOS Mobile Device Management - The SCEP server returned an invalid response

    I am in the process of writing an open source iOS mobile device management module in Java. For this I am referring the Apple provided Ruby code at [1]. I have set this up and it works fine for me. Now I need to convert this code to Java. So far I have accomplished to do that up to PKIOperation. In the PKI operation I get "The SCEP server returned an invalid response" which I believe is due to wrong response I sent to device upon PKIOperation.
    However when I do search on the internet I get this is something to do with the "maxHttpHeaderSize" as I am using the server as Apache Tomcat. Although I increase that since still it does not get resolved.
    Here is the code I need to convert - taken from Apple provided Ruby script
    if query['operation'] == "PKIOperation"
        p7sign = OpenSSL::PKCS7::PKCS7.new(req.body)
        store = OpenSSL::X509::Store.new
        p7sign.verify(nil, store, nil, OpenSSL::PKCS7::NOVERIFY)
        signers = p7sign.signers
        p7enc = OpenSSL::PKCS7::PKCS7.new(p7sign.data)
        csr = p7enc.decrypt(@@ra_key, @@ra_cert)
        cert = issueCert(csr, 1)
        degenerate_pkcs7 = OpenSSL::PKCS7::PKCS7.new()
        degenerate_pkcs7.type="signed"
        degenerate_pkcs7.certificates=[cert]
        enc_cert = OpenSSL::PKCS7.encrypt(p7sign.certificates, degenerate_pkcs7.to_der,
            OpenSSL::Cipher::Cipher::new("des-ede3-cbc"), OpenSSL::PKCS7::BINARY)
        reply = OpenSSL::PKCS7.sign(@@ra_cert, @@ra_key, enc_cert.to_der, [], OpenSSL::PKCS7::BINARY)
        res['Content-Type'] = "application/x-pki-message"
        res.body = reply.to_der
    end
    So this is how I written this in Java using Bouncycastle library.
    X509Certificate generatedCertificate = generateCertificateFromCSR(
                    privateKeyCA, certRequest, certCA.getIssuerX500Principal()
                            .getName());
            CMSTypedData msg = new CMSProcessableByteArray(
                    generatedCertificate.getEncoded());
            CMSEnvelopedDataGenerator edGen = new CMSEnvelopedDataGenerator();
            edGen.addRecipientInfoGenerator(new JceKeyTransRecipientInfoGenerator(
                    receivedCert).setProvider(AppConfigurations.PROVIDER));
            CMSEnvelopedData envelopedData = edGen
                    .generate(
                            msg,
                            new JceCMSContentEncryptorBuilder(
                                    CMSAlgorithm.DES_EDE3_CBC).setProvider(
                                    AppConfigurations.PROVIDER).build());
            CMSSignedDataGenerator gen = new CMSSignedDataGenerator();
            ContentSigner sha1Signer = new JcaContentSignerBuilder(
                    AppConfigurations.SIGNATUREALGO).setProvider(
                    AppConfigurations.PROVIDER).build(privateKeyRA);
            List<X509Certificate> certList = new ArrayList<X509Certificate>();
            CMSTypedData cmsByteArray = new CMSProcessableByteArray(
                    envelopedData.getEncoded());
            certList.add(certRA);
            Store certs = new JcaCertStore(certList);
            gen.addSignerInfoGenerator(new JcaSignerInfoGeneratorBuilder(
                    new JcaDigestCalculatorProviderBuilder().setProvider(
                            AppConfigurations.PROVIDER).build()).build(
                    sha1Signer, certRA));
            gen.addCertificates(certs);
            CMSSignedData sigData = gen.generate(cmsByteArray, true);
            return sigData.getEncoded();
    The returned result here will be output in to the servlet output stream with the content type "application/x-pki-message".
    It seems I get the CSR properly and I generate the X509Certificate using following code.
    public static X509Certificate generateCertificateFromCSR(
            PrivateKey privateKey, PKCS10CertificationRequest request,
            String issueSubject) throws Exception {
        Calendar targetDate1 = Calendar.getInstance();
        targetDate1.setTime(new Date());
        targetDate1.add(Calendar.DAY_OF_MONTH, -1);
        Calendar targetDate2 = Calendar.getInstance();
        targetDate2.setTime(new Date());
        targetDate2.add(Calendar.YEAR, 2);
        // yesterday
        Date validityBeginDate = targetDate1.getTime();
        // in 2 years
        Date validityEndDate = targetDate2.getTime();
        X509v3CertificateBuilder certGen = new X509v3CertificateBuilder(
                new X500Name(issueSubject), BigInteger.valueOf(System
                        .currentTimeMillis()), validityBeginDate,
                validityEndDate, request.getSubject(),
                request.getSubjectPublicKeyInfo());
        certGen.addExtension(X509Extension.keyUsage, true, new KeyUsage(
                KeyUsage.digitalSignature | KeyUsage.keyEncipherment));
        ContentSigner sigGen = new JcaContentSignerBuilder(
                AppConfigurations.SHA256_RSA).setProvider(
                AppConfigurations.PROVIDER).build(privateKey);
        X509Certificate issuedCert = new JcaX509CertificateConverter()
                .setProvider(AppConfigurations.PROVIDER).getCertificate(
                        certGen.build(sigGen));
        return issuedCert;
    The generated certificate commonn name is,
    Common Name: mdm(88094024-2372-4c9f-9c87-fa814011c525)
    Issuer: mycompany Root CA (93a7d1a0-130b-42b8-bbd6-728f7c1837cf), None
    [1] - https://developer.apple.com/library/ios/documentation/NetworkingInternet/Concept ual/iPhoneOTAConfiguration/Introduction/Introduction.html

    I am in the process of writing an open source iOS mobile device management module in Java. For this I am referring the Apple provided Ruby code at [1]. I have set this up and it works fine for me. Now I need to convert this code to Java. So far I have accomplished to do that up to PKIOperation. In the PKI operation I get "The SCEP server returned an invalid response" which I believe is due to wrong response I sent to device upon PKIOperation.
    However when I do search on the internet I get this is something to do with the "maxHttpHeaderSize" as I am using the server as Apache Tomcat. Although I increase that since still it does not get resolved.
    Here is the code I need to convert - taken from Apple provided Ruby script
    if query['operation'] == "PKIOperation"
        p7sign = OpenSSL::PKCS7::PKCS7.new(req.body)
        store = OpenSSL::X509::Store.new
        p7sign.verify(nil, store, nil, OpenSSL::PKCS7::NOVERIFY)
        signers = p7sign.signers
        p7enc = OpenSSL::PKCS7::PKCS7.new(p7sign.data)
        csr = p7enc.decrypt(@@ra_key, @@ra_cert)
        cert = issueCert(csr, 1)
        degenerate_pkcs7 = OpenSSL::PKCS7::PKCS7.new()
        degenerate_pkcs7.type="signed"
        degenerate_pkcs7.certificates=[cert]
        enc_cert = OpenSSL::PKCS7.encrypt(p7sign.certificates, degenerate_pkcs7.to_der,
            OpenSSL::Cipher::Cipher::new("des-ede3-cbc"), OpenSSL::PKCS7::BINARY)
        reply = OpenSSL::PKCS7.sign(@@ra_cert, @@ra_key, enc_cert.to_der, [], OpenSSL::PKCS7::BINARY)
        res['Content-Type'] = "application/x-pki-message"
        res.body = reply.to_der
    end
    So this is how I written this in Java using Bouncycastle library.
    X509Certificate generatedCertificate = generateCertificateFromCSR(
                    privateKeyCA, certRequest, certCA.getIssuerX500Principal()
                            .getName());
            CMSTypedData msg = new CMSProcessableByteArray(
                    generatedCertificate.getEncoded());
            CMSEnvelopedDataGenerator edGen = new CMSEnvelopedDataGenerator();
            edGen.addRecipientInfoGenerator(new JceKeyTransRecipientInfoGenerator(
                    receivedCert).setProvider(AppConfigurations.PROVIDER));
            CMSEnvelopedData envelopedData = edGen
                    .generate(
                            msg,
                            new JceCMSContentEncryptorBuilder(
                                    CMSAlgorithm.DES_EDE3_CBC).setProvider(
                                    AppConfigurations.PROVIDER).build());
            CMSSignedDataGenerator gen = new CMSSignedDataGenerator();
            ContentSigner sha1Signer = new JcaContentSignerBuilder(
                    AppConfigurations.SIGNATUREALGO).setProvider(
                    AppConfigurations.PROVIDER).build(privateKeyRA);
            List<X509Certificate> certList = new ArrayList<X509Certificate>();
            CMSTypedData cmsByteArray = new CMSProcessableByteArray(
                    envelopedData.getEncoded());
            certList.add(certRA);
            Store certs = new JcaCertStore(certList);
            gen.addSignerInfoGenerator(new JcaSignerInfoGeneratorBuilder(
                    new JcaDigestCalculatorProviderBuilder().setProvider(
                            AppConfigurations.PROVIDER).build()).build(
                    sha1Signer, certRA));
            gen.addCertificates(certs);
            CMSSignedData sigData = gen.generate(cmsByteArray, true);
            return sigData.getEncoded();
    The returned result here will be output in to the servlet output stream with the content type "application/x-pki-message".
    It seems I get the CSR properly and I generate the X509Certificate using following code.
    public static X509Certificate generateCertificateFromCSR(
            PrivateKey privateKey, PKCS10CertificationRequest request,
            String issueSubject) throws Exception {
        Calendar targetDate1 = Calendar.getInstance();
        targetDate1.setTime(new Date());
        targetDate1.add(Calendar.DAY_OF_MONTH, -1);
        Calendar targetDate2 = Calendar.getInstance();
        targetDate2.setTime(new Date());
        targetDate2.add(Calendar.YEAR, 2);
        // yesterday
        Date validityBeginDate = targetDate1.getTime();
        // in 2 years
        Date validityEndDate = targetDate2.getTime();
        X509v3CertificateBuilder certGen = new X509v3CertificateBuilder(
                new X500Name(issueSubject), BigInteger.valueOf(System
                        .currentTimeMillis()), validityBeginDate,
                validityEndDate, request.getSubject(),
                request.getSubjectPublicKeyInfo());
        certGen.addExtension(X509Extension.keyUsage, true, new KeyUsage(
                KeyUsage.digitalSignature | KeyUsage.keyEncipherment));
        ContentSigner sigGen = new JcaContentSignerBuilder(
                AppConfigurations.SHA256_RSA).setProvider(
                AppConfigurations.PROVIDER).build(privateKey);
        X509Certificate issuedCert = new JcaX509CertificateConverter()
                .setProvider(AppConfigurations.PROVIDER).getCertificate(
                        certGen.build(sigGen));
        return issuedCert;
    The generated certificate commonn name is,
    Common Name: mdm(88094024-2372-4c9f-9c87-fa814011c525)
    Issuer: mycompany Root CA (93a7d1a0-130b-42b8-bbd6-728f7c1837cf), None
    [1] - https://developer.apple.com/library/ios/documentation/NetworkingInternet/Concept ual/iPhoneOTAConfiguration/Introduction/Introduction.html

Maybe you are looking for