Compatibility issue: Veeam Agent - DATEV SQL Server

[Retrofreak]

Hi,
I had the following problem on some workstations (Windows 7 Pro, Windows 10 Pro) and servers (Windows Server 2012R2, Windows Server 2016) in the last weeks:
After Veeam Agent is installed, the mostly used German tax software (DATEV) gets in serious trouble because of compatibility problems between SQL-Servers. After some tests and support calls/contacts to DATEV-Support it turned out, that the Veeam SQL-Server is the reason for those weird problems. Some data-loss and switch back to the latest Acro....-Backup was necessary in one case. Not funny
Here is the working fix: https://www.datev.de/dnlexom/client/app ... nt/0908732
Not really easy to understand and it would be great if this will not happen again after Veeam updates, or in future versions. So I thought I'll post it here, perhaps isn't the issue known yet by the Veeam-Team?
Thanks for your perusal and greetings!

[Vitaliy S.]

Hi Mirko,

Veeam Agent is using Microsoft SQL Server 2012 Express LocalDB Edition, so the issue should be reproduced by just installing this software and not the Veeam Agent, right?

Thanks!

[Retrofreak]

Hi, thanks for your answer!

Might be right, but I don't have the courage to test it now
And nevertheless, if the cause of the DATEV-SQL-Server problem is SQL Server 2012 Express it should be recognized by the installation process. And both SQL-Servers are working together and not disturbing one another after installing updates of the "SQLSysClrTypes.msi" file in SQL-Server 2012. So, the veeam supplied version could include the fixed files in future versions?
The fixed file comes from here:
> https://www.microsoft.com/en-US/downloa ... x?id=43339
Not easy to replace, but possible. The howto is here:
> https://www.datev.de/dnlexom/client/app ... nt/1046341

[Vitaliy S.]

Let me forward this info to our R&D team. Thanks for the heads up!

[Vitaliy S.]

Ok! Logged a request to update the files in our next updates.

[Retrofreak]

Hey, thanks a lot!

[rhiem]

Is this fixed with Version 2.2 ?? Because I have to install Datev on Win 10 Client with Veeam Agebt installed.

Best regards.

[Dima P.]

Checking with QA team, stay tuned.

[hbilke]

This one hit me, too!
Please escalate!

[Vitaliy S.]

Hi everyone, SQL Server components will be updated to the most recent build within the version in our next release. This is how it will look like: http://prntscr.com/ky4o3z

If you're using agent management funcitonality in Veeam B&R, then these components have already been updated. Thanks!

[JMM_SM]

Would be nice if someone could confirm if this issue is resolved in current version of the agent (without B&R) for windows. I would like to use it for a workstation backup without destroying my DATEV configuration.

[Dima P.]

Hello and welcome to the community Juergen,

The SQL components version is updated to 11.4.7001.0 with Veeam Agent for Windows but component generation remains the same - SQL Server 2012 Express LocalDB family.

[hbilke]

My backups of DATEV-based Agent-Backups: set up as server backups - thus managed from B&R. So is there a solution for non B&R based backups?

Harald

[Vitaliy S.]

Hi Harald,

SQL Server components are not installed on the remote computer when you're using "managed by backup server" job type, so I guess it should not be a problem in your scenario. As for standalone agent, then these components have been updated both in the standalone Agent and for the "managed by Agent" job type.

Hope this helps!

[MonsieurD]

So the issue is resolved and I can use the standalone agent in version 3.0.1.1039 to backup a Datev PC without any problems?

[Dima P.]

Hello MonsieurD,

No, unfortunately the issue is not resolved but there is a KB article from DATEV with a potential workaround.

For agents running in managed by backup server mode (in case you are using Veeam B&R server to manage your agents) that's not the case and you should not see this issue at all. If that works for your environment - try Veeam Backup & Replication Community Edition 9.5. It' can be used to protect up to 3 servers or 10 workstations for free.

[MonsieurD]

Hello Dima,

Thanks for the answer.

The PC is also standalone so no potential B&R Server in range. The backup should be triggered by connecting an USB harddrive once per week which made Veeam agent ideal.
The workaround is a little bit too dicey for me so I will look for an other solution.

[cojaxx8]

Hello,
Sorry to resurrect an old thread but I just came across this issue myself. Not with DATEV but with another program called PCLAW.

Once Veeam got installed it prevented PCLaw from writing to the SQL 2017 Database.

Uninstalled Veeam and it started working again.

I implemented the workaround above (https://www.datev.de/dnlexom/client/app ... nt/1046341) and it indeed fixed the issue.

Just wondering what the long term implications of doing this is? Can Veeam handle using an older version CLR Types?

At present I have got the following installed

Microsoft System CLR Types for SQL Server 2012 (x64) - 11.2.5058.0
Microsoft SQL Server 2012 Express LocalDB - 11.4.7001.0
Microsoft SQL Server 2012 Management Objects (x64) - 11.4.7001.0

[Vitaliy S.]

Hi Peter,

Not sure old versions will be ever supported by VAW, or you're asking if Veeam Agent will be updating its CLR to the most recent version in the next updates?

Thanks!

[Retrofreak]

Just wanted to remark, this problem still exists. Okay, real DATEV-Serverenvirements can afford higher Veeam-Fullversions. But there are DATEV-single-place installations, and there's also the same problem after each Veeam Update. Indeed, after several years, I know how to repair it . Anyway I think it would be great just to let the user update the Veeam-Agent and DATEV keeps working. Is it worth to hope?

[Dima P.]

Mirko,

Upcoming major release of Veeam Agent for Windows should solve this issue completely as all SQL components are going to be replaced with SQLite. Thank you!