2017 Deployment doesn't honor custom Revit.ini

[chicks007]

I have created a deployment for 2017 software, including Revit and wanted to set custom template locations, etc. My issue is that the custom revit.ini file defined in the deployment is not honored/read. I have tried unsuccessfully both browsing to the revit.ini file (same location as image) and typing in a UNC path to the file, then selecting import in the deployment. After an install, when Revit launches it reports missing template location with no custom revit.ini settings honored. If I take the custom revit.ini file and manually copy it to the "usercache" folder and then launch Revit all the custom settings are there, no errors reported. Why won't the deployment read/honor the custom settings in revit.ini? All of our PCs use the same drive letter mapping(s) and even using UNC path to the ini file fails. In the same deployment a UNC path is used for locating a log file that works. The same deployment sets custom mapped drive locations for AutoCAD content that work fine. Any ideas, thanks, Carl

[Anonymous]

Hello Carl

I tested this last night and did not encounter any problems with a custom Revit.ini file that included custom content paths, project path, and the help file location.  The first thing you should check is if the custom Revit.ini file was copied into your network deployment image.  Specifically, a copy of your custom Revit.ini file should be available in the Img\CustomSettings folder.  If this file isn't there, there was a problem during the creation of the deployment image.  If the file is there, open it and see if it contains the expected changes.

From my experience, most custom Revit.ini issues stem from missing or incorrectly formatted content in the custom Revit.ini file.  If you continue to experience problems, you can post a copy of your custom Revit.ini file and I can take a closer look.

Tony Michniewicz

Autodesk Revit QA

[chicks007]

Hi Tony,

I took a look for ..\Img\CustomSettings and it did not get created and the revit.ini did not get copied to it. It seems if I attempt to modify the deployment it keeps the path to the revit.ini file but selecting import doesn't do anything. Also every time I modify the deployment it doesn't keep previous Revit library content (Canadian) checked however the deployment installs it rechecking. I really suspect issues with modifying the deployment but what might it be? I'm reluctant to create a new deployment with allot of settings. If I manually create the ...\Img\CustomSettings folder and put the ini file in it will the deployment use it (before I try it)? As I mentioned earlier I don't suspect the ini file itself because I know it works fine when I place it in a PC's "Usercache" manually.

Regards,
________________________________
Carl Hicks Revit ICE, Dipl Arch Design & Drafting
BIM Manager, Arch. Technologist
Fowler Bauld & Mitchell Ltd. Architecture & Interior Design
HS1-1660 Hollis Street, Halifax NS B3J 1V7
PO Box 514, Halifax NS B3J 2R7
Canada
tel: 902.429.4100 x 118
fax: 902.423.3063
hicks@fbm.ca | send me files

disclaimer

[Tony_Michniewicz]

Hi Carl

If the Img\CustomSettings folder wasn't created, then there was definitely a problem with the Revit.ini file during the creation of the deployment image.  Unfortunately, creating this folder and copying the Revit.ini into it will not resolve this issue.  My leading suspicion remains that the network deployment creation is not handling your custom Revit.ini properly.  This may still be the case even though it works fine when copied into the UserDataCache because the network deployment creation attempts to validate custom Revit.ini files.  If you can supply a copy of this file, I should be able to narrow down the exact problem.

Also, it sounds like you have encountered two known issues related to the modification of deployments.  The first is that the original location of your custom Revit.ini file is still used during the modification of deployments, which results in an error in the event that the file no longer resides in that location.  The work-around for this one is to browse to and select another copy of your custom Revit.ini file while modifying deployments.

The other known issue is that content pack selection reverts to the default values during the modification of deployments.  Unfortunately, this means you need to remember to re-select the desired content packs each time the deployment image is modified.

Tony Michniewicz

Autodesk Revit QA

[chicks007]

Hi Tony,

You requested my Revit.ini file, I did have it attached to my last email, here it is attached again. Perhaps I need to change all the drive mappings in the ini to UNC even though they are read correctly from the manual copy as I mentioned earlier.

Also:

[Revit.ini]
[Colors]
BackgroundColor=16777215
HiliteColor=12401408
PreHiliteColor=12401408
ErrorColor=33023
[Directories]
ProjectPath=D:\Revit Projects
ImportLineweightsNameDWG=J:\Projects\Data_Revit\RAC Resources\Utilities\2017\FBMimportlineweights-dwg.txt
MaterialLibraryFiles=..\Data\Rendering
IESFileLocation=C:\ProgramData\Autodesk\RVT 2017\IES\
LookupTableLocation=C:\ProgramData\Autodesk\RVT 2017\Lookup Tables\
ExportToClassIFC=..\..\..\ProgramData\Autodesk\RVT 2017\exportlayers-ifc-IAI.txt
RootPathForPointClouds=D:\Revit Projects\PointClouds
ExternalParameters=J:\Projects\Data_Revit\Shared Parameters\FBM Shared Parameter List.txt
[DirectoriesENU]
FamilyTemplatePath=..\..\..\ProgramData\Autodesk\RVT 2017\Family Templates\English_I
DataLibraryLocations=FBM Custom Library=J:\Projects\Data_Revit\FBM Library, Imperial Library=..\..\..\ProgramData\Autodesk\RVT 2017\Libraries\US Imperial, Imperial Detail Library=..\..\..\ProgramData\Autodesk\RVT 2017\Libraries\US Imperial\Detail Items, Canadian Metric Library=..\..\..\ProgramData\Autodesk\RVT 2017\Libraries\Canada, Canadian Metric Detail Library=..\..\..\ProgramData\Autodesk\RVT 2017\Libraries\Canada\Detail Items, US Metric Library=..\..\..\ProgramData\Autodesk\RVT 2017\Libraries\US Metric, US Metric Detail Library=..\..\..\ProgramData\Autodesk\RVT 2017\Libraries\US Metric\Detail Items
DefaultTemplate=2017 FBM Imperial=J:\Projects\Data_Revit\FBM Library\FBM Custom Templates\2017 FBM Imperial.rte, 2017 FBM Metric=J:\Projects\Data_Revit\FBM Library\FBM Custom Templates\2017 FBM Metric.rte, 2017 DTIR Metric=J:\Projects\Data_Revit\FBM Library\FBM Custom Templates\2017 DTIR Metric.rte, Architectural Template=..\..\..\ProgramData\Autodesk\RVT 2017\Templates\US Imperial\default.rte, Construction Template=..\..\..\ProgramData\Autodesk\RVT 2017\Templates\US Imperial\Construction-Default.rte, Structural Template=..\..\..\ProgramData\Autodesk\RVT 2017\Templates\US Imperial\Structural Analysis-Default.rte, Mechanical Template=..\..\..\ProgramData\Autodesk\RVT 2017\Templates\US Imperial\Mechanical-Default.rte
[UserInterface]
DisplayRecentFilesPage=1
[Language]
Select=ENU
[Applications]
Mechanical=
Electrical=
Architectural=
Structural=
[InstallationSettings]
Language=ENU
Usage=All
[Install]
InstallGUID=
[ContentSearch]
Site=http://seek.autodesk.com
[Documentation]
HelpFileLocation=C:\Program Files\Autodesk\Revit Content 2017\Help\en-US\WBH\index.html
[DirectoriesCHS]
FamilyTemplatePath=C:\ProgramData\Autodesk\RVT 2017\Family Templates\Chinese\
DataLibraryLocations=Library=C:\ProgramData\Autodesk\RVT 2017\Libraries\Generic\
DefaultTemplate=构造样板=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_CHS.rte, 建筑样板=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_CHS.rte, 结构样板=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_CHS.rte, 机械样板=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_CHS.rte
[DirectoriesCHT]
FamilyTemplatePath=C:\ProgramData\Autodesk\RVT 2017\Family Templates\Traditional Chinese\
DataLibraryLocations=Library=C:\ProgramData\Autodesk\RVT 2017\Libraries\Generic\
DefaultTemplate=建構樣板=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_CHT.rte, 建築樣板=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_CHT.rte, 結構樣板=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_CHT.rte, 機械樣板=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_CHT.rte
[DirectoriesCSY]
FamilyTemplatePath=C:\ProgramData\Autodesk\RVT 2017\Family Templates\Czech\
DataLibraryLocations=Library=C:\ProgramData\Autodesk\RVT 2017\Libraries\Generic\
DefaultTemplate=Stavební šablona=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_CSY.rte, Architektonická šablona=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_CSY.rte, Konstrukční šablona=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_CSY.rte, Mechanická šablona=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_CSY.rte
[DirectoriesDEU]
FamilyTemplatePath=C:\ProgramData\Autodesk\RVT 2017\Family Templates\German\
DataLibraryLocations=Library=C:\ProgramData\Autodesk\RVT 2017\Libraries\Generic\
DefaultTemplate=Construction-Vorlage=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_DEU.rte, Architektur-Vorlage=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_DEU.rte, Ingenieurbau-Vorlage=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_DEU.rte, Gebäudetechnik-Vorlage=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_DEU.rte
[DirectoriesESP]
FamilyTemplatePath=C:\ProgramData\Autodesk\RVT 2017\Family Templates\Spanish\
DataLibraryLocations=Library=C:\ProgramData\Autodesk\RVT 2017\Libraries\Generic\
DefaultTemplate=Plantilla de construcción=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_ESP.rte, Plantilla arquitectónica=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_ESP.rte, Plantilla estructural=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_ESP.rte, Plantilla mecánica=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_ESP.rte
[DirectoriesFRA]
FamilyTemplatePath=C:\ProgramData\Autodesk\RVT 2017\Family Templates\French\
DataLibraryLocations=Library=C:\ProgramData\Autodesk\RVT 2017\Libraries\Generic\
DefaultTemplate=Gabarit de construction=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_FRA.rte, Gabarit architectural=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_FRA.rte, Gabarit de structure=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_FRA.rte, Gabarit de génie climatique=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_FRA.rte
[DirectoriesITA]
FamilyTemplatePath=C:\ProgramData\Autodesk\RVT 2017\Family Templates\Italian\
DataLibraryLocations=Library=C:\ProgramData\Autodesk\RVT 2017\Libraries\Generic\
DefaultTemplate=Modello di costruzione=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_ITA.rte, Modello architettonico=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_ITA.rte, Modello strutturale=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_ITA.rte, Modello meccanico=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_ITA.rte
[DirectoriesJPN]
FamilyTemplatePath=C:\ProgramData\Autodesk\RVT 2017\Family Templates\Japanese\
DataLibraryLocations=Library=C:\ProgramData\Autodesk\RVT 2017\Libraries\Generic\
DefaultTemplate=建設テンプレート=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_JPN.rte, 建築テンプレート=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_JPN.rte, 構造テンプレート=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_JPN.rte, 機械テンプレート=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_JPN.rte
[DirectoriesKOR]
FamilyTemplatePath=C:\ProgramData\Autodesk\RVT 2017\Family Templates\Korean\
DataLibraryLocations=Library=C:\ProgramData\Autodesk\RVT 2017\Libraries\Generic\
DefaultTemplate=시공 템플릿=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_KOR.rte, 건축 템플릿=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_KOR.rte, 구조 템플릿=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_KOR.rte, 기계 템플릿=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_KOR.rte
[DirectoriesPLK]
FamilyTemplatePath=C:\ProgramData\Autodesk\RVT 2017\Family Templates\Polish\
DataLibraryLocations=Library=C:\ProgramData\Autodesk\RVT 2017\Libraries\Generic\
DefaultTemplate=Szablon konstrukcji=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_PLK.rte, Szablon architektoniczny=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_PLK.rte, Szablon konstrukcyjny=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_PLK.rte, Szablon mechaniczny=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_PLK.rte
[DirectoriesPTB]
FamilyTemplatePath=C:\ProgramData\Autodesk\RVT 2017\Family Templates\Portuguese\
DataLibraryLocations=Library=C:\ProgramData\Autodesk\RVT 2017\Libraries\Generic\
DefaultTemplate=Modelo de construção=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_PTB.rte, Modelo de arquitetura=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_PTB.rte, Modelo estrutural=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_PTB.rte, Modelo mecânico=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_PTB.rte
[DirectoriesRUS]
FamilyTemplatePath=C:\ProgramData\Autodesk\RVT 2017\Family Templates\Russian\
DataLibraryLocations=Library=C:\ProgramData\Autodesk\RVT 2017\Libraries\Generic\
DefaultTemplate=Шаблон строительства=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_RUS.rte, Архитектурный шаблон=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_RUS.rte, Шаблон несущей конструкции=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_RUS.rte, Шаблон механического оборудования=C:\ProgramData\Autodesk\RVT 2017\Templates\Generic\Default_M_RUS.rte
[Backups]
SaveReminderMinutes=30
[Graphics]
TempDimFontSizeInPoints=12
AllowNavigationDuringRedraw=1
UseGpuOcclusionCulling=0
Antialiasing=1
AntialiasingOptions=1
SemiTransparent=1
ThinLinesEnabled=0
[Partitions]
Username=
WorksharingDisplayFrequency=5
[AppFrame]
Theme=1
[Windows]
Maximized=0
[ACMSettings]
ACMOnNetwork=1
ACMNetworkPort=14931
[Misc]
SSOServer=0
[Recent File List]
File1=
File2=
File3=
File4=
File5=
File6=
[Recent Workset List]
Config1=All
Config2=All
Config3=All
Config4=All
Config5=All
Config6=All

________________________________
Carl Hicks Revit ICE, Dipl Arch Design & Drafting
BIM Manager, Arch. Technologist
Fowler Bauld & Mitchell Ltd. Architecture & Interior Design
HS1-1660 Hollis Street, Halifax NS B3J 1V7
PO Box 514, Halifax NS B3J 2R7
Canada
tel: 902.429.4100 x 118
fax: 902.423.3063
hicks@fbm.ca | send me files

disclaimer

[Tony_Michniewicz]

Hi Carl

I had a chance to build a deployment image with your Revit.ini file and everything worked as expected (custom Revit.ini file was copied to the Img\CustomSettings folder as well as the C:\ProgramData\Autodesk\RVT 2017\UserDataCache folder).  So it would appear the root of this problem is not the content of your Revit.ini file.

The next thing I would check is the format in which your Revit.ini file is saved in.  This file can be very finicky and I've seen problems arise when customers use a program other than Notepad to edit this file.  My recommendation would be to open the file in Notepad and then use the Save As command to create a new copy of it.  In the Save As dialog, double-check the Encoding value (located just to the left of the Save button), which should be Unicode.

If this doesn't help to resolve the problem, please let me know if you are creating your Revit 2017 deployment from Revit install media or something else such as the Building Design Suite.  It would also be helpful to know if you are using any non-default settings as there is a chance it could be a combination of things leading to the problem you've encountered.

Tony Michniewicz

Autodesk Revit QA

[chicks007]

Thanks Tony for your continued help.

I was not surprised to hear the ini file worked for you as well. I always use notepad to edit Revit.ini files as I am aware others apps can produce errors.

We are using Building Design Suite 2017 Premium, a deployment was created to install AutoCAD with custom path locations (working), 3DS Max (standard install and working), and Revit initially standard install (worked). I deployed this to a PC, ran Revit to create a custom ini, adjusted it with notepad and then modified the deployment to include the custom ini that was copied to the deployment folder. There were no errors in the initial standard silent deployment except that the Revit addins needed responding to extraction prompt at the end but they did install ok once responding. Since then attempts to modify the deployment to include the custom Revit settings has failed. When I navigate to the location where the custom revit.ini file is and select import it does not appear to do anything, it does not create the ...\CustomSettings\revit.ini in the Img folder.

Regards,
________________________________
Carl Hicks Revit ICE, Dipl Arch Design & Drafting
BIM Manager, Arch. Technologist
Fowler Bauld & Mitchell Ltd. Architecture & Interior Design
HS1-1660 Hollis Street, Halifax NS B3J 1V7
PO Box 514, Halifax NS B3J 2R7
Canada
tel: 902.429.4100 x 118
fax: 902.423.3063
hicks@fbm.ca | send me files

disclaimer

[Tony_Michniewicz]

Hi Carl

After further testing, I found that custom Revit.ini files are working properly in Revit 2017 deployments but not in Building Design Suite 2017 deployments.  I'm going to continue my investigation and I'm hoping I can provide a work-around in the near future.

Tony Michniewicz

Autodesk Revit QA

[nathanalderfer3520]

We are having a similar issue with the Revit.ini file.  We are also on the Building Design Suite Premium.  When opening Revit it states that "The path you have specified for the default family template files is invalid"  It then erases the lines in the Revit.ini for the family template file locations and family libraries.

[greg_francis2]

We are running into the same situation. Any custom settings I make to a revit.ini file and then import into the deployment are not reflected in the installation. The "CustomSettings" settings directory is also not created. This is a deployment for 2017 Building Design Suite Premium.

[nathanalderfer3520]

I found that the Revit.ini file in: C:\ProgramData\Autodesk\RVT 2017\UserDataCache was blank.  Completely Blank.  

I copied over the Revit.ini file from C:\Users\MY USERNAME\AppData\Roaming\Autodesk\Revit\Autodesk Revit 2017 to the C:\ProgramData\Autodesk\RVT 2017\UserDataCache folder and it looks to be working.

After copying over the file I was able to change the file path for the template in the Options menu.  It modified the ini file in C:\Users\MY USERNAME\AppData\Roaming\Autodesk\Revit\Autodesk Revit 2017 and kept the change.

[yavork]

We are also having that issue with the Building Design Suite Premium 2017. I had a case open with the same issue (even worse ) for BDSP 2016 and seems revit deployment is not fixed 2nd year now? Now I have to revisit all Workstations and manually copy the revit.ini file in the Program Data folder.

[Tony_Michniewicz]

After running several tests, I was able to identify the underlying cause of this problem as well as a work-around that should allow you to successfully create BDS 2017 deployment images that include custom Revit.ini files.  Here are the steps necessary to address this issue:

1. In Windows Explorer, browse to the location of your BDS 2017 install media.
2. Use Notepad to open the Setup.ini file that resides alongside the main Setup.exe file.
3. Locate the section titled [ProductSelectionDlg2] and add the following four lines between the UI_Source= and BACKGROUND_IMAGE= lines:
   UI_CONSTRUCT_SOURCE=Setup\RevitContentPackUI.dll
   UI_CONSTRUCT=SelectionDlgConstruct
   UI_FINALIZE=RevitCreateCustomIni
   UI_FINALIZE_SOURCE=Setup\RevitSetup.dll
4. Save the changes made to Setup.ini and exit Notepad.
5. Launch the BDS 2017 installer from the main Setup.exe file.

If you have any questions about this work-around or continue to experience problems after implementing it, please let us know.

I would also like to mention that this problem is not unique to the BDS 2017 installation and will impact the following suites as well:

MEP Fabrication Suite 2017

Structural Fabrication Suite 2017

Plant Design Suite Premium 2017

Plant Design Suite Ultimate 2017

Building Design Suite Premium 2017

Building Design Suite Ultimate 2017

Infrastructure Design Suite Ultimate 2017

Infrastructure Design Suite Premium 2017

And lastly, I double-checked this behavior in the 2016 suites and verified that the Setup.ini files for these suites contain the correct data and should generate deployment images that include custom Revit.ini files.

Tony Michniewicz

Autodesk Revit QA

[greg_francis2]

I tried the fix that Tony suggested but it still didn't create the "CustomSettings" directory in the deployment and the custom revit.ini file was not deployed to my workstation on an install. Has anyone else been successful with the fix?

[pcacad]

I can confirm that Tony's recommendation resolved the issue for me with a little extra work.  I made the modification that Tony recommended.  Then for an unrelated reason I created a new deployment based on the "fixed" one.  There is now an Img\CustomSettings folder, but it contains only the INI for the second deployment.

So I would suggest following Tony's steps, then using the "Create & modify a deployment" link (found under Tools) to make a copy of your original deployment.  Guessing that will do the trick!

-Dan

[ktenbrook]

I too am having the EXACT same issue as the original poster.  Also Building Design Suite since I am unable to download an installation for standalone Revit 2017 that allows for creation of a deployment.  This is totally messed up and not ready for prime time.

[ktenbrook]

This "solution" did not work for me.

[Anonymous]

I am having the same issue with Revit 2017 from the Building Design Suite Premium 2017 USB. The Custom Revit.ini file is completely ignored on installation.

" After an install, when Revit launches it reports missing template location with no custom revit.ini settings honored. "

No errors in the Install Log and it indicates it is pointing to the ...\Img\Revit2017_00.ini created

Testing solution suggested...

[Anonymous]

So it is probably best to just not use a existing deployment and create a new one correct?

Will the install download be fixed at some point?

I created one with this issue and only installed it once on 1 computer, so I uninstalled from that test computer.

Thanks.

[ktenbrook]

Even after following all the previous work arounds here, Nothing worked trying to create a Revit deployment from the Building Design Suite download.  However, I finally learned that if you do not accept the default language of English for the Revit 2017 download, you will be presented with the download options, rather than just the "Install Now" option.  So, I picked the multi-language option (that includes English) and was able to download the administrative install for Revit 2017.  I was able to create a Revit 2017 deployment with a custom .INI file using that without any issues.

It's very frustrating when reports like this can go on years, and still AutoDesk never fixes them.  Of course, their testing is also completely inadequate since an issue like this would have shown itself with any kind of scenario testing whatsoever.  Alas.  Another couple of days of time I will never get back.