Microsoft KB Archive/242273

= MOD2000: Help Refers to Logger File as Wfe.log Instead of Modwfe.log =

Article ID: 242273

Article Last Modified on 6/26/2001

-

APPLIES TO


 * Microsoft Office 2000 Developer Edition

-



This article was previously published under Q242273





SYMPTOMS
The Logger object model of the Workflow Designer for SQL Server allows you to debug workflow script. When you run it for the first time, the Logger object creates a log file in the Windows folder. The Developer's Guide Help topic titled "Logger Object Model Reference" refers to this log file as the Wfe.log. However, the actual log file name that is created is the Modwfe.log.

NOTE: The Workflow Designer for SQL Server was formerly called the Access Workflow Designer.



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



Steps to Reproduce the Behavior
NOTE: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

 Install both the Workflow Designer for SQL Server server and the developer components. On the Start menu, point to Programs, point to Microsoft Office 2000 Developer, point to Access Workflow Designer, and click Developer's Guide online help. On the Index tab, type logger object . At the top of the left pane, double-click the Logger object model. Note that the topic "Logger Object Model Reference" appears. Read the first sentence there. Note that the Workflow log file is referred to as Wfe.log. Deploy the Issue Tracking application to your server. (To perform this step, follow the steps in, "Creating a Team Solution Based on a Team Template" in the Administrator's or Developer's Guide Online Help.)</li> At the end of this process, the sample Access project Issuetracking.adp appears. Leave it open.</li> Start the Workflow Designer for SQL Server.</li> In the Object list, click the Workflow Processes folder plus sign (+) to expand the folder.</li> Click IssuesWorkflow.</li> Click the Shared Script tab.</li> Search for the Sub State1_OnCreate procedure.</li> Before the "Session.Item.UpdateBatch" line, add this line:

Logger.PrintString("Added new issue")

</li> Click Verify Script (to ensure there are no syntax errors).</li> Quit the Workflow Designer for SQL Server and save the changes.</li> Click Start, click Run, and then type the following line in the Open box:

http:// /IssueTracking/default.htm

</li> Add a new issue, and then save it.</li> Click Start, point to Find, and then click Files or Folders.</li> Search for "*.log" (without the quotation marks) on the hard disk where Microsoft Windows is installed. Note that the Modwfe.log file is stored in the computer's Windows folder (which, by default, is the C:\WINNT folder for Microsoft Windows NT computers). Note that the Wfe.log file does not exists on the hard disk.</li> Open the Modwfe.log file in Notepad or in any text editor. Note that the entry "Added new issue" appears in the file as expected.</li></ol>

Additional query words: pra incorrect can not cannot can't find Wfe log Modwfe

Keywords: kbbug kbnofix kbdocerr KB242273

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.