SQL server, VDI Point-In-Time restore fails (4044193)

Date: NOV 2009
Product & Version: SQL Server 5.5.13
OS Version: Windows 2003

Symptoms:
Binary log show the following failure:

In German:

Error 2009/10/14 09:23:50 2542 Data Plugin SQLRESTORE01 ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Für den STOPAT-Parameter wurde ein ungültiger Wert angegeben.
Error 2009/10/14 09:23:50 2542 Data Plugin SQLRESTORE01 ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG wird fehlerbedingt beendet.
Error 2009/10/14 09:24:05 2542 Data Plugin SQLRESTORE01 SQL command failed before VD transfer
Error 2009/10/14 09:24:05 2542 Data Plugin SQLRESTORE01 The SQL VDI command failed.

In English:

Error 2009/10/14 09:23:50 2542 Data Plugin SQLRESTORE01 ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]An invalid value was given for the STOPAT parameter.
Error 2009/10/14 09:23:50 2542 Data Plugin SQLRESTORE01 ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG completed with errors
Error 2009/10/14 09:24:05 2542 Data Plugin SQLRESTORE01 SQL command failed before VD transfer
Error 2009/10/14 09:24:05 2542 Data Plugin SQLRESTORE01 The SQL VDI command failed.


Cause:
date time string format supplied by SQL is not in "YYYY-MM-DD HH:MM:SS@ format

APM Version SQL Server 5.5.13 can workaround this problem by changing the APM login user's language to English If the customer specified a login user in the APM's configure dialog, they will have to change that user's language.

Here are the steps to change a login user's language setting:

1. In the navigation pane of SQL Server Management Studio, expand a server group, and then expand a server.
2. Expand Security, and then click Logins.
3. In the details pane, right-click the login to modify, and then click Properties.
4. In the Language list, on the General tab, click the new default language.


Explanation:
To summarize the SQL Server plugin expects date time strings in SQL queries to be localized, in the date time string format "YYYY-MM-DD HH:MM:SS" but on a German installation the date/time is not .
Engineering are looking to fix this problem by having the APM use the IS0 8601 date/time string format which should be recognized by all localized versions of SQL Server