Re: Trouble with using AR System .NET API version 1.2.1761.15495

[Papolu, Appajee]

Title: Trouble with using AR System .NET API version 1.2.1761.15495

** Peter, Balu,   Usually I would not encourage folks polluting the system32 dir with application specific binaries. Having said that, looks like your current issue seem to be clearly a PATH related– some how the PATH adjustments are not sufficient enough to make all the necessary dependencies to be available when your app runs. Once you put the necessary stuff in System32, things seem to have worked (did they?). So this may be a short-term quick check/workaround that when dependencies are made available (by forcing them to be in System32), things work better to move you forward with whatever you’re set out to do. But IMHO “copying to system32” is not a good installation/deployment statement, so I would like this to be figured out. So in order to proceed further to see if I need to do any thing in .NET API itself, I would like each of the following questions (I had asked in my previous posting) explicitly answered. For your convenience, they’re pasted here again:   >>>>  * Can you identify the version of the .NET API you’re using (Look at the version info on BMC.ARSystem.DLL file properties)? * And please compare it against the latest drop available on Dev Community and confirm if your downloaded version is same. * After installation, are you able to run the installed FieldLabelChanger.exe (simply by double-clicking on it from File Explorer)? * If the FieldLabelChanager itself does not run, then the problem may be even more basic. * If this works fine [i.e. at least the GUI comes up, allows you to login, brings up a listing of list of forms/vuis (in combo-boxes) and fills up a grid of field names/labels] however,  then it is indicative of the installation being OK, but the problem is with the invocation of your specific client program. Then I would like to understand the following about your client program (sorry, I have deleted your previous posting that included usage snippet attachment, as I felt this thread has resolved your issue(s)) –      * is your app an ASP app?      * What is the exact error you get? * Any other details that may have caught your eye… <<<<    Thanks Appajee     From: Action Request System discussion list(ARSList) [mailto:arslist@arslist.org] On Behalf Of BALU Frédéric Sent: Wednesday, August 09, 2006 12:03 AM To: arslist@arslist.org Subject: Re: Trouble with using AR System .NET API version 1.2.1761.15495   Peter,    I has the same trouble. I was notified about the missing "BMC.arnettoc.dll", even with a PATH including the folder in which I have installed the API files.  I had to copy the files to the folder "C:\WINDOWS\system32".     De : Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] De la part de Papolu, Appajee Envoyé : mercredi 9 août 2006 03:32 À : arslist@ARSLIST.ORG Objet : Re: Trouble with using AR System .NET API version 1.2.1761.15495 ** From: Papolu, Appajee Sent: Tuesday, August 08, 2006 6:31 PM To: 'arslist@arslist.org' Subject: RE: Trouble with using AR System .NET API version 1.2.1761.15495   Peter,   Can you identify the version of the .NET API you’re using (Look at the version info on BMC.ARSystem.DLL file properties)? And please compare it against the latest drop available on Dev Community and confirm if your downloaded version is same. After installation, are you able to run the installed FieldLabelChanger.exe (simply by double-clicking on it from File Explorer)? If the FieldLabelChanager itself does not run, then the problem may be even more basic. If this works fine [i.e. at least the GUI comes up, allows you to login, brings up a listing of list of forms/vuis (in combo-boxes) and fills up a grid of field names/labels] however,  then it is indicative of the installation being OK, but the problem is with the invocation of your specific client program. Then I would like to understand the following about your client program (sorry, I have deleted your previous posting that included usage snippet attachment, as I felt this thread has resolved your issue(s)) – is your app an ASP app? What is the exact error you get? Any other details that may have caught your eye…   Thanks Appajee   __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___