Starting the Data Protection for SQL GUI or command line in certain situations causes the interface to crash
Problem Event Name: BEX64
Application Name: mmc.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bc808
Fault Module Name: MSVCR100.dll
Fault Module Version: 10.0.40219.1
Fault Module Timestamp: 4d5f034a
Exception Offset: 0000000000070468
Exception Code: c0000417
Exception Data: 0000000000000000
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033
Additional Information 1: d34f
Additional Information 2: d34f6fd5e7f2abd882568ceb3065e9fd
Additional Information 3: 662c
Additional Information 4: 662cee0d3e37bd2a9d1f238c608f4dcd
If a user copies a tdpsql.cfg file from another machine and that file does not have the full timestamp, a crash can occur. Example:
Will cause a crash:
Will allow the GUI or CLI to start:
LASTPRUNEDate 09/18/2013 16:32:16
Diagnosing the problem
Check tdpsql.cfg to see if there is a full timestamp in the entry.
Resolving the problem
Ensure that both the date and time is in correct format for the LASTPRUNEDATE entry in tdpsql.cfg if the file is copied from another system.
Alternatively, remove the LASTPRUNEDATE entry from the tdpsql.cfg file. If this entry does not exist, it will be added the next time the client is launched.
Also, if you use the setup wizard on a new install, the full timestamp will be added automatically.