 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Visual Studio.NET / Source Safe / January 2008VSS Locks up after credentials
Hey there, I'm trying to open some previously archived VSS databases, unfortunately after asking for username and password, VSS just locks up on the Splash screen with 95% cpu usage and stays that way until I terminate it. I can't get into the database no matter what I have tried, I have analyzed the database and it appears to be fine, any ideas what could be causing this problem? Nick. Hello Nick, It seems you cannot open a previously archived VSS database. When you are trying to open it, VSS locks up on the Splash screen with 95% CPU usage. If I misunderstood anything here, please don't hesitate to correct me. Could you please let me know what VSS version you are talking about? Have you tried upgrading either to latest VSS 6.0d or VSS2005 Update build? Also, please try logging in using a different VSS username, or modify in the user's ss.ini the Project variable to point to a different folder (something in the current project's may be corrupted and not detected by analyze). If that doesn't help, is it possible for you to pack the VSS database and sent it to me. (v-wywang@microsoft.com). I will try it on my side and perform further research. thanks. Have a great day, Best regards, Wen Yuan Microsoft Online Community Support ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. Hello Nick, Have you resolved this issue so far? I haven't heard from your a couple of days. I just want to check if there is anything we can help with. Please feel free to update here again, if you have any more concern. We are glad to assist you. Have a great day, Best regards, Wen Yuan Microsoft Online Community Support ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. Hey Wen, Sorry for the delay in my reply, I have been rushed off my feet at current. Fortunately the issue has been resolved and you were correct that it was a version mismatch, unfortunately I was relayed the wrong information as to which version of VSS the database was created with. Although with this said, I am mightily confused as to how VSS can fail under those circumstances considering the database contains necessary version information to inform the user that they are using the wrong version, rather than locking up the pc for an eternity. But maybe I missed the reason. Anyways, thanks a million for your reply, and sorry again for being so slow at replying! :) Nick. > Hello Nick, > [quoted text clipped - 12 lines] > This posting is provided "AS IS" with no warranties, and confers no > rights. Hello Nick, Thanks for your reply and sharing the information with us. :) Others may learn and benefit from your information. Have a great day, Best regards, Wen Yuan Microsoft Online Community Support ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.