> > If you set all these and still get the access violation, then > > there is probably something wrong with the DLLs/exes > > generated. The next step would be to get the binary version > > and see if the samples could be run. > > The only thing I've generated is a Project2.lib file that should be a > C++ Builder 6 equivalent of AxisClient.lib. Everything else I've taken > from either the Axis BIN or SRC distributions.
This seems to be quite a tough one to solve :-( I am not able to figure out any other way to fix this (In fact I am not a Windows geek) Samisa... On 7/27/05, Myles Bunbury <[EMAIL PROTECTED]> wrote: > > Ok lets have a checklist: > > > > 1. AXISCPP_DEPLOY environment variable is set > > Under system variables in the control panel: > D:\New Folder > > >2. axiscpp.conf > > is in folder pointed by %AXISCPP_DEPLOY% > > Yes, D:\New Folder\axiscpp.conf exists. > > 3. axiscpp.conf > > settings contain full paths > > Contents of axiscpp.conf: > > --- > > # The comment character is '#' > #Available directives are as follows > #(Some of these directives may not be implemented yet) > # > #WSDDFilePath:The path to the server wsdd > #LogPath:The path to the axis log > #ClientLogPath:The path to the axis client log > #ClientWSDDFilePath:The path to the client wsdd > #Transport_http:The HTTP transport library > #Transport_smtp:The SMTP transport library > #XMLParser:The xml parser library > #NodeName:Node name > #ListenPort:Listening port > #Channel_HTTP:The HTTP transport channel library > #Channel_HTTP_SSL:The HTTP transport secure channel library > > #LogPath:Axis\logs\AxisLog.txt > #WSDDFilePath:Axis\conf\server.wsdd > LogPath:D:\New Folder\AxisLog.txt > #WSDDFilePath:C:\Program Files\Apache Group\Apache\Axis\conf\server.wsdd > XMLParser:D:\New Folder\AxisXMLParser.dll > Transport_http:D:\New Folder\HTTPTransport.dll > Channel_HTTP:D:\New Folder\HTTPChannel.dll > #Channel_HTTP_SSL:HTTPSSLChannel.dll > > --- > > >4. The folder containing Xerces > > 2.2.0 DLL is in your PATH variable 5. The folder containing > > Axis CPP DLLs are in your PATH variable > > All the DLLs I keep in the same folder as the .EXE, so it should look > there first. Still, I added D:\New Folder to my PATH system variable. No > change. > > > If you set all these and still get the access violation, then > > there is probably something wrong with the DLLs/exes > > generated. The next step would be to get the binary version > > and see if the samples could be run. > > The only thing I've generated is a Project2.lib file that should be a > C++ Builder 6 equivalent of AxisClient.lib. Everything else I've taken > from either the Axis BIN or SRC distributions. > > > > > > > -----Original Message----- > > > From: Myles Bunbury [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, July 26, 2005 6:16 PM > > > To: Apache AXIS C User List; Samisa Abeysinghe > > > Subject: RE: Problems running under C++ Builder 6 > > > > > > > Please try having full path in the axiscpp.conf file for parser, > > > > transport and channel DLLs. > > > > > > > > Also, as you are not using SSL please drop Channel_HTTP_SSL from > > > > axiscpp.conf and try. > > > > > > > > > I made both those changes. No effect. > > > > > > > > > --- > > > > > > > On 7/25/05, Myles Bunbury <[EMAIL PROTECTED]> wrote: > > > > > > would you mind copying the contents of your axiscpp conf > > > > file here > > > > > > pls. > > > > > > > > > > I've copied the contents below. Nothing fancy... > > > > > > > > > > --- > > > > > > > > > > # The comment character is '#' > > > > > #Available directives are as follows #(Some of these directives > > > > > may not be implemented yet) # #WSDDFilePath:The path to > > the server > > > > > wsdd #LogPath:The path to the axis log > > #ClientLogPath:The path to > > > > > the axis client log #ClientWSDDFilePath:The path to the client > > > > > wsdd > > #Transport_http:The > > > > > HTTP transport library #Transport_smtp:The SMTP > > transport library > > > > > #XMLParser:The xml parser library #NodeName:Node name > > > > > #ListenPort:Listening port #Channel_HTTP:The HTTP transport > > channel > > > > > library #Channel_HTTP_SSL:The HTTP transport secure channel > > library > > > > > > > > > > #LogPath:Axis\logs\AxisLog.txt > > > > > #WSDDFilePath:Axis\conf\server.wsdd > > > > > LogPath:D:\New Folder\AxisLog.txt > > > > > #WSDDFilePath:C:\Program Files\Apache > > > > > Group\Apache\Axis\conf\server.wsdd > > > > > XMLParser:AxisXMLParser.dll > > > > > Transport_http:HTTPTransport.dll > > > > > Channel_HTTP:HTTPChannel.dll > > > > > Channel_HTTP_SSL:HTTPSSLChannel.dll > > > > > > > > > > --- > > > > > > > > > > >Also could you tell us what parser you are using - > > > > xerces, expat or > > > > > >XML4C. > > > > > > > > > > I'm using the (default?) Xerces 2.2.0 parser. Though once I > > > > get this > > > > > thing going I'd prefer to use the 2.6.0 version. > > > > > > > > > > >Could you also make sure that parsers libs are in your > > > > libpath (or > > > > > >whatever it is on your flavour of OS) e.g. xerces-2_2_2.0 > > > > lib (not > > > > > >the Axis xml parser libs). > > > > > > > > > > I was not doing anything with the Xerces .LIB files before. I > > moved > > > > > them into the same directory as the test application. I > > > > tried adding > > > > > them to the application. I tried adding them to my project that > > > > > generates the Axis .LIB file. No change on the error I'm seeing. > > > > > > > > > > That said, since I'm not having compile errors, why > > would the .LIB > > > > > files be a factor? Shouldn't the compile fail if I'm > > dependent on > > a > > > > > missing .LIB? > > > > > > > > > > > > > > > Anyway, perhaps also worth mentioning is that when this access > > > > > violation / abnormal program termination error occurs, it > > > > manages to > > > > > close Outlook 2003. Fun. > > > > > > > > > > > > > > > I also don't have a HTTPSSLChannel.dll file kicking around > > > > as I didn't > > > > > find it in either the bin or src axis distributions I > > > > downloaded. That > > > > > said, I'm NOT doing anything with SSL at the moment. > > > > > > > > > > > > > > > > I'm sorry to see that this is hard - when we get to the > > > > end of this > > > > > > it would be good to create a lessons learnt and work out > > > > what went > > > > > > wrong so we can fix the poor error messages ! > > > > > > this is an area that I've been trying to improve since > > > > the first day > > > > > > I started working on this code and it has improved > > > > greatly so please > > > > > > stay with us and we'll improve it ! > > > > > > > > > > Where there's a will there's a way. :) > > > > > > > > > > --- > > > > > > > > > > "Some would ask, how could a perfect God create a > > universe that is > > > > > filled with so much that is evil. They have missed a greater > > > > > conundrum: why would a perfect God create a universe at all?" > > > > > -Sister Miriam Godwinson - "But For The Grace Of God" > > > > > "The best things in life aren't things." > > > > > -Art Buchwald > > > > > "Never leave a friend behind. Friends are all we have to get us > > > > > through life > > > > > - and they are the only things from this world that we > > > > could hope to > > > > > see in the next." > > > > > -Dean Koontz - "Fear Nothing" > > > > > > > > > > Myles Bunbury, BASc. > > > > > Lead Software Developer & Product Supervisor, IP Search > > CDNameSearch > > > > > Phone: 1 (888) 414-4193 or (613) 739-2956 > > > > > Fax: (613) 739-1739 > > > > > Web: www.cdnamesearch.com > > > > > > > > > > > > > > > > > > > > > > > > > > "Myles Bunbury" <[EMAIL PROTECTED]> > > > > > > > > > > > > 18/07/2005 19:16 > > > > > > Please respond to > > > > > > "Apache AXIS C User List" > > > > > > > > > > > > To > > > > > > "Apache AXIS C User List" <[email protected]> > > cc Subject > > > > > > RE: Problems running under C++ Builder 6 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > This is incorrect. For client you have to have > > > > > > AXISCPP_DEPLOY env var > > > > > > > set. > > > > > > > Also you have to have axiscpp.conf file located in > > > > > > > %AXISCPP_DEPLOY% folder. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Both the serve side as well as the client side uses the > > > > > > axiscpp.conf > > > > > > > file. > > > > > > > > > > > > > > Client uses this file to locate the transport and parser > > files. > > > > > > > If you are only using the client, WSDDFilePath entry is not > > > > > > requires. > > > > > > > But the rest are required. Please see > > > > > > > http://ws.apache.org/axis/cpp/winuser-guide.html#transport > > > > > > > for more details. > > > > > > > > > > > > > > > > > > I've added AXISCPP_DEPLOY to my system environment > > > > variables in the > > > > > > control panel, and created an axiscpp.conf file in that > > directory. > > > > > > > > > > > > The abnormal program termination has gone away but been > > > > replaced by > > > > > > an access violation: > > > > > > > > > > > > Project Project1.exe raised exception class EAccessViolation > > with > > > > > > message 'Access violation at address 00000001. Read > > of address > > > > > > 00000001'. Process stopped. Use Step or Run to continue. > > > > > > > > > > > > I recompiled my .LIB file in a release mode to no effect as > > well. > > > > > > > > > > > > Still highly puzzled as to what's making this difficult. :( > > > > > > > > > > > > > > > > > > --- > > > > > > > > > > > > "Some would ask, how could a perfect God create a > > > > universe that is > > > > > > filled with so much that is evil. They have missed a greater > > > > > > conundrum: why would a perfect God create a universe at all?" > > > > > > -Sister Miriam Godwinson - "But For The Grace Of God" > > > > > > "The best things in life aren't things." > > > > > > -Art Buchwald > > > > > > "Never leave a friend behind. Friends are all we have > > to get us > > > > > > through life > > > > > > - and they are the only things from this world that we > > > > could hope to > > > > > > see in the next." > > > > > > -Dean Koontz - "Fear Nothing" > > > > > > > > > > > > Myles Bunbury, BASc. > > > > > > Lead Software Developer & Product Supervisor, IP Search > > > > CDNameSearch > > > > > > Phone: 1 (888) 414-4193 or (613) 739-2956 > > > > > > Fax: (613) 739-1739 > > > > > > Web: www.cdnamesearch.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
