fort-pymdwizard
fort-pymdwizard copied to clipboard
DOI-USGS
Program Never Opens
Steps to reproduce the behavior: The programs seems to install successfully. When I click on metadata wizard in the start menu, the cursor briefly indicates it is trying to open, but nothing else happens- no GUI pops up and nothing shows in the system tray.
- OS: Windows 10 service pack 20H2
This has happened on previous versions as well, although the duck would at least pop up on the screen briefly in those versions. I have uninstalled them and removed all associated files from the install location before trying the latest version. I have tried restarting, windows 8 compatibility mode, and installing with/without admin elevation.
Hello @specorar - debugging may require you working with someone and possibly doing a screenshare. Perhaps you can arrange a time to do so with @tnorkin ? We've seen similar behavior with previously connected external monitor set up where the tool attempts to open in that location but then fails to display, however an uninstall/re-install should have resolved that. Suggest a follow up with @tnorkin so we can better document the behavior.
Hi @specorar, I'm available today at 4 - 5pm MT and any time tomorrow. Are you a USGS employee so that we can connect through Microsoft Teams for a screenshare? If not, no problem, we can figure out another way.
@specorar, if we don't get a chance to check in, you can try installing the latest version of the wizard (accessible from here), and you can also try disconnecting from any connected external monitors before opening the application. You can reach me at [email protected] if you have questions.
After testing with @specorar, I confirmed that the wizard doesn't open (it's not a 2nd monitor issue), and there is no wizard icon showing up in the taskbar. When the .bat terminal is open, there is an immediate error message "Can't load requested DLL: C:\Program Files\GDAL\bin\gdal\plugins\gdal_BAG.dll", even though the gdal file does exist in this location on the machine. We looked at the environment settings for gdal paths and will follow up with ideas for testing and/or possible fixes.
I am also having a similar issue here. I've tried restarting my pc, making sure no ports are being used, checked display settings, and deleted then reinstalled newest version. The duck logo appears, and it looks as if the program is open in the taskbar, but when I hover over the icon in the taskbar the window appears white/blank, and when I click on the icon no window appears.
This is one solution:
Fix: right-click + shift the program icon in the taskbar > select Move.
Your mouse cursor will now jump to wherever the program is (somewhere off screen). While holding down the left mouse button, move the mouse around until the program comes into the display.
Still no luck...when I try to move the window around, I can see the cursor is in the proper "move" mode, but the window never becomes visible no matter where I move the cursor to.
From: bgjohnson1985 @.> Sent: Tuesday, March 7, 2023 12:19 PM To: DOI-USGS/fort-pymdwizard @.> Cc: Kinser, Dylan W @.>; Comment @.> Subject: [EXTERNAL] Re: [DOI-USGS/fort-pymdwizard] Program Never Opens (Issue #153)
This email has been received from outside of DOI - Use caution before clicking on links, opening attachments, or responding.
This is one solution:
Fix: right-click + shift the program icon in the taskbar > select Move.
Your mouse cursor will now jump to wherever the program is (somewhere off screen). While holding down the left mouse button, move the mouse around until the program comes into the display.
— Reply to this email directly, view it on GitHubhttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDOI-USGS%2Ffort-pymdwizard%2Fissues%2F153%23issuecomment-1458809999&data=05%7C01%7Cdkinser%40usgs.gov%7Cd03855ae0631438e575208db1f494bea%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C638138171902349629%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vWbJ3Ss2FsPjsw7TPhBaPSRgjhIVcn1z%2Be%2Fi5zjMFVg%3D&reserved=0, or unsubscribehttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA4CO3ZOR3GZFNK5JAFGZE53W26J57ANCNFSM5ZM54C5A&data=05%7C01%7Cdkinser%40usgs.gov%7Cd03855ae0631438e575208db1f494bea%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C638138171902349629%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1CWDdiCQc%2FSq1gxbIaRMNR4jQanmPe9oAul3dc%2F8pFc%3D&reserved=0. You are receiving this because you commented.Message ID: @.***>
Instead of 'move' try 'maximize'
IT WORKED! Thank you!
From: Ben Johnson @.> Sent: Tuesday, March 7, 2023 3:42 PM To: DOI-USGS/fort-pymdwizard @.> Cc: Kinser, Dylan W @.>; Comment @.> Subject: [EXTERNAL] Re: [DOI-USGS/fort-pymdwizard] Program Never Opens (Issue #153)
This email has been received from outside of DOI - Use caution before clicking on links, opening attachments, or responding.
— Reply to this email directly, view it on GitHubhttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDOI-USGS%2Ffort-pymdwizard%2Fissues%2F153%23issuecomment-1459040058&data=05%7C01%7Cdkinser%40usgs.gov%7Ccd64a7f762034105e86b08db1f659f37%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C638138293547244579%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gVqstcjmO6Geq0U93M0Vt%2BheJWiBcXjj41R01405Tog%3D&reserved=0, or unsubscribehttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA4CO3ZKCRDUD2EPFJKFQMUTW27BWJANCNFSM5ZM54C5A&data=05%7C01%7Cdkinser%40usgs.gov%7Ccd64a7f762034105e86b08db1f659f37%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C638138293547244579%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FKgh0sNKS3H%2BQd4dTrfro%2FyxXOGzUv9Lg1f5MQEGg2Y%3D&reserved=0. You are receiving this because you commented.Message ID: @.***>
Thanks for the feedback and troubleshooting. This is a known issue with some applications where there is some persistence or caching of having been last opened/close in an external display. Bringing the application back to the primary display before closing it (or before disconnecting from an external monitor) may help avoid the problem.