Yes, these issues are current. The errors noted in my last post was after installing 1.2.
I followed your suggestion and filled in full names for all states in our .csv file. The import failed again (same as above).
I then uninstalled Engage Locator, cleaned the database - and tried to reinstall the module. I encountered an error doing this during the register modules part. I'd seen this error before (with other modules) - wherein the uninstallation process doesn't remove the unique key in the md.modules table. So i removed it manually - and reinstalled Engage Locator 1.2 with success.
At this point, I attempted the .csv import again (with data in all required fields, and states spelled out fully). Again, the import appears to succeed - but nothing gets imported. The event viewer throws about 40 General Exceptions that read:
AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: The process cannot access the file because it is being used by another process.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.IO.IOException: The process cannot access the file because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.__Error.WinIOError() at System.IO.File.Move(String sourceFileName, String destFileName) at Engage.Dnn.Locator.DataImportScheduler.StageData(ArrayList files, FolderInfo folderInfo) at Engage.Dnn.Locator.DataImportScheduler.DoWork(Object threadContext)
Source: