Hi all,
patch search day today
Missed this one, it came out a few weeks ago and I still haven't installed it:
https://www.veeam.com/kb4441
I share with you..enjoy!
Hi all,
patch search day today
Missed this one, it came out a few weeks ago and I still haven't installed it:
https://www.veeam.com/kb4441
I share with you..enjoy!
Already knew about this a week or more ago and applied it to our VSPC. Thanks for sharing for the rest of the audience.
Thanks….saw this was available but haven’t applied it yet as I haven’t gathered the info around it yet. Thanks for posting for awareness though!
I tried the v7 Cumulative Patch today, to upgrade from v6 (this is a fresh install of VSP Console v6 from the Azure Marketplace, pre-installed with SQL Server 2016 64-bit).
The setup verified all the prerequisites, but errored out when trying to verify the SQL connection:
I can connect using SSMS with Windows authentication, and see that my SQL server is named VEEAMSQL2016, rather than the server it’s looking for (VeeamSQL2017). The upgrade wizard doesn’t allow me to choose a different SQL Server instance.
Has anyone seen and overcome this yet?
I tried the v7 Cumulative Patch today, to upgrade from v6 (this is a fresh install of VSP Console v6 from the Azure Marketplace, pre-installed with SQL Server 2016 64-bit).
The setup verified all the prerequisites, but errored out when trying to verify the SQL connection:
I can connect using SSMS with Windows authentication, and see that my SQL server is named VEEAMSQL2016, rather than the server it’s looking for (VeeamSQL2017). The upgrade wizard doesn’t allow me to choose a different SQL Server instance.
Has anyone seen and overcome this yet?
Are you not able to change the Server path that is there? It seems like it is looking in the wrong place for the instance.
I tried the v7 Cumulative Patch today, to upgrade from v6 (this is a fresh install of VSP Console v6 from the Azure Marketplace, pre-installed with SQL Server 2016 64-bit).
The setup verified all the prerequisites, but errored out when trying to verify the SQL connection:
I can connect using SSMS with Windows authentication, and see that my SQL server is named VEEAMSQL2016, rather than the server it’s looking for (VeeamSQL2017). The upgrade wizard doesn’t allow me to choose a different SQL Server instance.
Has anyone seen and overcome this yet?
Are you not able to change the Server path that is there? It seems like it is looking in the wrong place for the instance.
Exactly! I’m not able to change the Server path, as it’s greyed out.
I tried the v7 Cumulative Patch today, to upgrade from v6 (this is a fresh install of VSP Console v6 from the Azure Marketplace, pre-installed with SQL Server 2016 64-bit).
The setup verified all the prerequisites, but errored out when trying to verify the SQL connection:
I can connect using SSMS with Windows authentication, and see that my SQL server is named VEEAMSQL2016, rather than the server it’s looking for (VeeamSQL2017). The upgrade wizard doesn’t allow me to choose a different SQL Server instance.
Has anyone seen and overcome this yet?
Are you not able to change the Server path that is there? It seems like it is looking in the wrong place for the instance.
Exactly! I’m not able to change the Server path, as it’s greyed out.
Hmmm that is weird. Maybe check the forums as well for answers or open a support case. Forum - https://forums.veeam.com
Hmmm that is weird. Maybe check the forums as well for answers or open a support case. Forum - https://forums.veeam.com
Sorry, first timer here and thought I was on the forums 😁 I’ll try there and open a case
Hmmm that is weird. Maybe check the forums as well for answers or open a support case. Forum - https://forums.veeam.com
Sorry, first timer here and thought I was on the forums 😁 I’ll try there and open a case
No worries at all. We have many technical folks here but sometimes we are unable to help with things where the forums have more visibility with Product Management and support cases.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.