Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Visual SourceSafe Automation Object Crashes When You Call IVSSItem::get_Versions
Article ID: 323917 - View products that this article applies to.
This article was previously published under Q323917
When you use the Visual SourceSafe Automation object model, you may receive an access violation when you call the IVSSItem::get_Versions function.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Visual Studio .NET service pack that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 03-Jun-2002 09:21 06.00.9604 199,952 Analyze.exe 03-Jun-2002 09:21 295,696 Ddconv.exe 03-Jun-2002 09:21 420,624 Ddupd.exe 03-Jun-2002 09:21 224,969 Delta_ss.exe 03-Jun-2002 09:21 111,888 Mkss.exe 03-Jun-2002 09:22 231,143 Pvcs_ss.exe 03-Jun-2002 09:22 38,790 Readmess.htm 03-Jun-2002 09:22 397,584 Ss.exe 03-Jun-2002 09:22 06.00.9604 12,048 Ssadmin.exe 03-Jun-2002 09:22 06.00.9604 562,448 Ssapi.dll 03-Jun-2002 09:22 06.00.9604 499,472 Ssarc.exe 03-Jun-2002 09:22 06.00.9604 16,656 Ssexp.exe 03-Jun-2002 09:22 06.00.9604 1,132,304 Ssgui.dll 03-Jun-2002 09:22 06.00.9604 140,800 Ssint.exe 03-Jun-2002 09:22 152,336 Sslogin.exe 03-Jun-2002 09:22 06.00.9604 497,424 Ssrestor.exe 03-Jun-2002 09:22 06.00.9604 1,412,368 Ssscc.dll 03-Jun-2002 09:22 06.00.9604 480,528 Ssus.dll 03-Jun-2002 09:22 101,136 Testlock.exe 03-Jun-2002 09:22 144,144 Unlock.exe 03-Jun-2002 09:22 121,104 Updini.exe
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This bug was corrected in Visual Studio .NET 2003.