Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Installation problem with microsoft visual c++ redistribution

  • 16-07-2009 2:33pm
    #1
    malin182
    Banned (with Prison Access) Posts: 153 ✭✭


    Hi guys,

    I have been trying to install sony soundforge 9 and during the installation i get this message:

    The feature you are trying to use is on a network resource that is unavailable.

    Click OK to try again, or enter an alternate path to a folder containing the installation package 'vcredist.msi' in the box below.

    Use source:
    C:\DOCUME~1\Josh\LOCALS~1\Temp\IXP000.TMP\

    It looks for the vcredist.msi file, which i found and downloaded, although when i go to run the package it starts up and then just stops. Has anyone else had this problem and is there a solution? I am using windows vista 32bit.

    Thanks
    Tagged:


Comments

  • #2
    Capt'n Midnight
    Moderators, Recreation & Hobbies Moderators, Science, Health & Environment Moderators, Technology & Internet Moderators Posts: 93,596 Mod ✭✭✭✭Capt'n Midnight


    you may have to right click and run as administrator


  • #3
    malin182
    Banned (with Prison Access) Posts: 153 ✭✭malin182


    no that makes no difference because I am the administrator


  • #4
    cance
    Registered Users, Registered Users 2 Posts: 1,562 ✭✭✭cance


    Type the follwing at a cmd prompt

    msiexec /I c:\vcredist.msi /lv c:\c+.log /qb /norestart

    the log file it produces should give you an idea of why it fails.


Advertisement