paparesta Posted November 9, 2010 Report Share Posted November 9, 2010 I have cath this exception in VS2010 "Attemped to read or write proteced memory.This often an indication that other memory is corrupt". With an Asp.net solutions Best regards Stefano Paparesta Link to comment Share on other sites More sharing options...
paparesta Posted November 9, 2010 Author Report Share Posted November 9, 2010 I don't understood, i have this problem only with one asp.net solutions. Stefano Link to comment Share on other sites More sharing options...
miller Posted November 9, 2010 Report Share Posted November 9, 2010 Stefano, Hi, We need to activate StackTrace to get more debug information abot this error. first, close your Plastic client, and edit your Plastic Client.conf file The file is placed in different paths depending on your OS, The client.conf file can be found in the user local directory (that is, /home/<user>/.plastic directory in Linux or C:\Documents and Settings\<user>\ Local Settings\Application Data \plastic in Windows XP or C:\Users\<user>\AppData\Local\plastic in Vista/Win7) Add this line: <StackTrace>YES</StackTrace> Like below: </DiffTools> <StackTrace>YES</StackTrace> <SetFilesAsReadOnly>yes</SetFilesAsReadOnly> <CheckFileContentForChanged>no</CheckFileContentForChanged> <CaseSensitiveFsOnMac>no</CaseSensitiveFsOnMac> <CacheServer /> 2- reproduce the error. 3- from VS open view->other windows ->requests combo ->source control Link to comment Share on other sites More sharing options...
paparesta Posted November 9, 2010 Author Report Share Posted November 9, 2010 Miller, hi i have actuvate StackTrace and i look this C:\DotSp\ProgettiWeb\AsprocarneSaS\DotSp.AsprocarneSas.Core\DotSp.AsprocarneSas.Core.vbproj : error : Unexpected error encountered. It is recommended that you restart the application as soon as possible. Error: The parameter is incorrect. File: vsee\lib\xfcstr\winstrw.cpp Line number: 166 C:\DotSp\ProgettiWeb\AsprocarneSaS\DotSp.AsprocarneSas.Data\DotSp.AsprocarneSas.Data.vbproj : error : Unexpected error encountered. It is recommended that you restart the application as soon as possible. Error: The parameter is incorrect. File: vsee\lib\xfcstr\winstrw.cpp Line number: 166 and this dialog. Link to comment Share on other sites More sharing options...
miller Posted November 10, 2010 Report Share Posted November 10, 2010 Hi Stefano, Thank you, we are looking into it. Miller Link to comment Share on other sites More sharing options...
paparesta Posted November 10, 2010 Author Report Share Posted November 10, 2010 Hi Miller, you can help the vs solution that generates the exception? Is only a little test with Asp.net, if you will give me an email address i'll send you the project Stefano Link to comment Share on other sites More sharing options...
miller Posted November 10, 2010 Report Share Posted November 10, 2010 Hi Stefano, Thank you,, Ill push for an answer from development team and get back to you. Send me your project to the Plastic SCM support mail. /Miller Link to comment Share on other sites More sharing options...
JeanDeSpaey Posted November 15, 2010 Report Share Posted November 15, 2010 I encountered the same problem ("Attemted to read or write...") when I wanted to add a Visual Studio 2010 project to PlasticSCM. The project is a Win Forms application. I am using the Visual Studio integration package. As soon as I want to add the project to PlasticSCM (from the Solution Explorer) the popup is shown. I added a number of other projects without any problem (assemblies, command line application and setup program). Only the Winforms application (so far) seems to give these problems. The Winforms application contains a number of user controls which are used by the application. There is no ASP involved. The unfortunate thing is that this is happening in an attempt to move from Perforce to PlasticSCM. I am trying to promote PlasticSCM as a source control system for our development team. I have experience both with Clearcase and with Perforce and I was very enthousiastic about PlasticSCM. Is it possible to have a fix for the integration package to solve this issue? Link to comment Share on other sites More sharing options...
miller Posted November 15, 2010 Report Share Posted November 15, 2010 Jean, Thank you for your feedback, our dev. team is working on this, and if we can see misbehavior, we will fix it fast Ill keep you posted. Miller Link to comment Share on other sites More sharing options...
Guest Posted November 16, 2010 Report Share Posted November 16, 2010 We are testing the case with the provided Visual Studio solution; we'll try to get an answer for tomorrow. Thanks for your patience. Best, Luis Link to comment Share on other sites More sharing options...
miller Posted November 17, 2010 Report Share Posted November 17, 2010 Ok guys, We reproduced the issue in our labs and already working on a fix, Ill update you soon. Miller Link to comment Share on other sites More sharing options...
paparesta Posted November 17, 2010 Author Report Share Posted November 17, 2010 Thanks Miller, i'm wait your fix ;-) Link to comment Share on other sites More sharing options...
miller Posted November 18, 2010 Report Share Posted November 18, 2010 This is fixed! and will be probably included in the next minor release. Miller Link to comment Share on other sites More sharing options...
JeanDeSpaey Posted November 18, 2010 Report Share Posted November 18, 2010 Great news that this issue is fixed. One question: when will it be released? Link to comment Share on other sites More sharing options...
miller Posted November 18, 2010 Report Share Posted November 18, 2010 Hi Jean, As soon the release passes our testings, which I would estimate some time next week Miller Link to comment Share on other sites More sharing options...
paparesta Posted November 22, 2010 Author Report Share Posted November 22, 2010 Hello, now work fine.Many Thanks =d> Stefano Link to comment Share on other sites More sharing options...
miller Posted November 23, 2010 Report Share Posted November 23, 2010 Hi Jean, Stefano, We released the 3.0.10 (3.0.187.10) that fixed the issue, please feel free to download and try. Stefano, I know you are OK now with the patch I sent. Cheers, Miller Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.