The bar menu *was* showing, but now it doesn't show for either the with or without GeoPAK shortcuts. Repair install of FDOT Software did not fix it. However, uninstall and reinstall did.
What might be causes for the Bar Menu to no longer display?
1. Environment Variables not configured or configured correctly.
2. FDOT Server location has been moved.
3. Permissions not set correctly on FDOT Client or FDOT Server location.
4. .Net Framework not installed or installed and not configured correctly. (Usually effects some applications loaded from the FDOT Menu Bar. FDOT Menu Bar usually loads and is visible.)
5. FDOT registry entries not configured correctly.
6. Missing required files from client install or server install.
7. Incorrect or user modified configuration.
8. Target line in the FDOT2010 shortcut not configured to load the FDOT Workspace.
There may be a few other reasons, however, these seems to be the most common reasons for the FDOT Menu Bar to operate improperly or not load when initializing the FDOT2010 workspace.
1. Environment Variables not configured or configured correctly.
2. FDOT Server location has been moved.
3. Permissions not set correctly on FDOT Client or FDOT Server location.
4. .Net Framework not installed or installed and not configured correctly. (Usually effects some applications loaded from the FDOT Menu Bar. FDOT Menu Bar usually loads and is visible.)
5. FDOT registry entries not configured correctly.
6. Missing required files from client install or server install.
7. Incorrect or user modified configuration.
8. Target line in the FDOT2010 shortcut not configured to load the FDOT Workspace.
There may be a few other reasons, however, these seems to be the most common reasons for the FDOT Menu Bar to operate improperly or not load when initializing the FDOT2010 workspace.
This could be caused by a number of things:
1. Environment Variables not configured or configured correctly.
2. FDOT Server location has been moved.
3. Permissions not set correctly on FDOT Client or FDOT Server location.
4. .Net Framework not installed or installed and not configured correctly. (Usually effects some applications loaded from the FDOT Menu Bar. FDOT Menu Bar usually loads and is visible.)
5. FDOT registry entries not configured correctly.
6. Missing required files from client install or server install.
7. Incorrect or user modified configuration.
8. Target line in the FDOT2010 shortcut not configured to load the FDOT Workspace.
There may be a few other reasons, however, these seems to be the most common reasons for the FDOT Menu Bar to operate improperly or not load when initializing the FDOT2010 workspace.
This could be caused by a number of things:
1. Environment Variables not configured or configured correctly.
2. FDOT Server location has been moved.
3. Permissions not set correctly on FDOT Client or FDOT Server location.
4. .Net Framework not installed or installed and not configured correctly. (Usually effects some applications loaded from the FDOT Menu Bar. FDOT Menu Bar usually loads and is visible.)
5. FDOT registry entries not configured correctly.
6. Missing required files from client install or server install.
7. Incorrect or user modified configuration.
8. Target line in the FDOT2010 shortcut not configured to load the FDOT Workspace.
There may be a few other reasons, however, these seems to be the most common reasons for the FDOT Menu Bar to operate improperly or not load when initializing the FDOT2010 workspace.