[CONNECT Update 16] Installation of MicroStation removed the SDK folder

Hi Jon,

There are only a couple behaviors that I can (technically) imagine how that could happen; listing the most likely first (due to missing root folder)...

1. W/MSCE SDK installed "under" a parent/dependent product root folder, a (future) product installer could attempt to install "completely clean" and wipe everything out. Apps built using Microsoft MSI installers by default would never attempt this since any user touched files/folders would be left behind by design. Only a full install w/cleanup and product install nesting could meet what you describe.
2. If an previous version parent product had any common dependencies registered on (prior) install, it is possible during an upgrade that the new parent product could trigger a dependent installer during an upgrade action (uninstall, upgrade and/or new product/files install).  Again, since files under the SDK root (e.g. examples) perform some actions under the source code directories these files are considered user modified and are not removed by product uninstalls/cleanup - thereby keeping the top-level product root folder as an artifact for the next product install to have those files available.
3. If the SDK was installed to an external mapped drive, it is possible that the USB quick removal/performance characteristics; not being optimal for reliability; could have created an inconsistency and possibly corrupted some/all data on that drive.
4. There are a lot of other possibilities, but I don't think we should speculate until there is some evidence one way or the other.

I suggest two quick actions you can take to see if we determine if the actions above (or something else) may have occurred.

1. Open Windows Reliability History feature (Win + "Reli") and see if you can find evidence (by day or day before the event occurred). This is a quick way to see most noticed and unnoticed software patches and upgrades along with being able to click on any Details present to find more detailed logs, exception data, etc.
2. Since the above may provide a quick big picture and easy entry path to this, if not registered above I suggest to see if you have any recent install logs (zipped for all) that MicroStation creates in your localappdata temp folder: e.g. C:\Users\robert.hook\AppData\Local\Temp\MicroStation_CONNECT_Edition_20210623143008.zip. Within those files may likely be evidence of shared dependencies and installers that could have been triggered intentionally (by an installer) or unintentionally (accidental configuration or install option used). I suggest looking for key terms like: ERROR, WARN, INFO (likely a lot be certainly helpful to build a story) and ROLLBACK

Robert Hook said:

There are only a couple behaviors that I can imagine how that could happen

Thanks for your suggestions, but it's quicker to install the SDK.  I just wanted to bring to your attention the unwanted and unexpected behaviour of the MicroStation installer.  As I wrote above, previous updates of MicroStation have not removed the SDK folder.

Robert Hook said:

Do you mind emailing me the past couple install zipped log files?

Sure: where will I find those files?

e.g. C:\Users\robert.hook\AppData\Local\Temp\MicroStation_CONNECT_Edition_20210623143008.zip

My a/c name is CONNECT, but in sub-folder C:\Users\CONNECT\AppData\Local\Temp and its sub-folders there are no ZIP files.

HI Jon Summers,

I am not sure if you are open to using a file name search utility from VoidTools called Everything (Search Everything) that I use and find invaluable to find file name patterns over my two drives having ~6M documents generally within a second or less. If you like to use that (productively) or prefer some other reliable search for file names, could you search for anything across your drive(s) matching a pattern like: MicroStation_CONNECT_Edition_*.zip?

Thank you,
Bob

Robert Hook said:

could you search for anything across your drive(s) matching a pattern like: MicroStation_CONNECT_Edition_*.zip?

They ended up in G:\temp...

G:\>dir/s MicroStation_CONNECT_Edition_*.zip
 Volume in drive G is Applications
 Volume Serial Number is 18D2-6D88

 Directory of G:\temp

28/06/2021  12:03         5,622,915 MicroStation_CONNECT_Edition_20210628105848.zip
28/06/2021  12:03         2,212,989 MicroStation_CONNECT_Edition_20210628120149.zip
               2 File(s)      7,835,904 bytes

     Total Files Listed:
               2 File(s)      7,835,904 bytes
               0 Dir(s)  315,078,180,864 bytes free

G:\>

They're on their way to you via WeTransfer.

Hi Jon Summers,

I will try to review the logs in between and parallel to remaining tasks needed for the SDK release. So it may be a day or two to see if there is any helpful evidence to provide some feedback on, even though you have moved on/resolved this issue by re-installing.

Thank you,
Bob

Hi Jon Summers,

I reviewed the logs you provided (thank you) however I do not find any unexpected behaviors/actions within the somewhat verbose installer logs.  Typically looking for: Error, Warn, (sparingly Info), Removed and in this case SDK; reveals nothing out of the ordinary.  The installer found a previous version Product and Components then proceeded to verify if the new package had newer versions, then incrementally uninstall each Component then the Product installing the new Components and Product - successfully.

For safety concern if your G: drive is connected via USB you may want to confirm using a safety vs. performance removal policy setting. For all other cases and confidence in system stability consider performing a full diagnostic check disk (chkdsk /f /r) of G: to detect and repair any potential disk errors that may exist.

If the problem occurs again or persists, the only other option to consider is to look into enabling Microsoft NTFS filesystem auditing policy logging; that may impact performance somewhat; but could help user, actions and date/time data.

Sorry I can't offer much better input or direction at this time w/o having some additional evidence to help decide what happened and what to do next.

HTH,
Bob

BTW. MSCE SDK U16 UPDATE. Final changes have been committed and we are awaiting a final build containing those changes (likely .84 or .85 build) and release likely between: sometime next week (shooting for Wed or Thur) though could be as late as early (Mon-Wed) the following week.

Robert Hook said:

if your G: drive is connected via USB

The G: drive is a local SSD.

Robert Hook said:

consider performing a full diagnostic check disk (chkdsk /f /r) of G:

Why?  MicroStation is installed on my C: drive.  The %TEMP% folder is on my G: drive, which is where I found the log files you requested.

Robert Hook said:

[on 02-Jul-2021] MSCE SDK U16 UPDATE. Final changes have been committed and we are awaiting a final build containing those changes (likely .84 or .85 build) and release likely between: sometime next week (shooting for Wed or Thur) though could be as late as early (Mon-Wed) the following week

Two weeks have passed since your wrote that estimate.

It's difficult to make predictions, especially about the future. Possibly by Niels Bohr. 

HI Jon Summers,

Thank you for the friendly reminder. I want to assure you (post the most recent update) we are trying to get a complete/final and stable release out in an expedited manner. Since the release of MSCE U16 there were a couple minor commit issues in need of resolution along with some large new (internal) build changes/improvements that all were aligned around the MSCE U16 release.

Thank you and HTH,
Bob

HI Jon Summers,

Thank you for the friendly reminder. I want to assure you (post the most recent update) we are trying to get a complete/final and stable release out in an expedited manner. Since the release of MSCE U16 there were a couple minor commit issues in need of resolution along with some large new (internal) build changes/improvements that all were aligned around the MSCE U16 release.

Thank you and HTH,
Bob