I was logged on with Administrator permissions to the server - aka, root. Since a reboot cleared the problem and the install succeeded, that is proof it was not a permissions issue. Perhaps you can think of another reason? Like, maybe this error occurs if someone is running CRM.exe when the upgrade starts? Or maybe some service has to be stopped? The events that occurred are real, in spite of how many other customers successfully upgraded.
I don't recall being presented with any install option checkboxes having to do with Quickbooks, I would have left them unchecked (which should be the default since I would never trust RH to interface with my Quickbooks installation, or QB to talk to RH). Can you tell me how these options would have been presented to me? What would they have said? In spite of the state of the checkbox, your error handling could: Detect a QB upgrade issue, inform the user and ask them, 'Do you wish to disable Quickbooks integration?'. We just ignored the errors, and hoped the install would continue, since we don't do QB integration. The error boxes don't tell the user the consequences of continuing or cancelling the install.
As you might be able to tell from my tone, we are having numerous problems with RH, on a daily basis, so our confidence in your software is severely shaken. Most prevelant is the frequent drops of the connection to the SQL database - which boots the user(s) off the system.
I emailed the upgrade errors we got to our Team Automation rep, but perhaps he did not forward them to you:
The Following Error Occurred: 5
Invalid object name 'RedHorseQB.dbo.customer'.
Could not use view or function 'qb_viewcustomer' because of binding errors.
Current Context: Run Proc File SQL.procs1.sql - Create Procedure CRM_RecurringContract : .Net SqlClient Data Provider
And:
The Following Error Occurred: 5
Invalid object name 'RedhorseQB.dbo.customertype'.
Could not use vview or function 'qb_viewCustomerType' because of binding errors.
Invalid object name 'RedHorseQB.dbo.vendortype'.
Could not use view or function 'qb_viewvendorType' because of binding errrors.
Current Context: Run Proc File SQL.triggers.sql - create trigger IMPORT_Insert : .Net SqlClient Data Provider
Reporting the version of the setup.exe is confusing and unnecessary. I'm not upgrading the setup, I'm upgrading RH - you should report the RH version to avoid confusion. By the way, I'm an experienced (26 yrs) enterprise software developer and system administrator (not a sales rep trying make RH run).