4.0.5 Beta bug report: Missing icons for an online solution
Moderator: SourceGear
4.0.5 Beta bug report: Missing icons for an online solution
We have a weird situation on 4.0.5 beta (it's really Fortress 1.0.5 beta). There are no icons on the files, check-ins/getlatest work, and the right click menu of the solution is missing the Online/Offline options. Attached is a screenshot of how this looks...
We are using the 2005 client with CVS-style file handling.
We have double and triple-checked that the Fortress 2005 client is the selected client, and that the client has the correct configuration (for example, if there were no connection to the Fortress server, the Fortress Client options button on the VS2005 config section would be disabled, but it is enabled.
We have tried erasing the local copy of the solution and opening from Fortress again (it all worked, except there are still no icons), restarting VS, rebooting the machine, etc... The one thing we have not done is to reinstall the Fortress client.
This all started happening out of the blue, it had all been working the day before.
EDIT: This is only happening on one machine, the others are all working normally.
We are using the 2005 client with CVS-style file handling.
We have double and triple-checked that the Fortress 2005 client is the selected client, and that the client has the correct configuration (for example, if there were no connection to the Fortress server, the Fortress Client options button on the VS2005 config section would be disabled, but it is enabled.
We have tried erasing the local copy of the solution and opening from Fortress again (it all worked, except there are still no icons), restarting VS, rebooting the machine, etc... The one thing we have not done is to reinstall the Fortress client.
This all started happening out of the blue, it had all been working the day before.
EDIT: This is only happening on one machine, the others are all working normally.
- Attachments
-
- FortressMissingIcons.gif (54.89 KiB) Viewed 5177 times
gabriel magana-gonzalez
Sure, here is a screen capture of the dialog... The bindings look messed up (root folder for all?). If it helps any, everything is displayed OK in the Fortress client.
EDIT: Forget my comment above of the bindings looking messed up, it is the same way on a machine that works fine...
EDIT: Forget my comment above of the bindings looking messed up, it is the same way on a machine that works fine...
- Attachments
-
- FortressMissingIcons2.gif (129.62 KiB) Viewed 5165 times
gabriel magana-gonzalez
The $ that you're seeing is the working folder mapping that applies for the project. All the projects in the screen shot are using the mapping that is set that the root of the repository is mapped to the c:\devel directory.
Can you turn on client side logging for this user and send us the log file? I'm hoping that there's an exception that is causing the problem in the icon choosing code, but nowhere else.
Can you turn on client side logging for this user and send us the log file? I'm hoping that there's an exception that is causing the problem in the icon choosing code, but nowhere else.
Ok, we turned on VS2005 client logging per http://support.sourcegear.com/viewtopic.php?p=5375 . I attach the generated log, it covers opening and closing the solution without doing anything else.
- Attachments
-
- VaultVsipClient.ZIP
- (79.28 KiB) Downloaded 236 times
gabriel magana-gonzalez
This is an odd one. There's no failures in the log that would cause this. Is there anything unusual about this particular machine that might be relevant?
It's possible that there was a glitch in setup. Try running devenv.exe /setup (where devenv.exe is the Visual Studio 2005 executable) on this machine. If that has no effect, I'd try these steps:
Uninstall Fortress.
Do a Visual Studio Repair (via add/remove programs)
Re-install Fortress.
It's possible that there was a glitch in setup. Try running devenv.exe /setup (where devenv.exe is the Visual Studio 2005 executable) on this machine. If that has no effect, I'd try these steps:
Uninstall Fortress.
Do a Visual Studio Repair (via add/remove programs)
Re-install Fortress.
Ian Olsen
SourceGear
SourceGear
I'm about to have the developer do as you suggest, except there's a little wrinkle: On another solution it works fine... This is really mind-boggling because the same solution displays icons on all the other machines, and the other solution displays the icons on all machines.
gabriel magana-gonzalez