Keith did the same thing (deleted the tables and packages and let the DDT recreate them) and he is working now, too.

1. Uninstall SF
2. Delete any SF related registry settings
3. Delete SF related folders:
• C:\Program Files\Common Files\Microfour
• C:\Program Files\Microfour
4. Delete Internet Cache
5. Download and Install SF

I had the messaging and security tables in DDT, so I also:

1. Deleted all messaging and security data packages and tables
2. Re-insert messaging and security data packages and tables
3. Deployed to server

Once I finished this:

1. Opened my project in VS
2. Right-click on the Solution and chose "Clean Solution"
3. Rebuilt the solution

Everything is now peachy...

1) We removed the StrataFrameInternal database so that we would not have to worry about data deployment problems for people running the DDT, Messaging, BOMapper, etc.  Instead, we embedded the localization data in XML files within the assemblies.

2) We added some extra functionality to the StrataFrameApplication.RunApplication() method to ensure that all embedded messaging files within each assembly get registered every time.  Before, you had to manually call the Localization.RegisterEmbeddedXmlFile(), but now, the runtime does it for you by watching the AppDomain.AssemblyLoaded event and registering the message files when the assemblies are lazy loaded or manually loaded into the app domain. 

So, the current update should fix this problem for you, and all of the localization data should be present.

LocalizationKeyNotFoundException
 The specified key [SFSM_PasswordAuthenticationFailed] was not found within the messaging database.
KeyNotFoundException
 The message key [SFSM_PasswordAuthenticationFailed] could not be found in the localization data.

Source     : MicroFour StrataFrame Base

Stack Trace:
(snip)