SUMMARY:
When the Microsoft Access Workflow Designer End-User Client Components, log information is written to install a file called SetupC.log default, the file is located in the following folder:
Program Files\Microsoft Office Developer folder.
MORE INFORMATION
During the installation of the Access Workflow Designer End-User Client Components the SetupC.log file logs the following:
1. The date and time that the Access Workflow Designer client components are installed.
2. System information with the boot drive, CPU, default language, RAM, and operating system version.
3. The PC name, username, and domain name of the person installing the Access Workflow Designer client components.
4. Checking for the installation of Microsoft Access.
5. Checking for the installation of MSDE and Microsoft SQL Server SP1.
6. Checking for the installation of the Access Server design tools (DDS) and Access SQL namespace file.
7. Checking for the installation of Microsoft Internet Explorer 5.0.
8. Checking for the modSystem database.
9. Registering Microsoft Office 2000 Developer files.
10. Setting registry values.
The following is a sample track Setup.log on a PC with Windows 98 and 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\modUserSys Admin.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\modExistMo dSystem.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



Reply With Quote
Copyright Techfuels
Bookmarks