So we have a web project install and I've recently ran up against something kind of weird.  All of a sudden we're getting a 1606 error.  The weird thing about it is that it seems to show some database fields.  I believe the Database fields are found as a result of some SQL connection information we enter during the install.

Can anyone help me figure out what is happening with this...

Action 9:21:54: CostFinalize. Computing space requirements
Action start 9:21:54: CostFinalize.
MSI (s) (00:68) [09:21:54:369]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.
MSI (s) (00:68) [09:21:54:369]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.
MSI (s) (00:68) [09:21:54:369]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.
MSI (s) (00:68) [09:21:54:369]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.
MSI (s) (00:68) [09:21:54:369]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.
MSI (s) (00:68) [09:21:54:372]: PROPERTY CHANGE: Modifying USERPROFILE property. Its current value is 'C:\Users\Charlie.Smith'. Its new value: 'C:\Users\Charlie.Smith\'.
MSI (s) (00:68) [09:21:54:372]: PROPERTY CHANGE: Modifying ALLUSERSPROFILE property. Its current value is 'C:\ProgramData'. Its new value: 'C:\ProgramData\'.
MSI (s) (00:68) [09:21:54:373]: PROPERTY CHANGE: Adding ISYourDataBaseDir property. Its value is 'C:\inetpub\wwwroot\Database\'.
MSI (s) (00:68) [09:21:54:377]: Note: 1: 1314 2: ACTUALFIX, BUGSTATUS, BUGTITLE, BUGTYPE, c_BUGLOG, C_COMPANY, C_CONTACT, C_EXTIMD, C_ESTIMT, C_FEATURE, C_FIXCMT, C_LOC, C_NOTES, C_PMCMT, C_QAREV, C_SECFEAT, C_SEVERITY, C_VERFIX, C_VERFIX1, CP_PROG, CPPRIORITY, CPPRJCT, CPPRJTYP, CPUPGRDTO, CPUPGRDTP, DATECLOSED, DATEFOUND, FIX_VER, FOUNDBY, HPRGAREA, L_ADDED, L_BEHAVIOR, L_DOC, L_ESCALATE, L_OPTIMIZE, L_UPDATE, MENTIONED, N_BUGAUTO, N_FAILED, N_PASSED, OS, PERSON, PRIORITY, PROG_VER, R_CADVER, R_CLSDBY, R_DBTYPE, R_IMPLTVRN, R_INTEGRAT, R_INTFACE, R_NUMREPOR, R_PRODSPEC, R_WSHLISTP, R_WSHSTAT, T_DATE_1, T_DATE_2, T_DATE_3, T_DATE_4, T_DATE_5, T_DATE_6, T_DATE_7, T_DATE_8, T_DATE_9, T_DATE_10, T_DATE_11, T_DATE_12, T_DATE_13, T_DATE_14, T_DATE_15, T_NAME_1, T_NAME_2, T_NAME_3, T_NAME_4, T_NAME_5, T_NAME_6, T_NAME_7, T_NAME_8, T_NAME_9, T_NAME_10, T_NAME_11, T_NAME_12, T_NAME_13, T_NAME_14, T_NAME_15, T_PER_1, T_PER_2, T_PER_3, T_PER_4, T_PER_5, T_PER_6, T_PER_7, T_PER_8, T_PER_9, T_PER_10, T_PER_11, T_PER_12, T_PER_13, T_PER_14, T_PER_15, T_SPRINT1, T_YN_1, T_YN_2, T_YN_3, T_YN_4, T
MSI (s) (00:68) [09:21:54:377]: Note: 1: 1606 2: ACTUALFIX, BUGSTATUS, BUGTITLE, BUGTYPE, c_BUGLOG, C_COMPANY, C_CONTACT, C_EXTIMD, C_ESTIMT, C_FEATURE, C_FIXCMT, C_LOC, C_NOTES, C_PMCMT, C_QAREV, C_SECFEAT, C_SEVERITY, C_VERFIX, C_VERFIX1, CP_PROG, CPPRIORITY, CPPRJCT, CPPRJTYP, CPUPGRDTO, CPUPGRDTP, DATECLOSED, DATEFOUND, FIX_VER, FOUNDBY, HPRGAREA, L_ADDED, L_BEHAVIOR, L_DOC, L_ESCALATE, L_OPTIMIZE, L_UPDATE, MENTIONED, N_BUGAUTO, N_FAILED, N_PASSED, OS, PERSON, PRIORITY, PROG_VER, R_CADVER, R_CLSDBY, R_DBTYPE, R_IMPLTVRN, R_INTEGRAT, R_INTFACE, R_NUMREPOR, R_PRODSPEC, R_WSHLISTP, R_WSHSTAT, T_DATE_1, T_DATE_2, T_DATE_3, T_DATE_4, T_DATE_5, T_DATE_6, T_DATE_7, T_DATE_8, T_DATE_9, T_DATE_10, T_DATE_11, T_DATE_12, T_DATE_13, T_DATE_14, T_DATE_15, T_NAME_1, T_NAME_2, T_NAME_3, T_NAME_4, T_NAME_5, T_NAME_6, T_NAME_7, T_NAME_8, T_NAME_9, T_NAME_10, T_NAME_11, T_NAME_12, T_NAME_13, T_NAME_14, T_NAME_15, T_PER_1, T_PER_2, T_PER_3, T_PER_4, T_PER_5, T_PER_6, T_PER_7, T_PER_8, T_PER_9, T_PER_10, T_PER_11, T_PER_12, T_PER_13, T_PER_14, T_PER_15, T_SPRINT1, T_YN_1, T_YN_2, T_YN_3, T_YN_4, T
Error 1606. Could not access network location ACTUALFIX, BUGSTATUS, BUGTITLE, BUGTYPE, c_BUGLOG, C_COMPANY, C_CONTACT, C_EXTIMD, C_ESTIMT, C_FEATURE, C_FIXCMT, C_LOC, C_NOTES, C_PMCMT, C_QAREV, C_SECFEAT, C_SEVERITY, C_VERFIX, C_VERFIX1, CP_PROG, CPPRIORITY, CPPRJCT, CPPRJTYP, CPUPGRDTO, CPUPGRDTP, DATECLOSED, DATEFOUND, FIX_VER, FOUNDBY, HPRGAREA, L_ADDED, L_BEHAVIOR, L_DOC, L_ESCALATE, L_OPTIMIZE, L_UPDATE, MENTIONED, N_BUGAUTO, N_FAILED, N_PASSED, OS, PERSON, PRIORITY, PROG_VER, R_CADVER, R_CLSDBY, R_DBTYPE, R_IMPLTVRN, R_INTEGRAT, R_INTFACE, R_NUMREPOR, R_PRODSPEC, R_WSHLISTP, R_WSHSTAT, T_DATE_1, T_DATE_2, T_DATE_3, T_DATE_4, T_DATE_5, T_DATE_6, T_DATE_7, T_DATE_8, T_DATE_9, T_DATE_10, T_DATE_11, T_DATE_12, T_DATE_13, T_DATE_14, T_DATE_15, T_NAME_1, T_NAME_2, T_NAME_3, T_NAME_4, T_NAME_5, T_NAME_6, T_NAME_7, T_NAME_8, T_NAME_9, T_NAME_10, T_NAME_11, T_NAME_12, T_NAME_13, T_NAME_14, T_NAME_15, T_PER_1, T_PER_2, T_PER_3, T_PER_4, T_PER_5, T_PER_6, T_PER_7, T_PER_8, T_PER_9, T_PER_10, T_PER_11, T_PER_12, T_PER_13, T_PER_14, T_PER_15, T_SPRINT1, T_YN_1, T_YN_2, T_YN_3, T_YN_4, T_YN_5, T_YN_6, T_YN_7, T_YN_8, T_YN_9, T_YN_10, T_YN_11, T_YN_12, T_YN_13, T_YN_14, T_YN_15.
MSI (s) (00:50) [09:22:03:832]: I/O on thread 6916 could not be cancelled. Error: 1168
MSI (s) (00:50) [09:22:03:832]: I/O on thread 6932 could not be cancelled. Error: 1168
MSI (s) (00:50) [09:22:03:832]: I/O on thread 6936 could not be cancelled. Error: 1168
MSI (s) (00:50) [09:22:03:832]: I/O on thread 6940 could not be cancelled. Error: 1168
MSI (s) (00:50) [09:22:03:832]: I/O on thread 1688 could not be cancelled. Error: 1168
MSI (s) (00:50) [09:22:03:832]: I/O on thread 4252 could not be cancelled. Error: 1168
MSI (s) (00:50) [09:22:03:832]: I/O on thread 4712 could not be cancelled. Error: 1168
MSI (s) (00:50) [09:22:03:832]: I/O on thread 5076 could not be cancelled. Error: 1168
MSI (s) (00:50) [09:22:03:832]: I/O on thread 4672 could not be cancelled. Error: 1168
MSI (s) (00:50) [09:22:03:832]: I/O on thread 4920 could not be cancelled. Error: 1168
MSI (s) (00:68) [09:22:03:833]:
MSI (s) (00:68) [09:22:03:834]: Note: 1: 1606 2: ACTUALFIX, BUGSTATUS, BUGTITLE, BUGTYPE, c_BUGLOG, C_COMPANY, C_CONTACT, C_EXTIMD, C_ESTIMT, C_FEATURE, C_FIXCMT, C_LOC, C_NOTES, C_PMCMT, C_QAREV, C_SECFEAT, C_SEVERITY, C_VERFIX, C_VERFIX1, CP_PROG, CPPRIORITY, CPPRJCT, CPPRJTYP, CPUPGRDTO, CPUPGRDTP, DATECLOSED, DATEFOUND, FIX_VER, FOUNDBY, HPRGAREA, L_ADDED, L_BEHAVIOR, L_DOC, L_ESCALATE, L_OPTIMIZE, L_UPDATE, MENTIONED, N_BUGAUTO, N_FAILED, N_PASSED, OS, PERSON, PRIORITY, PROG_VER, R_CADVER, R_CLSDBY, R_DBTYPE, R_IMPLTVRN, R_INTEGRAT, R_INTFACE, R_NUMREPOR, R_PRODSPEC, R_WSHLISTP, R_WSHSTAT, T_DATE_1, T_DATE_2, T_DATE_3, T_DATE_4, T_DATE_5, T_DATE_6, T_DATE_7, T_DATE_8, T_DATE_9, T_DATE_10, T_DATE_11, T_DATE_12, T_DATE_13, T_DATE_14, T_DATE_15, T_NAME_1, T_NAME_2, T_NAME_3, T_NAME_4, T_NAME_5, T_NAME_6, T_NAME_7, T_NAME_8, T_NAME_9, T_NAME_10, T_NAME_11, T_NAME_12, T_NAME_13, T_NAME_14, T_NAME_15, T_PER_1, T_PER_2, T_PER_3, T_PER_4, T_PER_5, T_PER_6, T_PER_7, T_PER_8, T_PER_9, T_PER_10, T_PER_11, T_PER_12, T_PER_13, T_PER_14, T_PER_15, T_SPRINT1, T_YN_1, T_YN_2, T_YN_3, T_YN_4, T
Error 1606. Could not access network location ACTUALFIX, BUGSTATUS, BUGTITLE, BUGTYPE, c_BUGLOG, C_COMPANY, C_CONTACT, C_EXTIMD, C_ESTIMT, C_FEATURE, C_FIXCMT, C_LOC, C_NOTES, C_PMCMT, C_QAREV, C_SECFEAT, C_SEVERITY, C_VERFIX, C_VERFIX1, CP_PROG, CPPRIORITY, CPPRJCT, CPPRJTYP, CPUPGRDTO, CPUPGRDTP, DATECLOSED, DATEFOUND, FIX_VER, FOUNDBY, HPRGAREA, L_ADDED, L_BEHAVIOR, L_DOC, L_ESCALATE, L_OPTIMIZE, L_UPDATE, MENTIONED, N_BUGAUTO, N_FAILED, N_PASSED, OS, PERSON, PRIORITY, PROG_VER, R_CADVER, R_CLSDBY, R_DBTYPE, R_IMPLTVRN, R_INTEGRAT, R_INTFACE, R_NUMREPOR, R_PRODSPEC, R_WSHLISTP, R_WSHSTAT, T_DATE_1, T_DATE_2, T_DATE_3, T_DATE_4, T_DATE_5, T_DATE_6, T_DATE_7, T_DATE_8, T_DATE_9, T_DATE_10, T_DATE_11, T_DATE_12, T_DATE_13, T_DATE_14, T_DATE_15, T_NAME_1, T_NAME_2, T_NAME_3, T_NAME_4, T_NAME_5, T_NAME_6, T_NAME_7, T_NAME_8, T_NAME_9, T_NAME_10, T_NAME_11, T_NAME_12, T_NAME_13, T_NAME_14, T_NAME_15, T_PER_1, T_PER_2, T_PER_3, T_PER_4, T_PER_5, T_PER_6, T_PER_7, T_PER_8, T_PER_9, T_PER_10, T_PER_11, T_PER_12, T_PER_13, T_PER_14, T_PER_15, T_SPRINT1, T_YN_1, T_YN_2, T_YN_3, T_YN_4, T_YN_5, T_YN_6, T_YN_7, T_YN_8, T_YN_9, T_YN_10, T_YN_11, T_YN_12, T_YN_13, T_YN_14, T_YN_15.
MSI (s) (00:68) [09:22:04:766]:
Action ended 9:22:04: CostFinalize. Return value 3.
Action ended 9:22:04: INSTALL. Return value 3.
Property(S): CURRENTDIRECTORY = C:\Windows\system32
Property(S): CLIENTUILEVEL = 0
Property(S): CLIENTPROCESSID = 3196
Property(S): DiskPrompt = [1]
Property(S): UpgradeCode = {13125C10-F4DA-4F5B-9144-78024D46EE4C}
Property(S): ProductCode = {26734A57-40E5-4DA9-BB2F-9524513702DF}
Property(S): ServicePackLevel = 1

I don't recall making any recent changes.  Also, I run this on another machine pointing to another database and its fine.  I then thought maybe something fluky was going on with the database, so on the problematic machine I tried pointing to the success test database and the same error occurs.

I've read some things regarding 1606 errors and problematic directory table entries, but there's been no changes there that I can recall.

Any help appreciated!

1 Comment   [ + ] Show Comment

Comments

  • What looks like db fields, is in fact that, but they are being pulled from a web config file on upgrade, property set, then written to the config file again via Text File Changes. This has been working up until now. I wonder if there is a length issue with the string I dump in the property.
Please log in to comment

Answers

0
Validate your MSI. I'll bet you have a missing/incorrect entry in the Directory table or possibly have gained a property whose name matches a Directory table entry.
Answered 07/18/2016 by: VBScab
Red Belt

Please log in to comment
0

I thought about all of that, but luckily an actual change to our app saved me.

The install had a front end Custom Action that would run and grab .config file entries if the file existed and store them in properties.  I think the value that held the database field names was too long or at least that is all I can come up with.

Our developers have since moved that value to the database the application accesses so there is no longer a need to maintain it in the config file.  So I commented the grab of that value from the front end widget and removed the Text File Replacement that used the property and all went through fine.

One thing you mentioned that I am terrible about is validating the database.  I should start doing that if it aids in finding directory table problems, etc.  However, in this case it was a runtime issue so I don't know that it would have caught anything.

Answered 07/18/2016 by: Superfreak3
Black Belt

  • What is perplexing is that I'm not so sure this is was a property value length issue. I recall in the past working with ini values in the InstallShield interface and something we needed added to an ini file contained a huge value. It was too long for the .ini table I believe so I used a Property to store the value first then used the Property in the ini view of IS. The value that seemed to be causing the problem this time was just a comma delimited list of database fields.
Please log in to comment
0
>I should start doing that
You need to be intelligent about warnings and errors, remembering that the validation can be a bit dumb. For example, it might flag an incorrect key path when what you have, on purpose, is an empty key path.
Answered 07/19/2016 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity