And I upgraded directly to Win 10 Anniversary Edition. Unfortunately, I will have to say, the installation went well.īut I had Windows 7 Professional on the VM and upgraded to Windows 10 Professional. Just for the fun of it, I took a Win7 virtual machine that I had around and upgraded it to Windows 10 and installed SQL 2016 on it. You got the same arithmetic overflow this time. Indeed, it seems that they got the exception in the same class as you did. Not that the original error is particularly obvious: "Arithmetic operation resulted in an overflow."īut I searched on this error in conjunction with installation of SQL 2016, and I found some older forum threads where I had been active myself, and the common theme in those cases were that people had Windows 10 that they had upgraded from Windows 7. So that is a classic case of a failing error handler occluding the original error, making troubleshooting more difficult. Shortly after the original error was thrown. This is an error which occurs in .WatsonExceptionBucket.FormatStackFrame I looked at your logs, and I found that the error "Object reference not set to an instance of an object." is not the original error. But was that the original OS on the machine? Or did you upgrade from Windows 7?Ī little more background why I am asking this. I see from the log that you have Windows 10. It can be very difficult in some situations to install SQL 2016.
0 kommentar(er)
