FIX: PDW package cannot be installed if the user name is based on DBCS characters

This article was previously published under Q293295
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
When you run a Microsoft Visual Basic 6.0 application Setup package that the Package and Deployment Wizard (PDW) generated, you may receive the following error message:
Path or File not found
This error occurs when the following conditions are true:
  • The operating system is Microsoft Windows 2000.
  • The Setup package is installed by a user whose user name contains DBCS characters.
RESOLUTION
To work around this problem, log on as a user whose user name is ANSI-based to install the application. After the installation, you can use the application when you log on as the Korean character-based user.
STATUS
To resolve this problem, obtain the latest service pack for Visual Studio 6.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
MORE INFORMATION

Steps to reproduce the problem

  1. Create an application Setup package with the Visual Basic 6.0 Package and Deployment Wizard.
  2. Click Start, point to Programs, point to Administrative Tools, and then click Computer Management.

    Note You must do this on a Windows 2000-based computer.
  3. Expand the Local Users and Groups node. Right-click Users, and then click New User. In the User name box, type a name with DBCS characters. Complete the required information to create a new user, and then click Create.
  4. Click Groups, right-click Administrators in the right pane, and then click Add to Group. Click Add, and then add the newly-created user to the Administrators group. Click OK two times.
  5. Log off, and then log on as the newly-created user.
  6. Start the application Setup package.

    You may receive the error message that is mentioned in the "Symptoms" section.
Korean Japanese PDW DBCS
Properties

Article ID: 293295 - Last Review: 02/27/2014 21:07:59 - Revision: 3.1

  • Microsoft Visual Basic 6.0 Enterprise Edition
  • Microsoft Visual Basic 6.0 Professional Edition
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbfix kbvs600sp6fix kbappsetup kbbug kbdeployment kbintldev kbnofix kbwizard KB293295
Feedback