Jump to content
Sign in to follow this  
Xinyong

error 1304

Recommended Posts

login as administrator ,problem also 1304.

one user is administrator only.

Share this post


Link to post
loged in remote. use Microsoft remote desktop.

 

Is it a domain or a workgroup?

If it is a workgroup try the login with workgroup\administrator

 

Is the installation file stored on the server?

Share this post


Link to post

Well, you have two ways to install Win server.

 

1-Make a local login (not terminal services) and install.

 

2-From Admin kit, install server.

 

Rafael Gómez

Share this post


Link to post
loged in localy .

problem also 1304.

377995[/snapback]

 

 

Hello,

 

on default KAV tries to protect it's modules during installation, just uncheck this with installationwizzard.

 

bb_S

Share this post


Link to post

If installation still not work move content of windows/installer directory temporary into another dir and clear up the windows temp folder.

check if the MSInstaller works correctly or install latest version - also you can check the regsitry for already existing installation paths or installation packages and delete them.

 

i also remember that 1304 was an error on older system with having an installation path including spaces. here you can change installation path to one without spaces.

 

last thing is to log the installation with one of the following options:

 

MSIEXEC VERBOSE-LOGGING

 

The following syntax is an example of a verbose log command line:

Msiexec /i Testdbsetup.msi /l*v c:\Msi.log

 

 

 

REGISTRY VERBOSE-LOGGING

 

Please add to the registry value

 

[HKEY_CURRENT_USER\SOFTWARE\InstallShield\ISWI\3.0\SetupExeLog]

"VerboseLogFileName"="C:\install.log"

 

 

SETUP.EXE VERBOSE-LOGGING

 

- extract all files from self-extracted archive to the local drive

- start installtion using Setup.exe /verbose"C:\IS.log".

- find C:\IS.log

 

/verbose : Generate verbose InstallScript engine log file (Standard projects only) For a Standard-project installation program, you can create a verbose InstallScript-engine-installation log file using the /verbose argument followed by the path to the log file you want to create. A typical command is Setup.exe /verbose"C:\IS.log". The log file generated can help you troubleshoot errors in installing the InstallScript engine on a target system. The /verbose option requires a full path to the log file, and not a relative path.

 

 

Share this post


Link to post
Sign in to follow this  

×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.