Article ID: 318705 - Last Review: June 21, 2003 - Revision: 1.1

FIX: Writing .ini Files to Network Location with Windows Installer Results in Error 1913

This article was previously published under Q318705
Expand all | Collapse all

SYMPTOMS

When you run a setup program that was authored to use the Windows Installer, and you write to an .ini file that is on a secured network, you may receive an error 1913 that is similar to the following:
Product: test -- Error 1913.
Could not update the ini file \\<servername>\<path>\<filename>.ini.

Verify that the file exists and that you can access it.

CAUSE

This behavior is caused by a bug in the Windows Installer engine, which occurs when the following conditions exist:
  • The Windows Installer processes .msi files.
  • The .msi files that are being processed were authored to write .ini files by using the IniFile table.
  • The target location of the .ini files is set to a secured network location.

RESOLUTION

Windows NT 4.0 or Windows 2000

On a computer that is running Windows NT 4.0 or Windows 2000, use the following location to download the correct update:
Windows Installer 2.0 Redistributable for Windows NT 4.0 and 2000 (http://www.microsoft.com/downloads/release.asp?ReleaseID=32832)

Windows 95/98/Me

On a computer that is running Microsoft Windows 95, Microsoft Windows 98 or Microsoft Windows Millennium Edition, use the following location to download the correct update:
Windows Installer 2.0 Redistributable for Windows 95, 98, and Me (http://www.microsoft.com/downloads/release.asp?ReleaseID=32831)

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Although you can work around this problem by allowing Everyone to have write access on the network share to which the .ini file is being written, this creates a significant security issue. Microsoft does not recommend this workaround.

APPLIES TO
  • Microsoft Windows Installer 2.0
Keywords: 
kbappsetup kbbug kbfix kbsetup KB318705
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
 

Article Translations