General discussion

Locked

InstallShield Scripting runtime

By wakim ·
Hi I am receiving a popup "1607:Unable to install InstallShield Scripting runtime". I tried all I know from suggesstion I found on the web site but most are too steep for me to grab. Please help me through this problem I am just average in computer IT. My OS. windows XP Pro SP2.Thanks.

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by HAL 9000 Moderator In reply to InstallShield Scripting r ...

Here is the solution,

http://support.microsoft.com/kb/910816/

Lets know if you need any help to understand it.

Col

Collapse -

by wakim In reply to InstallShield Scripting r ...

Thanks Col I have problem in the ms.link you have given. I could not find the word "add" in the user ac. If I click on my login ac. I was given 5 selection, change my name,create a password,change my picture,change my ac. type and det up my ac. to use .net passport. I am at present in my ac.as a computer administrator. Please kindly advised further. Thanks.

Collapse -

by HAL 9000 Moderator In reply to InstallShield Scripting r ...

For Windows XP Home Edition or Windows XP Professional Edition when Windows XP is not connected to a domain
1. Click Start, click Control Panel, and then click User Accounts.
2. In the Pick a task list, click Create a new account.
3. Type the name that you want to use for the account. Then, click Next.
4. Click Administrator to select the account type, and then click Create Account.

The Add option should only appear if you are on a Domain and logged in as Admin. If you are currently on a domain and not logged in as Admin you will not see this option and you do not have the ability to install new software for this you'll need to speak to your system admin.

Comment Button has disappeared again.

Collapse -

by cyauch In reply to InstallShield Scripting r ...

In our instance, we created custom groups of users to access shared drives and folders. When implemented, ALL groups and users were removed from the root, and allowed to propagate back down with nothing. Then, the custom groups were added, as well as an administrator account. Still we were getting a 1607 error when attempting to install a Symantec A/V CE 10.0. After a few days, we decided to add back the SYSTEM user, and all worked great. Just my $0.02 because after scouring Google and even Symantec, we couldn't this solution (at the time, anyway).

Back to Desktop Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums