ZDM Agent "Invalid Drive Path"

We use Zenworks to install software and use the Zenworks folders to display the program shortcut icon. After installed, it will launch (Run options tab > Application > Path to file) and the program will start. I'm having an issue for the last couple weeks that some users are seeing:
0xD001
Could not get needed resources for application [application name] to be launched (id=number).
Problem: Invalid drive path [specified drive path]
The same NAL app is working fine for other users. I have confirmed on the faulty pc that the program will run manually and through a Windows shortcut link. The only thing I have noticed is the users that its failing on has ZDM 6.5 agent. If I upgrade them to ZDM 7, its fixed!
Apparently there is alot of pc's which still have ZDM 6.5 but I'm only hearing a few complaints. I know a fix is to upgrade to ZDM 7 but we have a conflicting issue if they have the ZCM inventory agent, the upgrade will kill DLU policy.
Any ideas to discover why this is happening all of a sudden and possible fix?

You could try having the App launch your program from the "Launch
Script" instead of "Path to File".
This helped with some issues I had years ago.
(Might have been ZEN2 .........)
Maybe Try Killing the NALCache Folder on those devices?
On 9/23/2010 11:36 AM, Michael Fleming wrote:
>
> craig_wilson;2025774 Wrote:
>> Maybe make sure a proper working directory is set for the app?
>
> Yep the working directory is fine and even weirder the same NAL object
> works fine for ZDM 7 users (and has been working for 6.5 users). It just
> seems the last 4 weeks this error is popping up. As soon as I update
> them to ZDM 7 the error goes away. Unfortunately I can't have ZDM agent
> update as the solution as it will require reboot and it has another
> issue which kills the DLU if ZCM is installed.
>
> I just can't pin-point whats special about these pc's or whats changed
> as there must be 100's-1000's of ZDM 6.5 out there with no issues.
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.

Similar Messages

  • "Invalid object path" Driver Import

    PS P01:\> Add-CMDriverToDriverPackage -DriverName $item.LocalizedDisplayName -DriverPackageName $HWType -verbose
    VERBOSE: Executing WQL query: SELECT * FROM SMS_DriverPackage WHERE Name='Microsoft.HyperV.W7X64'
    VERBOSE: Query options: ExpectResults
    VERBOSE: Performing the operation "Add" on target "DriverToDriverPackage: Name="Microsoft.HyperV.W7X64"".
    VERBOSE: Executing method 'RequestLock' against class 'SMS_ObjectLock'
    VERBOSE: Input properties:
    VERBOSE: -- :: ObjectRelPath == SMS_DriverPackage.PackageID="P010009C"
    VERBOSE: -- :: RequestTransfer == True
    VERBOSE: Output properties:
    VERBOSE: -- :: AssignedMachine == <SERVER>
    VERBOSE: -- :: AssignedObjectLockContext == b72216b2-de12-453a-98d6-89bbcdd88443
    VERBOSE: -- :: AssignedSiteCode == P01
    VERBOSE: -- :: AssignedTimeUTC == 10/28/2014 10:19 PM
    VERBOSE: -- :: AssignedUser == <USER>
    VERBOSE: -- :: LockState == 1
    VERBOSE: -- :: RequestID == 3F595BA4-BEAF-4707-B824-A786AD02EAD5
    VERBOSE: -- :: RequestState == 10
    VERBOSE: -- :: ReturnValue == 0
    VERBOSE: Lock acquisition on 'SMS_DriverPackage.PackageID="P010009C"' returned: Granted
    VERBOSE: Executing WQL query: SELECT * FROM SMS_Driver WHERE LocalizedDisplayName='Microsoft Hyper-V Network Adapte
    r'
    VERBOSE: Query options: ExpectResults
    VERBOSE: Query 'SELECT * FROM SMS_Driver WHERE LocalizedDisplayName='Microsoft Hyper-V Network Adapter' ' processed
    1 results.
    VERBOSE: Executing WQL query: Select CTC.ContentID From SMS_CIToContent As CTC Join SMS_Driver As DR On DR.CI_ID=CT
    C.CI_ID Where DR.CI_ID=16786189
    VERBOSE: Query options: None
    VERBOSE: Executing method 'ReleaseLock' against class 'SMS_ObjectLock'
    VERBOSE: Input properties:
    VERBOSE: -- :: ObjectRelPath == SMS_DriverPackage.PackageID="P010009C"
    VERBOSE: Output properties:
    VERBOSE: -- :: ReturnValue == 0
    VERBOSE: Lock release on 'SMS_DriverPackage.PackageID="P010009C"' success: True
    Add-CMDriverToDriverPackage : Invalid object path
    At line:1 char:2
    + Add-CMDriverToDriverPackage -DriverName $item.LocalizedDisplayName -DriverPacka ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (Microsoft.Confi...rPackageCommand:AddDriverToDriverPackageCommand) [
    Add-CMDriverToDriverPackage], WqlQueryException
    + FullyQualifiedErrorId : UnhandledExeception,Microsoft.ConfigurationManagement.Cmdlets.Osd.Commands.AddDrive
    rToDriverPackageCommand
    Does anybody know a workaround for this bug?
    Same error in Add-CMDriverToDriverPackage and Import-CMDriver
    How will be the WMI Commandlet?
    Please Help. THX

    Hi,
    Please refer to the link below:
    Import-CMDriver
    http://technet.microsoft.com/en-us/library/dn151073(v=sc.20).aspx
    More info:
    ConfigMgr Driver Injector
    This tool will help you to capture installed drivers on your workstations and then will automatically import them in ConfigMgr 2012.
    http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.
    Hi Xin Guo,
    thx for post, but you can try the syntax and it will fail, cause what i read there is since 2012 R2 CU 3 some changes also in SQL and so the command with Paramater
    -DriverPackageName
    will not work correctly and abort, so the Technet Page is here not the Solution about.
    Also i don't need an extra Tool, cause i have all driver's but for the massimport i want to use wmi, powershell.
    Help :)

  • Network drives and System Update updating itself (Error 1327.Invalid Drive)

    I have a Windows network share permanently mapped as a network drive on my system. This prevents Lenovo System Update 5 from updating itself.
    Here is what happens:
    Launch Lenovo System Update and click Next to look for updates.
    When 'Searching for agent updates' it will tell me: 'System Update is updating itself. Your copy of System Update needs to be updated. Click OK to begin updating System Update.'
    Click OK, Lenovo System Update will download the update and appear to install it.
    At the end it will tell me: 'System Update was installed successfully'
    Click Close, just to be sure I wait for a while so System Update can finish whatever it is doing in the background (if anything at all).
    When nothing appears to happen I launch Lenovo System Update manually and it will tell me it needs to update itself again, and go to the same process as above. The update did not install successfully at all. System update keeps updating itself in a loop.
    Next thing I tried is manually downloading the latest System Update version from http://support.lenovo.com/en_US/detail.page?LegacyDocID=TVSU-UPDATE
    I downloaded systemupdate503-09-17-2013.exe for my Windows 7 machine.
    The installer detects to old version of System Update and offers to uninstall that. I click Yes.
    A moment later the real error appears: 'Error 1327.Invalid Drive: S:\'
    The only thing I can do now is press OK to close the installer.
    The S:\ drive is my network drive which is permanently mapped to a share on my NAS.
    It is not an invalid drive, S:\ opens fine in Windows Explorer.
    I don't know why the System Update installer wants to access my S: drive in the first place. All my applications are installed on C:. While I did move some special folders like My Pictures and My Videos to S:, the relevant folders My Documents and Desktop are still on C:.
    I have found a workaround to the problem above:
    Close Lenovo System Update completely when it says it needs to update itself.
    Run Command Prompt as Administrator (find it in the start menu, righ-click it and 'Run as administrator').
    Type 'subst s: c:\' without the quotes. Replace s: with the drive letter of your network drive, and c: should be an existing regular drive.
    Now run Lenovo System Update again and let it update itself.
    You'll notice System Update now restarts itself after updating and there are no problems.
    Once you are done with System Update, type 'subst s: /D' to delete the substituted virtual drive. Don't worry, this will not delete your actual network drive.
    The workaround does the job, but it would be nice to see an actual fix from Lenovo. I have a ThinkPad X230 running 64bit Windows 7 Professional if this is relevant.

    Please try either of the workaround.
    1. Create a new Admin user, log on in that and then you can install Adobe Reader,
    or
    2. easier solution is just create a dummy folder on your machine anywhere, lets says Folder name "Dummy"  in c:\
    not go to command prompt
    and type subst I: c:\dummy
    and you are all set to go.
    once you are done, you can remove that virtual drive mapping by
    subst I:\  /d
    please let me know if works.

  • "Invalid Drive X:\" install errors

    Disclaimer: Apple does not necessarily endorse any suggestions, solutions, or third-party software products that may be mentioned in the topic below. Apple encourages you to first seek a solution at Apple Support. The following links are provided as is, with no guarantee of the effectiveness or reliability of the information. Apple does not guarantee that these links will be maintained or functional at any given time. Use the information below at your own discretion.
    While upgrading or uninstalling a Windows software package (such as iTunes for Windows or QuickTime for Windows), you may receive the following error message:
    Invalid Drive X:\
    ... where the red X:\ could be any drive letter (F, H, J, or so on.) Usually you won't actually have a drive with that particular drive letter on your system.
    Typically, this is caused by a problem with an installer database entry for a component for the software package. The installer database believes that the component is on the X:\ drive. When your Windows Installer goes to remove that component from the X:\ drive while uninstalling the existing version of the software and doesn't find any drive there at all it gets horribly confused and you get the "Invalid Drive" message.
    If that is what is afoot with your "Invalid Drive X:\" message, here are a couple of possible resolutions for the problem. If at all possible, attempt resolution 1 prior to trying resolution 2.
    1. Temporarily add an X:\
    drive to your system.
    2. Use the Windows Installer CleanUp utility to clear the installation database for the software you're getting the Invalid Drive X:\ message with.
    1. Temporarily add an X:\
    drive to your system.
    So long as you actually have an X:\ drive on your system, your Windows Installer will typically remain relatively calm during the uninstall of the existing software (even if it can't find the component it was looking for on the drive in question). So one way of getting past an "Invalid drive X:\" message is to temporarily add an X:\ drive to your system.
    An easy way to create the missing drive X: (thanks to turingtest2)
    Open a Windows Command prompt, e.g. Hit Start > Run, type in CMD and press OK.
    Type in SUBST X: C:\<enter>
    This will map X: to C: until the machine is restarted or you enter SUBST X: /D at the command prompt. Now you can try uninstalling or upgrading the software again. (If upgrading the software, install the software in the default location, not on the X:\ drive.)
    Otherwise, you will need an external hard drive, a thumb drive, an iPod in manual mode, or any other storage device that appears as a hard drive in "My Computer" (on Windows XP) or "Computer" (on Windows Vista or Windows 7).
    Connect the drive to your computer. (If you are using an iPod, and iTunes for Windows launches, quit iTunes.) Open My Computer (on Windows XP) or Computer (on Windows Vista or Windows 7). Check to see what drive letter has been assigned to the drive.
    If the drive letter for the drive you added matches the drive letter being given in the "Invalid Drive X:\" message, try uninstalling or upgrading the software again. (If upgrading the software, install the software in the default location, not on the X:\ drive.)
    If the drive letter for the drive you added does not match the drive letter being given in the "Invalid Drive X:\" message, try using Disk Management to change the drive letter of the drive you added so that it does match the drive letter being given in the "Invalid Drive X:\" message.
    (1) In your Start menu, right-click My Computer (on XP) or Computer (on Vista or 7), and select Manage.
    (2) In Computer Management, click Disk Management.
    (3) Right-click the drive you attached to your computer and select Change Drive Letters and Paths ...
    (4) Click Change ...
    (5) In the drop-down menu, select the letter that appears in your "Invalid Drive X:\" error message.
    (6) Click OK.
    (7) In the dialog box that comes up, click Yes.
    (8) Close Computer Management.
    (9) Try uninstalling or upgrading the software again. (If upgrading the software, install the software in the default location, not on the X:\ drive.)
    2. Use the Windows Installer CleanUp utility to clear the installation database for the software you're getting the Invalid Drive X:\ message with.
    If it isn't feasible to add a drive to your system, you can also get past an "Invalid Drive X:\" error message by using the Windows Installer CleanUp utility.
    (1) Click here first, and read the important information about the utility.
    (2) Click the Download the Windows Installer Cleanup Utility package now link on that page to download a file titled msicuu2.exe.
    (3) Open the msicuu2.exe file and follow the prompts to install it.
    (4) In your Start menu click All Programs and then click Windows Install Clean Up. The Windows Installer CleanUp utility window appears, listing software that is currently installed on your computer.
    (5) Select the software you're getting the "Invalid Drive X:\" message for from the list and click Remove.
    (6) Click OK in the confirmation dialog that appears.
    (7) If you have multiple entries for the software you're getting the "Invalid Drive X:\" message for, repeat steps 5 and 6 for the other entries for the software.
    (8) Click Exit.
    (9) Restart the computer.
    If you were getting the "Invalid Drive X:\" message when trying to upgrade software, now try reinstalling the latest version of the software.
    If you were getting the "Invalid Drive X:\" message when just trying to uninstall software, program files for the software in question will remain on the PC after it has been removed by the Windows Installer CleanUp utility. If you want to remove leftover program files, check in at the appropriate forum at Apple Discussions and ask which files can be safely removed.
    This is the 1st version of this tip. It was submitted on June 1, 2010 by b noir.
    Do you want to provide feedback on this User Contributed Tip or contribute your own? If you have achieved Level 2 status, visit the User Tips Library Contributions forum for more information.

    Hi turingtest2 & b noir,
    Sorry about the delay in getting this out. Has this been tested then? Is there even a good way to test it when the user doesn't have admin privileges?
    How would you like it integrated into the tip? How does this look?
    1. Temporarily add an X:\ drive to your system.
    So long as you actually have an X:\ drive on your system, your Windows Installer will typically remain relatively calm during the uninstall of the existing software (even if it can't find the component it was looking for on the drive in question). So one way of getting past an "Invalid drive X:\" message is to temporarily add an X:\ drive to your system.
    An easy way to create the missing drive X:
    Open a Windows Command prompt, e.g. Hit Start > Run, type in CMD and press OK.
    Type in SUBST X: C:\<enter>
    This will map X: to C: until the machine is restarted or you enter SUBST X: /D at the command prompt.
    Otherwise, you will need an external hard drive, a thumb drive, an iPod in manual mode, or any other storage device that appears as a hard drive in "My Computer" (on Windows XP) or "Computer" (on Windows Vista or Windows 7).
    Thanks,
    Nubz

  • Error 1327.Invalid Drive: E:\

    We purchased the Macromedia Studio 8 Education package for my
    school work in the hope for me to use far more advanced skills and
    uptill this day has been working fine. However with me giving this
    laptop back I am forced to put it back to it original state. This
    means taking the software off.
    With the operating systems being XP I accessed the Add/Remove
    section in Control Panel and chose first of all to remove Flash.
    Then I met this code (The Message Title). Unsure what it was I went
    onto the rest of the software and all produced the same message. I
    could really do with some quick assistance as ideally this needs to
    go back within the week.
    Thank You For Any Help

    I had a similar problem, except my error message said invalid drive letter D:\. 
    Since I have no "D" drive, I right clicked on "My Computer" and chose "Manage".
    I then went down to "Storage" and clicked on "Disk Management".  I have
    a second hard drive, but it is assigned to letter "I" (dont ask) so I right clicked on
    the "I" drive and chose "change drive letters and paths".  Next, I selected letter D
    then clicked "OK", then clicked the other "OK", closed out of Computer Management
    and restarted the installation.
    No problems after that!  After the installation, I changed the letter back to "I" (which
    you don't have to do, but it was my preference).
    I hope this helps, because it worked wonders for me!!
    -Patrick

  • Invalid Drive G:/ error message when trying to download I-Tunes 9

    I have had problems trying to download the last two versions of I-Tunes but as my ipod classic was working wasn't bothering.
    I just recieved an Ipod Nano 5th Generation for Christmas and when I plug into computer states that it needs newer version of I-Tunes.
    I go through all the process then just at the end of installing I get a message saying 'invalid drive:/G'
    I can't use my new ipod or get the latest version of I-Tunes as get error message every time.
    HELP !

    Hi Any,
    I have been getting a similar error when it gets to the quicktime phase, it says invalid G drive.
    I found some help on the web that if you go to start and run at the command prompt, type the following: "Subst G: C:\". This gets me further in the installation, but I end up getting an error that says "the specified path is too long G:\lib". At that time, my only option is to cancel out. I have tried starting in my dock with external drive plugged in and thumb drive too to avoid having to use the SUBST command. When I do it this way, I get a different error, 2869.
    I have tried just installing quicktime separately, but does not work either. Give it a try, maybe it will work for you differently. let me know your outcome, maybe you will encounter something that will help me too.

  • UTL_FILE errors,  invalid directory path ???

    Hi All,
    I am trying to create a csv output file through pl/sql.
    However i am having some issues since its my first time.
    Please have a look at the following code:
    create or replace
    PROCEDURE amer_main_proc (start_sent_date date,
                        end_sent_date date,
                        senttype number) IS
    CURSOR main_cur IS
    SELECT
              s.sent_id,
              s.ussc_id,
              s.sent_upd_date,
              s.alt_docket,
              s.amend_year,
              s.def_num,
              s.dep_status_code,
              s.var_status_code,
              s.disp_type_code,
              s.docket,
              s.oth_sent_code,
              substr(s.oth_text,1,100) oth_text,
              s.po_code,
              ind.prim_offn_code,
              s.prob_mons
    FROM      sentences s,
              submission sub,
              ind_sent ind,
              defendants def,judges j
    WHERE      s.sent_id = sub.sent_id
    AND      s.sent_id = ind.sent_id
    AND      ((sub.case_type_code in (10,11) 
    AND      trunc(sent_vio_date) between start_sent_date and end_sent_date) or
              (sub.case_type_code in (10)  AND trunc(sent_vio_date) between start_sent_date and end_sent_date) or
              (sub.case_type_code in (11) AND trunc(sent_vio_date) between start_sent_date and end_sent_date) or
              (sub.case_type_code in (11) and  s.amend_code = 10 AND trunc(sub.create_date) between start_sent_date and end_sent_date))
              AND s.def_id=def.def_id
              AND s.ao_judge_id = j.ao_judge_id
              AND sent_creator_id is not null
              AND dist_id != 99
    ORDER BY s.ussc_id, s.sent_id;
    --Define output file variables
    out_file UTL_FILE.FILE_TYPE;        /* file type */
    path_name VARCHAR2(50);            /* file path */
    file_name VARCHAR2(50);            /* file name */
    line_buffer VARCHAR2(2000);        /* store all the elements that make up one line in the output file */
    BEGIN
        path_name := 'C:\SQL';  // this folder does exist in my C drive
        file_name := 'main.txt';
        out_file := UTL_FILE.FOPEN(path_name, file_name, 'W');
        line_buffer := 'data main;';
        UTL_FILE.PUT_LINE (out_file, line_buffer);
        line_buffer := 'infile cards delimiter='','';';
        UTL_FILE.PUT_LINE (out_file, line_buffer);
        line_buffer := 'input ' ||
        'USSCIDN ' ||
        'ALT1DOC $ ' ||
        'DEPART ' ||
        'VARIAN ' ||
        'DISPOSIT ' ||
        'DOCKETID $ ' ||
        'TYPEOTHS ' ||
        'TYPEOTTX $ ' ||
        'POOFFICE $ ' ||
        'MONOFFTP ' ||
        'PROBATN ';
        UTL_FILE.PUT_LINE (out_file, line_buffer);
        FOR main_cur_rec IN main_cur LOOP
         --Writes to file
              line_buffer := main_cur_rec.ussc_id ||
              ',' || nvl(main_cur_rec.alt_docket,' ') ||
              ',' || nvl(to_char(main_cur_rec.dep_status_code),' ') ||
              ',' || nvl(to_char(main_cur_rec.var_status_code),' ') ||
              ',' || nvl(to_char(main_cur_rec.disp_type_code),' ') ||
              ',' || nvl(main_cur_rec.docket,' ') ||
              ',' || nvl(to_char(main_cur_rec.oth_sent_code),' ') ||
              ',' || nvl(main_cur_rec.oth_text,' ') ||
              ',' || nvl(to_char(main_cur_rec.po_code),' ') ||
              ',' || nvl(to_char(main_cur_rec.prim_offn_code),' ') ||
              ',' || nvl(to_char(main_cur_rec.prob_mons),' ');
              UTL_FILE.PUT_LINE (out_file, line_buffer);
         END LOOP;
         --Write SAS footer
         line_buffer := ';';
         UTL_FILE.PUT_LINE (out_file, line_buffer);
         line_buffer := 'run;';
         UTL_FILE.PUT_LINE (out_file, line_buffer);
         --Close file
         UTL_FILE.FCLOSE(out_file);
    EXCEPTION
    -- Write error messages to the screen and file
        WHEN OTHERS THEN
        DBMS_OUTPUT.PUT_LINE(SUBSTR(SQLERRM,1,50));     // this is line 106
        UTL_FILE.PUT_LINE(out_file, SUBSTR(SQLERRM,1,50));
       UTL_FILE.FCLOSE(out_file);
    END amer_main_proc;I know I am having issues regarding the path, please have a look at the ERRORS below:
    Error starting at line 1 in command:
    DECLARE
      START_SENT_DATE DATE;
      END_SENT_DATE DATE;
      SENTTYPE NUMBER;
    BEGIN
      START_SENT_DATE := '01-JAN-2001';
      END_SENT_DATE := '01-MAR-2001';
      SENTTYPE := 10;
      AMER_MAIN_PROC(
        START_SENT_DATE => START_SENT_DATE,
        END_SENT_DATE => END_SENT_DATE,
        SENTTYPE => SENTTYPE
    END;
    Error report:
    ORA-29282: invalid file ID
    ORA-06512: at "SYS.UTL_FILE", line 878
    ORA-06512: at "USSC_CASES.AMER_MAIN_PROC", line 106
    ORA-29280: invalid directory path
    ORA-06512: at line 10
    29282. 00000 -  "invalid file ID"
    *Cause:    A file ID handle was specified for which no corresponding
               open file exists.
    *Action:   Verify that the file ID handle is a value returned from a
               call to UTL_FILE.FOPEN.thanks guys.
    Edited by: Rooney on Feb 20, 2012 12:29 PM

    You'll need to create an Oracle Directory object that contains 'C:\SQL' and use that in your UTL_FILE call if you are using a 10g+ version of the database and the UTL_FILE_DIR parameter does not include your path.
    CREATE DIRECTORY my_dir AS 'C:\SQL';
    GRANT READ WRITE ON DIRECTORY my_dir TO <user>;You can then use the directory object name in the path of your UTL_FILE call.
    ORA-29280: invalid directory path Cause: A corresponding directory object does not exist.
    Action: Correct the directory object parameter, or create a corresponding directory object with the CREATE DIRECTORY command.>
    Hope this helps!

  • Import-CMDriver fails with "Import-CMDriver : Invalid object path "

    I am attempting to use Import-CMDriver but it fails with:
    "Import-CMDriver : Invalid object path "
    I can see that it is adding the driver to the catalog, but it is failing to add it to the package and I can't figure out why.  I have tried with different inf files and deleted and created different packages.  It just doesn't work.  Here is
    the command that I am running.  I don't see any reason why it wouldn't work.
     Set-Location abc:
        foreach($iniFile in $infFilesToDeploy){
            $cmDrivePackage = Get-CMDriverPackage -Name "PackageName"
            $cmDriverCat = Get-CMCategory -CategoryType "DriverCategories" -Name "PackageName"
            $cmDrivePackage
            $iniFile
            Import-CMDriver -UncFileLocation $iniFile -ImportDuplicateDriverOption AppendCategory -AdministrativeCategory $cmDriverCat -EnableAndAllowInstall $True -DriverPackage $cmDrivePackage -UpdateDistributionPointsforDriverPackage $false
    As I said, it is seeing the ini file since it it importing it into the catalog.  It just won't add it to the package.  It also leaves the package in a locked state if I try to modify it after I run this command.
    Anyone have any ideas why this command doesn't function?
    Thank you for your time.

    Hi,
    What's the version of your SCCM? I ran this command "Import-CMDriver -UncFileLocation... " on my SCCM 2012 R2 CU1. I didn't get the error above.
    I also tried the command below, it ran successful.
     $d=Get-CMDriverPackage -Id "..."
     Import-CMDriver -UncFileLocation "\\..." -DriverPackage $d -EnableAndAllowInstall $true
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • WARNING: JTS5020: Invalid log path when connecting to JTS

    Hi
    I am using JNDI to connect to JDBC resources defined in Sun's App Server from a standalone application.
    The application is not part of the J2EE container.
    I was able to sucessfully connect and execute SQL against the db passing VM params...
    my problem is that every time application runs I get the WARNING about JTS logs
    Here is a sample of my output:
    Jul 9, 2004 3:52:46 PM com.sun.jts.CosTransactions.Log checkFileExists
    WARNING: JTS5020: Invalid log path.  Using [.\jts].
    Jul 9, 2004 3:52:46 PM com.sun.jts.CosTransactions.Log checkFileExists
    WARNING: JTS5021: Invalid default log path.  Using current directory.
    Driver Information
         Driver Name: jTDS Type 4 JDBC Driver for MS SQL Server
         Driver Version: 0.8
    Database Information
         Database Name: Microsoft SQL Server
         Database Version: 08.00.0760Right now I am using VM parameters
    -Dorg.omg.CORBA.ORBInitialHost=localhost
    -Dorg.omg.CORBA.ORBInitialPort=3700
    Is there any way to specify the log file location so that the warning will go away?
    Thanks

    Hi,
    This message is harmless and comes, when standalone client (if you use appclient it will not come) is used. Ignoring the message is the right thing.
    regards

  • Compiling Media invalid file path error when buring a DVD

    Hello,
    I have updated to 3.0.2 Premiere Elements and the latest XP Home updates. I had 2.0 and it worked without any problems. I bought 3.0 and have had nothing but problems, I can capture, access files and put a video together but no matter if to file or to DVD I always get this error
    "Burn DVD Progress screen"
    "Compiling Media invalid file path"
    then it all stops and nothing.
    Any help or suggestions appreciated, I searched the web for this error and found nothing, when I search here I seem to get every Adobe product comes up but no premiere.
    Thank you

    I started to do the FAQ to build a clean AVI file. I also re-installed the program, did an update to 3.0.2, defrag. Made sure I had 118gig space. All in order. Still I got the errors. Then I thought perhaps since this pointed to a path that somewhere a path was not correct. So I looked under Preferences - scratch disks - and found they all pointed to the D drive where I had some old Adobe files. It appears the 2.0 version worked when I had the files stored on another partition and 3.0 did not like this. So when I moved everything in Scratch Disk to the same folder on C: where I installed 3.0 things seemed to begin to work.
    I tested it by burning to a file and then to an actual DVD and both worked well. I have a quad core chip.
    Now the problem seems to be when I edit each end of a clip, "the IN and OUT" the in does not seem to be saved or rendered. When I get to the preview I can still see and hear date prior to the SET IN. I save, re-save and re-render and it still happens. However some clips it works fine.
    Thanks again for pointing me in a direction so at least I can start to trouble shoot.

  • How do you fix error msg for Windows IE v8 SP3 invalid drive: J\ when installing Reader?

    I have tried to install the latest version (and two older ones shown on Adobes install free Reader webpage) onto Windows IE 8 sp3 get error message Invalid drive: J\, or Folder path "My Pictures" there is invalid character. I have been unable to correct these to allow  Reader to install without errors. Get to 96 % installation then these messages appear but not at the same time.  Any suggestions?

    See http://support.microsoft.com/kb/894510

  • Invalid Parent Path in Archive

    Secure Access V2.0 returned an error when I tried to open my vault. After I type in the password I get the error message, "Invalid Parent Path In Archive".  When I click 'OK' I get the standard "4 Ways To Protect Your Data" screen as usual when I open a vault. When I click the 'Next" button I get the error, "This vault could not be loaded, it may be located on another computer or the original vault file has been manually removed." After I click OK the main screen opens. It has the vault listed, but if I click on it I get the same error message.  Whats going on? How can I access my vault? It is my backup for important documents and archives. No, I haven't moved or deleted the vault. The vault is located on the memory stick.I only work from one computer running Windows 7. This particular Sandisk 32 Extreme is never used with any other computer. I haven't changed the password. Everything was working fine until I just couldn't sign in.

    Hello, There are some steps you can try in order to recover the vault files . 1) copy the vault and secure access application from the write protected drive over to the new drive2) run secure access on the new drive3) when it prompts to create a new vault go ahead and create a new vault with the exact same password as the old vault4) encrypt any file in the new vault (this will generate two new system files)5) close secure access6) open the vault folder on the new drive via windows explorer, navigate to the system files folder, you should see several files, among them are two sets of "USB Flash Drive-XXXXXXXXXXXXXXX.idx and .bak files7) Looking at the date stamps of the files, 2 will be older and 2 will be newer (you can also check on the old write protected drive to confirm the names of the older files, the older files contain the encryption information needed however the file name is associated with the previous drive we will need to rename the old files)8) copy the 2 newer files and paste them into any temporary location outside of the flash drive (i.e.. desktop)8) once you've copied the two new files to a temporary location delete the originals from the system files folder on the flash drive.9) go to the temporary location and copy only the file name from the .idx file (the file name, not the file itself)10) go to the vault / system files and rename the old .idx file with the name you copied from the new .idx file11) repeat the same for the idx.bak file12) now you should have renamed the old .idx and .idx.bak files with the names of the newly generated system files.  

  • Difficulty downloding Adobe Reader and Error 1327. Invalid Drive H:\

    I am having a difficulty downloading Adobe reader on my laptop. For some reasons, I am getting error 1327. Invalid Drive H:\ notification. I have followed the tips on how to resolve this issue from Adobe's help and FAQ pages, but I am still not able to download Adobe reader. This issue begun short while after I installed a Tuneup software from AVG. I contacted this Tuneup company, and one of it's representative guided me through the steps on how to resolve the problem; unfortunately, the correction attempt did not make any difference. Adobe tech support team can fix my issue, but at a cost of $ 40. I do not want to pay it. Hence, I am trying to solve this problem myself. Could any one, who has the knowledge to deal with this issue, please respond to my request?
    Thank you in advance for your assistance. I look forward to hearing from you.
    Best regards,
    Peter VK Mayangi

    Have you tried both solutions on the link from the earlier poster?  Microsoft Fixit did not fixit?
    If so, you will have to search the registry manually for your invalid drive H:\
    Please post back if you are unsure what to do when you find that registry entry.
    P.S. please do not post your email address and other private data in this public forum!

  • Error Message...Invalid Drive E when loading ITunes

    I have tried to download ITunes for 3 days straight, I keep getting an error message that I have an invalid Drive E. I have done disk clean up, defrag, cleaned out cookies and temp files, what else can I do? Does anyone else get this message? I am dying to use my new phone but I can not unlock or register it.

    Bissley,
    I have received this error in the past and it is usually caused by Windows automatically changing your external drive letters when you install. There are two ways around it; first, follow the directions provided by b noir. Second, within iTunes go to Edit > Preferences > Advanced
    Under the advanced options you'll see a recessed section called "iTunes Media folder location". Although you may have set this in the past it, if Windows changed your drive letters it will no longer be valid. Default is usually "C:\blah\blah\mymusic"
    Changing it just a matter of clicking "change" and finding your music folder again or change your drive letter back (if it changed at all).
    If Windows is changing your drive letters, it is best to set them yourself so that everytime you plug in the devices they use the letter you assigned. Here is a link for that process:
    http://windows.microsoft.com/en-US/windows-vista/Change-add-or-remove-a-drive-le tter
    Hope it helps.

  • I keep getting an error report 1327 invalid drive .I have tried to remove adobe reader and it won't let me , this used to work opk on my computer , but has not for quite a while now .I would like it gone from my computer

    I am having problems with adobe reader , an error message 1327 invalid drive . I have tried to remove adobe readr=er from my computer , but it wont let me . It is useless as I am unable to use it ...why can I nor remove it

    This means that something in your registry is pointing to a drive that doesn't exist; see http://support.microsoft.com/kb/327763
    Let us know if you need any help with editing the registry.

Maybe you are looking for