I am trying to install SP5 for SQL Server 6.5. On my client machine the service pack installs with no problem. On the server i get an error like
"setup initilization could not be succesfully completed.
ISQL.exe could not be executed. Please check the relevant .OUT file
could not be executed. Please check the relevant .OUT file".
(no, thats not a typo, the second 'could not be executed' line has a blank space where a program name should be)
By doing a find on files modified in the last day i can see what .OUT files were generated by the service pack installation. All of these .OUT file contain various warnings about it not being SQL Server 7.0, and a message saying to ignore these warnings. There is only one .OUT file that does not end with the line "*.sql completed successfully"
This is the text of that one .OUT file.
[Proc65_3.SQL]
Starting Install\Proc65_3.SQL at 13 Oct 2000 13:11:23:763
Making sure that updates to system tables are allowed.
Configuration option changed. Run the RECONFIGURE command to install.
Time established during sequence mode 1 before creates is '2000/10/13
13:11:25' (spid=10, db=master)
Insert sysmessages....
Insert spt_values type='TBO' , sp_tableoption.
Creating 'sp_db_upgrade2'.
Creating 'sp_namecrack_qi'.
Creating 'sp_tableoption'.
Creating 'sp_fallback_MS_enroll_dev'.
Creating 'sp_fallback_MS_enroll_usg'.
Creating 'sp_fallback_MS_verify_ri'.
Creating 'sp_fallback_activate_svr_db'.
Creating 'sp_rename'.
Creating 'sp_password'.
Creating 'sp_processmail'.
Creating 'sp_helpconstraint'.
Creating 'sp_recompile'.
Creating 'sp_columns'.
Creating 'sp_fkeys'.
Creating 'sp_helpsort'.
The datetime established earlier during sequence mode 1 was
'2000/10/13 13:11:25' (spid=10, db=master)
The number of objects updated with category | 2 was 15. (spid=10,
db=master)
DELETE useless sysprotects duplicates where grantor is null...
NumDeleted DBName
----------- ------------------------------
0 master
NumDeleted DBName
----------- ------------------------------
0 model
NumDeleted DBName
----------- ------------------------------
0 msdb
NumDeleted DBName
----------- ------------------------------
0 pubs
NumDeleted DBName
----------- ------------------------------
0 tempdb
DELETE... ended.
Configuration option changed. Run the RECONFIGURE command to install.
CHECKPOINTing database that was changed.
Time established during sequence mode 1 before creates is '2000/10/13
13:12:00' (spid=10, db=msdb)
Creating trigger 'syshistory_row_limiter'...
Creating procedure 'sp_verifytaskdate'...
Creating procedure 'sp_verifytasktime'...
Creating procedure 'sp_purgehistory'...
Creating procedure 'sp_updatealert'...
The datetime established earlier during sequence mode 1 was
'2000/10/13 13:12:00' (spid=10, db=msdb)
The number of objects updated with category | 2 was 5. (spid=10,
db=msdb)
I'm not sure that this has anything to do with the problem, as it seems to have completed, but i thought it might be helpful.
Has anyone seen this or a similar problem? I can't debug my stored procedures till i get this SP installed. Help!
TIA [sig]<p>Ruairi<br><a href=mailto:ruairi@logsoftware.com>ruairi@logsoftware.com</a><br>Experienced with: <br>
VB6, SQL Server, QBASIC, C(unix), MS Office VBA solutions<br>
ALSO: Machine Control/Automation using GE and Omron PLC's and HMI(human machine interface) for industrial applications[/sig]
"setup initilization could not be succesfully completed.
ISQL.exe could not be executed. Please check the relevant .OUT file
could not be executed. Please check the relevant .OUT file".
(no, thats not a typo, the second 'could not be executed' line has a blank space where a program name should be)
By doing a find on files modified in the last day i can see what .OUT files were generated by the service pack installation. All of these .OUT file contain various warnings about it not being SQL Server 7.0, and a message saying to ignore these warnings. There is only one .OUT file that does not end with the line "*.sql completed successfully"
This is the text of that one .OUT file.
[Proc65_3.SQL]
Starting Install\Proc65_3.SQL at 13 Oct 2000 13:11:23:763
Making sure that updates to system tables are allowed.
Configuration option changed. Run the RECONFIGURE command to install.
Time established during sequence mode 1 before creates is '2000/10/13
13:11:25' (spid=10, db=master)
Insert sysmessages....
Insert spt_values type='TBO' , sp_tableoption.
Creating 'sp_db_upgrade2'.
Creating 'sp_namecrack_qi'.
Creating 'sp_tableoption'.
Creating 'sp_fallback_MS_enroll_dev'.
Creating 'sp_fallback_MS_enroll_usg'.
Creating 'sp_fallback_MS_verify_ri'.
Creating 'sp_fallback_activate_svr_db'.
Creating 'sp_rename'.
Creating 'sp_password'.
Creating 'sp_processmail'.
Creating 'sp_helpconstraint'.
Creating 'sp_recompile'.
Creating 'sp_columns'.
Creating 'sp_fkeys'.
Creating 'sp_helpsort'.
The datetime established earlier during sequence mode 1 was
'2000/10/13 13:11:25' (spid=10, db=master)
The number of objects updated with category | 2 was 15. (spid=10,
db=master)
DELETE useless sysprotects duplicates where grantor is null...
NumDeleted DBName
----------- ------------------------------
0 master
NumDeleted DBName
----------- ------------------------------
0 model
NumDeleted DBName
----------- ------------------------------
0 msdb
NumDeleted DBName
----------- ------------------------------
0 pubs
NumDeleted DBName
----------- ------------------------------
0 tempdb
DELETE... ended.
Configuration option changed. Run the RECONFIGURE command to install.
CHECKPOINTing database that was changed.
Time established during sequence mode 1 before creates is '2000/10/13
13:12:00' (spid=10, db=msdb)
Creating trigger 'syshistory_row_limiter'...
Creating procedure 'sp_verifytaskdate'...
Creating procedure 'sp_verifytasktime'...
Creating procedure 'sp_purgehistory'...
Creating procedure 'sp_updatealert'...
The datetime established earlier during sequence mode 1 was
'2000/10/13 13:12:00' (spid=10, db=msdb)
The number of objects updated with category | 2 was 5. (spid=10,
db=msdb)
I'm not sure that this has anything to do with the problem, as it seems to have completed, but i thought it might be helpful.
Has anyone seen this or a similar problem? I can't debug my stored procedures till i get this SP installed. Help!
TIA [sig]<p>Ruairi<br><a href=mailto:ruairi@logsoftware.com>ruairi@logsoftware.com</a><br>Experienced with: <br>
VB6, SQL Server, QBASIC, C(unix), MS Office VBA solutions<br>
ALSO: Machine Control/Automation using GE and Omron PLC's and HMI(human machine interface) for industrial applications[/sig]