Microsoft KB Archive/238754

= MOD2000: SetupC.log File Contents for End-User Client Components =

Article ID: 238754

Article Last Modified on 7/31/2001

-

APPLIES TO


 * Microsoft Office 2000 Developer Edition

-



This article was previously published under Q238754



SUMMARY
When you install the Microsoft Access Workflow Designer End-User Client Components, log information is written to a file named SetupC.log. By default, the SetupC.log file resides in the following folder:

Program Files\Microsoft Office Developer folder.

NOTE: If you have previously installed the developer components, the SetupC.log file is overwritten when you install the end-user client components.



MORE INFORMATION
During the installation of the Access Workflow Designer End-User Client Components (sometimes referred to as the Client Run-Time Components), the SetupC.log file logs the following:
 * The date and time that the Access Workflow Designer client components are installed.
 * System information including the boot drive, CPU, default language, RAM, and operating system version.
 * The computer name, username, and domain name of the person installing the Access Workflow Designer client components.
 * Checking for the installation of Microsoft Access.
 * Checking for the installation of MSDE and Microsoft SQL Server SP1.
 * Checking for the installation of the Access Server design tools (DDS) and Access SQL namespace file.

NOTE: The Access SQL namespace and Access server design tools items are only part of the developer and client components installations. This is one difference you see compared to the server components installation (logged in SetupS.log).
 * Checking for the installation of Microsoft Internet Explorer 5.0.
 * Checking for the modSystem database.
 * Registering Microsoft Office 2000 Developer files.
 * Setting registry values.

The following is a complete sample SetupC.log on a computer with Microsoft Windows 98 and Microsoft Office 2000 Premium:

11:28:07 Microsoft Office Developer Setup Log File 11:28:07 System Info: 11:28:07 DATE: 11-19-1999 11:28:07 TIME: 11:28:07 11:28:07 BOOTUPDRIVE: C: 11:28:07 CPU: Pentium 11:28:07 EXTENDEDMEMORY: 63M 11:28:07 LANGUAGE: English 11:28:07 IS_LANGUAGE: English 11:28:07 LANGUAGE_DRV: 11:28:07 OS: Windows 95 or Windows 98 11:28:07 OSMAJOR: 4.10 11:28:07 OSMINOR: 4.10

11:28:07 CMDLINE: -i 11:28:07 CMDLINE: -i 11:28:07 Loading System Support DLLs 11:28:07 Loading Application Support DLLs 11:28:07 Computer Name: COMPUTER 11:28:07 User Name: USER 11:28:07 Domain Name: DOMAIN 11:28:07 IsDomainController: COMPUTER 11:28:07 Return Code: 0 11:28:07 Return Code: 0 11:28:07 Checking for FrontPage Web Server Extensions (WEC dlls). 11:28:08 Found. 11:28:08 Checking for Access. 11:28:08 Checking for Access Server design tools (DDS). 11:28:08 Checking for Access SQL namespace file. 11:28:08 Found. 11:28:08 Checking for SQL Server 7.0, Service Pack 1. 11:28:08 SQL Install Path: C:\MSSQL7\Install 11:28:08 SQL Binn Path: C:\MSSQL7\binn 11:28:08 SQL Data Path: C:\MSSQL7 11:28:08 SQL Version: 7.00.623 11:28:08 SQL Version (Service Pack): 7.00.699 11:28:08 Checking for Internet Explorer 5.0. 11:28:08 Internet Explorer Version: 5.00.2614.3500 11:28:10 Checking for which SQL services are running. 11:28:10 The following SQL service(s) was found running: 11:28:10 Starting SQL service(s): MSSQLServer 11:28:20 Return Code: 0 11:28:20 Checking for sysadmin permissions.

11:28:20 Executing: C:\MSSQL7\binn\osql.exe -U sa -P "*****" -b -n -i C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\modUserSysAdmin.sql -o C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\SQLScript.log 11:28:23 Return Code: 0

11:28:23 Checking for existence of modSystem database. (0 -> Yes)

11:28:23 Executing: C:\MSSQL7\binn\osql.exe -U sa -P "*****" -b -n -i C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\modExistModSystem.sql -o C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\SQLScript.log 11:28:25 Return Code: (ERROR?) 1 Msg 50000, Level 16, State 1, Server COMPUTER, Procedure, Line 2 [Microsoft][ODBC SQL Server Driver][SQL Server]modSystem database does not exist

11:28:26 Return Code: (ERROR?) 1 11:28:26 Database file: C:\MSSQL7\data\modsystem.mdf 11:28:26 Not Exists 11:28:26 Stopping SQL service(s): MSSQLServer 11:28:30 Return Code: 0 11:28:33 Install Directory: C:\Program Files\Microsoft Office Developer 11:28:33 Setting registry: Software\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Office Developer End-User Components, UninstallString=C:\WINDOWS\IsUninst.exe -f"C:\Program Files\Microsoft Office Developer\UninstC.isu" -c"C:\Program Files\Common Files\Microsoft Shared\Microsoft Office Developer\Uninstall\modcss.dll" 11:28:33 Moving data... 11:28:45 Starting SQL service(s): MSDTC MSSQLServerAgent MSSQLServer

11:29:05 Return Code: 0

11:29:05 Registering mod files. 11:29:05 Launching application: C:\Program Files\Common Files\Microsoft Shared\Microsoft Office Developer\Bin\modtbad.exe /RegServer 11:29:06 Launching application: C:\Program Files\Common Files\Microsoft Shared\Microsoft Office Developer\Bin\modhost.exe /RegServer

11:29:07 Setting registry values. 11:29:07 Setting registry: Software\Microsoft\Office Developer, AppPath=C:\Program Files\Microsoft Office Developer 11:29:07 Setting registry: Software\Microsoft\Office Developer, CommonFilesPath=C:\Program Files\Common Files\Microsoft Shared\Microsoft Office Developer 11:29:07 Setting registry: Software\Microsoft\Office Developer, Server=COMPUTER 11:29:07 Setting registry: Software\Microsoft\Office Developer, userid=sa 11:29:08 Setting registry: Software\Microsoft\Office Developer, dbo=sa 11:29:08 Setting registry: Software\Microsoft\Office Developer, InstallPath=C:\Program Files\Microsoft Office Developer

11:29:08 Setting up folders and menu items.

11:29:08 Installing mod system database components.

11:29:08 Executing: C:\MSSQL7\binn\osql.exe -U sa -P "*****" -b -n -i C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\modWin9x.sql -o C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\SQLScript.log 11:29:10 Return Code: 0 New login created.

11:29:10 Executing: C:\MSSQL7\binn\osql.exe -U sa -P "*****" -b -n -i C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\modSystem.sql -o C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\SQLScript.log 11:29:20 Return Code: 0 The CREATE DATABASE process is allocating 0.75 MB on disk 'modSystem'. The CREATE DATABASE process is allocating 0.49 MB on disk 'modSystem_log'. Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'master.dbo.xp_modAddApp'. The stored procedure will still be created. Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'master.dbo.xp_modSyncUserList'. The stored procedure will still be created.

11:29:21 Executing: C:\MSSQL7\binn\osql.exe -U sa -P "*****" -b -n -i C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\modsystemdatabaseproccreation.sql -o C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\SQLScript.log 11:29:26 Return Code: 0 Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'master..xp_modExecute'. The stored procedure will still be created. Added the procedure modCreateSchema Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'master..xp_modExecute'. The stored procedure will still be created. Added the procedure modDropSchema Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'master..xp_modExecute'. The stored procedure will still be created. Added the procedure modCreateProcedures Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'master..xp_modExecute'. The stored procedure will still be created. Added the procedure modDropProcedures Added the procedure modExecuteTimeOutEvents

11:29:26 Executing: C:\MSSQL7\binn\osql.exe -U sa -P "*****" -b -n -i C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\modsystemmessagesENU.sql -o C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\SQLScript.log 11:29:45 Return Code: 0 New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added. New message added.

11:29:45 Executing: C:\MSSQL7\binn\osql.exe -U sa -P "*****" -b -n -i C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\modCommonSetup.sql -o C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\SQLScript.log 11:29:48 Return Code: 0

11:29:49 Executing: C:\MSSQL7\binn\osql.exe -U sa -P "*****" -b -n -i C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\modClientSetup.sql-o C:\WINDOWS\TEMP\_ISTMP4.DIR\_ISTMP0.DIR\SQLScript.log 11:29:52 Return Code: 0 (1 row affected) (1 row affected)

11:29:52 Unloading System Support DLLs 11:29:52 Setup completed.

Additional query words: setupc log

Keywords: kbinfo kbworkflowdesigner KB238754

-

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

© Microsoft Corporation. All rights reserved.