Access violation messages

What are these access violation messages I keep getting after downloading casual games? The download goes through Ok, but when I try to open them, McAfee puts up these messages and terminates the procedure. This never happened when I was with Orange. Other downloads such as BBC iPlayer work fine, just what is wrong and how do I puit it right. I operate Windows 7 and have plenty of memory and up to date drivers.

They're the same things they were in the last thread you started on the subject.

Similar Messages

Syntax error or access violation...

I have recently purchased a .com and webhosting through the company hostgator.com , I am currently trying to integrate a java application thru this .com and the databases they provide me to use
Anyway, here is the code I have
====
import java.sql.*;
public class mysql_connector
      * @param args
     public static void main(String[] args)
          Connection conn = null;
        try
            String userName = "******";
            String password = "*******";
            String url = "jdbc:mysql://bkardi.com:3306/******";
            Class.forName ("com.mysql.jdbc.Driver").newInstance ();
            conn = DriverManager.getConnection (url, userName, password);
            System.out.println ("Database connection established");
        catch (Exception e)
            System.err.println ("Cannot connect to database server");
            System.out.println(e);
        finally
            if (conn != null)
                try
                    conn.close ();
                    System.out.println ("Database connection terminated");
                catch (Exception e) { /* ignore close errors */ }
}and here is the error I get
Cannot connect to database serverjava.sql.SQLException: Syntax error or access violation message from server: "Access denied for user 'buk110_kardi'@'24.115.97.153' to database 'buk110_java'"
Any ideas, suggestions?

You need to verify your parameters. The error message is telling you:
"Access denied for user 'buk110_kardi'@'24.115.97.153' to database 'buk110_java"
So you have some sort of a login issue, either username/password and/or access to the database specified. If all of these are correct then you need to talk to the web host and make sure that they have set up your DB correctly.

InitCVIRTE generates error message "Unhandled exception in "MyApp.exe": 0xC0000005: Access violation reading location 0x00000000."

Hi,
I have converted a LabWindows CVI project to Visual Studio 2005. When I start the application i debug mode I get the message "Unhandled exception at 0x685662ba in EE352-500V.exe: 0xC0000005: Access violation reading location 0x00000000."
It comes when the application calls: InitCVIRTE in this context:
int __stdcall WinMain (HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpszCmdLine, int nCmdShow)
// Initialize LabWindows/CVI run-time library
if (InitCVIRTE (hInstance, 0, 0) == 0)
return -1; /* out of memory */
The debugger indicates that value of hInstance is 0x00400000 {unused=9460301}
Can someone give me a solution to this problem. I have done some search on the Web without success.
Thanks!

I think that exception might be coming from the data execution prevention service that is part of Win XP SP2. The OS thinks that you're somehow trying to execute in the data segment and kills the process. It's intended to catch worms and viruses.
You can turn this service off for non-Microsoft programs using the control panel.
Many pointer handling errors now report as this exception instead of as a memory violation exception. That looks like a null pointer derefence to me.
Menchar
Message Edited by menchar on 11-09-2007 07:12 PM

Access violation error message 'WMP54GSv1_1.exe'

Hi,
Each time I start my Compaq Presario, I get the following Error message: "Access violation at address 004A55F7 in module ‘WMP54GSv1_1.exe’. Read of address 00000000." I cannot view wireless networks or access internet.
I have a Linksys wireless card in my PC and it just came back from HP for faulty on/off switch servicing.
How do I rememdy this situation?
Thanks!!
TJ

The drivers you need to download are your correct product model number and version which you may find underneath the card itself on one of the stickers... or with the card box (if you still have it)
After you have downloaded them, just 1st transfer them into the non-working PC... the file might be zipped... so you might need to unzip them first... you then uninstall the card from the PC... either go to add/remove programs and add/remove hardware....
Then restart the PC... after you restart it, you will probably be prompted for a "found new hardware wizard"... just go through the process... if it asks your for the drivers.. select "specify a location and specify the folder where you actually unzipped the files...
Sounds lengthy I know...

"Access Violation" error messages in Diadem 9.1

We have recently purchased Diadem V.9.1 and are encountering numerous "Access violation" errors as well as Runtime errors.The most frustrating aspect of trying to run this software are the constant crashes we are experiencing.
It is taking us 3X as long to process one subject as it should. I posted a request to NI technical help but I think it is the Thanksgiving holiday in the US.

Actually, DIAdem 9.1 is a very stable version. If you are continuously
experiencing crashes this might be due to some problems with your
computer hardware or configuration.
Is your PC matching the recommended system requirements as found in the
helpfile? What OS are you using, did you install the most recent
servicepacks?
Do you have similar problems with other software on this computer as
well? Unexpected system crashes often occure because of corrupt
RAM chips. DIAdem is using a lot of memory - so maybe you are accessing
regions that other programs dont use and - for that reason - see
the crashes only in DIAdem.
You are writing that the processing takes 3 times longer than expected.
How do you compare? Have you been using elder versions of DIAdem which
were faster, or are you comparing with the processing speed of another
computer?
There are some things I would do to try to improve the performance.
Check that you have at least 256MB RAM
Check that you are using Windows 2000 with servicepack 4 or XP with servicepack 1 at least
Reinstall DIAdem, use the version 9.1 SP2 instead of the installer you have been using. You can download this installer here.
Add servicepack 2b afterwards. The latter is a selfextracting zipfile
which has to be unpacked in the DIAdem directory while the first is a
complete DIAdem installer.
Replace the RAM modules of your PC.
You are welcome to post again if you dont get any further. In this case
please give some more information about the system such as CPU, OS,..
and the crashes. When do they occure? Is it a specific function or
module you are using when DIAdem crashes. What does the error messages
tell you about the module in which the exeptions occure?
Regards
Ingo Schumacher
Systems Engineer Sound&VibrationNational Instruments Germany

TFTP Read Access Violation in Snoop while doing network boot

Hi
I have setup my Oracle dhcp server and AI on oracle 11.1.
configure the /etc/ethers and /etc/hosts file as well.
pntadm and dhtam is also setup with macro
I deplou solaris 11.1 AI sparc image as my service
create-client and manifest is also associated as per client machine Mac interface
On client machine
I created the devalias entry for my Nic interface
did now
boot net:dhcp
Requesting Internet Address for 0:e:1E:8:bf:f8
Requesting Internet Address for 0:e:1E:8:bf:f8
Time out waiting for tftp reply
On server machine in snoop its showing
tftp read "01010F19" (octet)
TFTP Error : Access violation
I check tftp service is running on server as below
/usr/sbin/in.tftpd -s /etc/netboot
Please help me i am not able to figure out whats the problem
Thanks

But even on dhcp it doesn't work without setting network-boot-arguments on OBP
If i don't feed any entry in /etc/ethers and /etc/hosts
whenvever I do on client side boot net:dhcp it always give rarp messages in the snoop on server.
What can be the reason.

How can I repair "an access violation has occurred"

I found this message after you install the update of an audio software (Pro Tools 8.0.5) and after trying to listen to an audio recording "an access violation has occurred." In a later appeared to me the message "/ System / Library / Extensions / CDSDAAudioCaptureSupport.Kext". I removed the software completely reinstalled all audio and I havethe previous version but to no avail. I also reinstalled operating system from OS 10.6.2 Leopard up to 10.6.8 but still nothing. The message reappears when I use the audio software is not allowing me to listen to the audio (only with ProTools, while iTunes feature regularly. I do not know what to do yet.

Linc Davis wrote:
It's the PACE DRM rootkit that's installed along with the Pro Tools application. Its purpose is to cripple your computer so that you can only do what the developer chooses to let you do. If you have a problem with that, you'll have to take it up with DigiDesign, or get rid of their product.
Most absurd response to a question I have ever read...
DRM protects composers life myself from theft. I just hate it when people steal my stuff. Don't you?
I've been a PT professional user for well over a decade. My computer is in no way "crippled". I can do what I want with it and what I want with that software. I run PT with iTunes open all day long with no issue. I can import audio from my iTunes library into PT with no issue. If the audio you are trying to import is protected (from being stolen and remixed etc.) than no, you can't import it into PT. I'm pretty sure that most law abiding citizens would agree that having thier own personal livelyhood protected under law would be a good thing. But for some reason, this society thinks that musicians and other creative professionals don't deserve the same level of protection and don't need to feed thier families...

Error Occuring While Processing Data With DIAdem 8.1Exception EAccessViolation in module ntdll.dll at 000111DE. Access violation at address 7C9111DE in module 'ntdll.dll". Read address 37363430

Hello,
We are having an issue running Diadem 8.1 on a new HP XW 9400 with Windows XP SP2. 3 errors have been occuring with frequent crashes, they are:
1) "1Exception EAccessViolation in module ntdll.dll at 000111DE. Access violation at address 7C9111DE in module 'ntdll.dll". Read address 37363430.
2) The instruction at "0x7c9111de" referenced memory at "0x352e302d". The memory could not be "read".
3) ---Error--- DIAdem
Error in Autosequence - processing in line: 74 (IARV_VAR_GET)
Runtime Error while executing command "Iarv2Txt$ := FR(T9,L1)"
Error type: ACCESS VIOLATION
Error address: 000101DE
Module name:ntdll.dll
We are using the same scripts and version 8.1 on a variety of Dell desktop computers (W2K and XP SP2) without any issue, looking for suggestions as this affects no other software on the HP XW 9400 other than DIAdem. Appreciate any suggestions.
Message Edited by swillh on 06-25-2007 08:55 AM

Christian,
I will answer your questions in the text below. Thanks for your help.
Hi swillh,
I also would like to help you.
Unfortunately, The reported access violation in the central Windows ntdll.dll is very unspecific.
May be the following questions will help you to provide me more info.
1. You mentioned that the aut's and - I think - also the accessed text file reside on a server.
Is there a stable network connection?
The server can sometimes be a little slow but the connection is good. This computer is using the same connection that the prior computer utilized without issue.
Are the files accessed by multiple clients simultaneously?
It is possible that more than one computer can be accessing the same file, but again, this has never been an issue. We are reading the files only, not writing to them.
The processing routines we are running have used for over 5 years without any issues until adding this computer.
Is the text file read by one client while another client is writing the same file?
No, files are "read only"
2. Have you already tested opening the file with the FileOpen command before calling FR?
Yes
Do you see any chance to convert the aut to a vbs file? This gives you more alternatives in accessing text files.
3. What do you mean with "processing ATD's with 30 or more channels of data"? Where is the relation between ATD files and data channels?
Processing Crash Dummy data with file sets low in channel count (15 channels) result in successful processing without any crashes or access errors. When processing dummies with more than 20 channels we sometimes encounter these issues. The higher channel count may be the only common factor I can find in these faults.
Steve
Message Edited by swillh on 07-09-2007 08:44 AM

What does this error mean? Error: Access violation at address 0053DD46

I am trying to run diff reports using batch scripts, and its very puzzling that some of the diff report scripts within the batch script are running and some are not, there is no consistency to what is getting errored out.
I then tried running them manually in foreground on the client and I get the same issue. Has anyone encountered this issue? What do I make of it?,
4/24/2013 1:29:30 PM - *** MDMConnect starting ***
4/24/2013 1:29:30 PM - Logged in successfully.
4/24/2013 1:29:30 PM - Started export job for PLN_FLD_ACCT_DIFF
4/24/2013 1:29:34 PM - ERemotableException with message: "Server was unable to process request. ---> Error during Export. Export was unable to run. Error: Access violation at address 0053DD46 in module 'mdm_ntier_engine.exe'. Read of address 00000024" while running Export
4/24/2013 1:29:34 PM - => ERROR: Data Relationship Management Server returned error: "Server was unable to process request. ---> Error during Export. Export was unable to run. Error: Access violation at address 0053DD46 in module 'mdm_ntier_engine.exe'. Read of address 00000024."
4/24/2013 1:29:34 PM - *** MDMConnect stopping ***
Thank you
Tanuja Donavalli

This is issue is coherent in DRM version 11.1.1.2
Whenever a property is deleted, the references to that property would still exists/stored in tables. The next version of DRM is made to address this issue, where in it takes care of removing all references whenever we delete the property.
Cause: Properties was deleted from DRM client but the value was still stored in the compare table for Difference export and causing export to fail.
Solution: Need to recreate the deleted properties and remove the properties in the exports and delete the properties.
Going Forward: Instead of deleting the properties we need to remove the property from the export and hide the property.
Hope this helps.

Access Violation while initialising WEBUTIL on Ora9iDS

Hello,
as part of an urgent evaluation I installed WEBUTIL as described in the documentation, did the additional steps described in the readme and added WEBUTIL as described to an existing form. Now the form raises an access violation error while executing trigger WHEN-CUSTOM-ITEM-EVENT on item WEBUTIL.WEBUTIL_FILETRANSFER_FUNCTIONS exactly when calling procedure WEBUTIL_CORE.CustomEventHandler while registering the beans.
Did anybody experience the like? Any guess what's going wrong or what could help?
The crash is documented in the log as follows:
[09/09/03 08:38:46 Westeuropäische Sommerzeit]::Client Status [ConnId=0, PID=3048]
 >> ERROR: Abnormal termination, Error Code: C0000005 ACCESS_VIOLATION
======================= STACK DUMP =======================
Fault address: 60A98D4D 01:00097D4D
Module: E:\Programme\OraHome1\bin\orapls9.dll
System Information:
Operating System: Windows NT Version 5.0 Build 2195 Service Pack 4
Command line: ifweb90 server webfile=HTTP-0,0,1,53.147.33.61
FORM/BLOCK/FIELD: DOKUMENTE:DOKUMENTE.KLARTEXT
Last Trigger: WHEN-CUSTOM-ITEM-EVENT - (In Progress)
Msg: <NULL>
Last Builtin: NAME_IN - (Successfully Completed)
Registers:
EAX:00000000
EBX:0012D9C0
ECX:00000000
EDX:0012D9C0
ESI:0777C6E4
EDI:02A26C78
CS:EIP:001B:60A98D4D
SS:ESP:0023:0012D978 EBP:0012D998
DS:0023 ES:0023 FS:003B GS:0000
Flags:00010246
------------------- Call Stack Trace ---------------------
Frameptr RetAddr Param#1 Param#2 Param#3 Param#4 Function Name
0x0012d998 60a3d308 0777c6e4 00000001 0012d9c0 070468a8 pfrb1assign_aad2va
0x0012d9ec 60a92b11 0777c6e4 00000001 66020030 070468a8 pevmGBVAR+d8
0x0012e0f0 60a1ce7d 0777c6e4 02a26c78 0776dd6c 00000002 _pfrrun+6841
0x0012e158 6601ea45 02a26c78 0777c6e4 02a46f00 029de3b4 _peicnt+ed
0x02a26874 029de3b4 65fdb2a0 65fdb2e0 65da1f30 00000000 0x6601ea45
0x02a46f00 00000001 0000000a 02a46fd8 0026181f 65d51752 0x029de3b4
------------------- End of Stack Trace -------------------
WebUtil-Logfile is not very verbose (despite detailed logging enabled):
53.147.33.61:ZSCHAU: Connection from Form=E:\ISAP_ASP4\isap\websourcen\Doktestweb.fmx Client O/S=Windows 2000 locale=de
53.147.33.61:ZSCHAU: 2003-Sep-09 08:38:00.889 WUF[VBeanCommon.getIPAddress()] 53.147.33.61
53.147.33.61:ZSCHAU: 2003-Sep-09 08:38:00.929 WUH[VBeanCommon.getIPAddress()] 53.147.33.61
53.147.33.61:ZSCHAU: 2003-Sep-09 08:38:00.949 WUS[VBeanCommon.getIPAddress()] 53.147.33.61
Java Console prints:
JInitiator: Version 1.3.1.9
Verwendung der JRE-Version 1.3.1.9 Java HotSpot(TM) Client VM
Home-Verzeichnis des Benutzers = C:\Dokumente und Einstellungen\zschau
Proxy-Konfiguration:Automatische Proxy-Konfiguration
JAR cache enabled
Location: C:\Dokumente und Einstellungen\zschau\Oracle Jar Cache
Maximum size: 50 MB
Compression level: 0
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
q: hide console
s: dump system properties
t: dump thread list
x: clear classloader cache
0-5: set trace level to <n>
Loading http://localhost:8888/forms90/webutil/webutil.jar from JAR cache
Loading http://localhost:8888/forms90/webutil/jacob.jar from JAR cache
Loading http://localhost:8888/forms90/java/f90all_jinit.jar from JAR cache
RegisterWebUtil - Loading Webutil Version 1.0.2 Beta
connectMode=HTTP, native.
Forms Applet-Version : 90290
2003-Sep-09 08:38:00.819 WUI[VBeanCommon.findLocalHost()] obtaining LocalHost info from InetAddress
2003-Sep-09 08:38:00.839 WUI[VBeanCommon.getIPAddress()] 53.147.33.61
2003-Sep-09 08:38:00.879 WUF[VBeanCommon.findLocalHost()] obtaining LocalHost info from InetAddress
2003-Sep-09 08:38:00.889 WUF[VBeanCommon.getIPAddress()] 53.147.33.61
2003-Sep-09 08:38:00.909 WUH[VBeanCommon.findLocalHost()] obtaining LocalHost info from InetAddress
2003-Sep-09 08:38:00.929 WUH[VBeanCommon.getIPAddress()] 53.147.33.61
2003-Sep-09 08:38:00.939 WUS[VBeanCommon.findLocalHost()] obtaining LocalHost info from InetAddress
2003-Sep-09 08:38:00.949 WUS[VBeanCommon.getIPAddress()] 53.147.33.61
2003-Sep-09 08:38:00.969 WUT[VBeanCommon.findLocalHost()] obtaining LocalHost info from InetAddress
2003-Sep-09 08:38:00.969 WUT[VBeanCommon.getIPAddress()] 53.147.33.61
2003-Sep-09 08:38:01.460 WUO[VBeanCommon.findLocalHost()] obtaining LocalHost info from InetAddress
2003-Sep-09 08:38:01.470 WUO[VBeanCommon.getIPAddress()] 53.147.33.61
2003-Sep-09 08:38:01.500 WUL[VBeanCommon.findLocalHost()] obtaining LocalHost info from InetAddress
2003-Sep-09 08:38:01.510 WUL[VBeanCommon.getIPAddress()] 53.147.33.61
2003-Sep-09 08:38:01.550 WUB[VBeanCommon.findLocalHost()] obtaining LocalHost info from InetAddress
2003-Sep-09 08:38:01.560 WUB[VBeanCommon.getIPAddress()] 53.147.33.61
2003-Sep-09 08:38:48.268 WUB[VBeanCommon.destroy()] WebUtil Browser Functions being removed..
2003-Sep-09 08:38:48.298 WUL[VBeanCommon.destroy()] WebUtil C API Functions being removed..
2003-Sep-09 08:38:49.59 WUO[VBeanCommon.destroy()] WebUtil Client Side Ole Functions being removed..
2003-Sep-09 08:38:49.89 WUT[VBeanCommon.destroy()] WebUtil File Transfer Bean being removed..
2003-Sep-09 08:38:49.89 WUS[VBeanCommon.destroy()] WebUtil Session Monitoring Facilities being removed..
2003-Sep-09 08:38:49.89 WUH[VBeanCommon.destroy()] WebUtil Client Side Host Commands being removed..
2003-Sep-09 08:38:49.99 WUF[VBeanCommon.destroy()] WebUtil Client Side File Functions being removed..
2003-Sep-09 08:38:49.99 WUI[VBeanCommon.destroy()] WebUtil GetClientInfo Utility being removed..
I run Ora9iDS on a Windows2000 system.
Thanks to anybody who tries to help.

Hello, Grant,
the crash occurs before I try to do anything vital. There is some init stuff in the form (initialising items, global variables etc.), query execution for initial displaying of database entries and a sychronize statement. After that the triggers in the WEBUTIL section fire, as I understand to initialise the beans (registering). As part of this registering the crash occurs - before I call any of the WEBUTIL functionality from my own code.

Re: (forte-users) access violation caught in debugmode

Eric,
There has been a problem with Forte debug mode for sometime now when the app
is silent. If you attempt to inspect the variables when the app is in the
'silent' mode, i.e., waiting on an event loop for a user input or a system
event, then you get the "Access violation caught ..." exception message and
the workspace including the launch server crashes.
If you are getting this problem in the 'step-through' mode, you should look
at the lauch server immediately after you get the exception before
everything disappears. There could be a stack backtrace due to some illegal
reference. We have faced a similar situation before but the error appeared
both in the 'debug' and 'run' modes.
Hope this helps.
Braja K Chattaraj.
From: Eric Decossaux <[email protected]>
To: forte mailing <[email protected]>
Subject: (forte-users) access violation caught in debug mode
Date: Thu, 23 Sep 1999 17:31:39 +0200
Hello,
I have a problem using Forte in debug mode. If I run my program on my NT
machine from the partition workshop (distributed run), the program works
fine except that some object does not display what I'm expecting. So I
want to use the debug mode to inspect the objets of this window. When I
choose the "local variables" option to see the content of my window, I
have a "access violation caught" and forte disappears. If I just let my
program run without choosing this option, everything is the same than
with the distributed run.
Does somebody have an idea what to look for ? I really want to look the
inside the attributes of this window.
We recently upgraded from release 30G2 to release 30L2. Could it be the
problem ?
Eric Decossaux
Cliniques Universitaires St Luc
Informatique des Laboratoires
av Hippocrate 10 / 1730
1200 Bruxelles
+32+2+764 17 53
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

Eric,
Another possibility has to do with the repository. You said you recently
migrated 30G2 to release 30L2.
Many strange problems have been traced to release migrations with old
repositories. If the repository was properly migrated another thing you can try
is to export the project(s) to PEX files, delete them from the repository, and
then re-import. I know this can be time consuming but I have solved more than
one unexplained problem in the IDE by doing it.
---------------------- Forwarded by Charlie Shell/Bsg/MetLife/US on 09/23/99
01:19 PM ---------------------------
"Ajith Kallambella" <[email protected]> on 09/23/99 12:08:54 PM
To: [email protected], [email protected]
cc: (bcc: Charlie Shell/Bsg/MetLife/US)
Subject: Re: (forte-users) access violation caught in debug mode
Eric,
Sometimes( 90% ) you can solve this problem by
checking out the class that is causing the crash
and force-compiling it.
If it doesn't help, run through this checklist.
1. Do you have enough memory resources.?
2. Is the object you are inspecting held in a lock ?
( mutex, transaction lock etc )
3. Does it work when you wait for sometime at the
breakpoint before inspecting the values? I mean
are you interrupting some process thread?
4. Does it work if you log the attributes using logmgr?
5. Are you using any call-outs/call-ins? Any external
systems integration? Sometimes( for reasons beyond
my comprehension ) the objects allocated outside
Forte gets corrupted when its passed back and forth.
6. ...finally...Santa Clause, help me!
Ajith Kallambella M.
Forte Systems Consultant.
From: Eric Decossaux <[email protected]>
To: forte mailing <[email protected]>
Subject: (forte-users) access violation caught in debug mode
Date: Thu, 23 Sep 1999 17:31:39 +0200
Hello,
I have a problem using Forte in debug mode. If I run my program on my NT
machine from the partition workshop (distributed run), the program works
fine except that some object does not display what I'm expecting. So I
want to use the debug mode to inspect the objets of this window. When I
choose the "local variables" option to see the content of my window, I
have a "access violation caught" and forte disappears. If I just let my
program run without choosing this option, everything is the same than
with the distributed run.
Does somebody have an idea what to look for ? I really want to look the
inside the attributes of this window.
We recently upgraded from release 30G2 to release 30L2. Could it be the
problem ?
Eric Decossaux
Cliniques Universitaires St Luc
Informatique des Laboratoires
av Hippocrate 10 / 1730
1200 Bruxelles
+32+2+764 17 53
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

JDeveloper 3.2 Problems - Access violation errors

Hi,
I suddenly got the following error message on a dialog box when I was editing code in the visual designer:
QUOTE
Access violation at address 00402FC8 'jdeveloper.exe'. Read of address FFFFFFF
UNQUOTE
When I tried to save my work, I was not able to received a similar message. When I tried to exit, I recived the following message:
QUOTE
JDeveloper was unable to autosave the current workspace. Do you wish to close the workspace anyway?"
UNQUOTE
After exiting the workspace, I was not able to reopen the workspace. I created a new workspace and added my projects to the new workspace. I was happy that I did not lose my work.
I have received the access violation error before. I do not know what causes it and I would appreciate very much if the JDev team explains why such an error occurs.
Thanks.

Hi,
We intermittently see postings of this kind. The more information you can provide us about your environment and what you are doing when you get the error, the better:
1. What OS are you running (include version and SP).
2. What kind of processor does your machine run?
3. Do you have a single processor or multiple?
4. What kind of project were you working on? Did you create an empty project and a new class file and were just editing source code, or did you create some initial content using one of the wizards from the Object Gallery and were modifying the generated code, or did you import existing code from some other location?
5. How many source files did you have in the project?
6. Was the source file you were editing a .java file, or a .jsp, .xml, .html?
7. Does this happen frequently, or is this the first time? Has it happened since?
Again, the more detail you can provide, the better we are able to identify possible sources of trouble.

"Syntax error or access violation" on Data Flow Task OLE DB Data Source

I am implementing expression parameter for a SQL Server connection string (like this: http://danajaatcse.wordpress.com/2010/05/20/using-an-xml-configuration-file-and-expressions-in-an-ssis-package/) and it works fine except when it reaches data flow
task - OLE DB Source task. In this task, I execute a stored procedure like this:
exec SelectFromTableA ?,?,?
The error message is this:
0xC0202009 at Data Flow Task, OLE DB Source [2]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "Syntax error or access violation".
Error: 0xC004706B at Data Flow Task, SSIS.Pipeline: "OLE DB Source" failed validation and returned validation status "VS_ISBROKEN"
When I change the SQL command above with reading from table directly it works fine. I should also add that before changing connection string of the SQL data source to use expression, the SSIS package was working fine and I know that the connection string
is fine because other tasks in the package works fine!
Any idea why?

Hi AL.M,
As per my understanding, I think this problem is due to the mismatching between the source and the destination tables. We can reconfigured every of components of the package to check the table schemas and configuration settings, close the BIDS/SSDT and then
open and try to see if there are errors.
Besides, to trouble shoot this issue, we can use the variable window to see the variable's value. For more details, please refer to the following blog:
http://consultingblogs.emc.com/jamiethomson/archive/2005/12/05/2462.aspx
The following blog about “SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred: Reasons and troubleshooting” is for your reference:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/11/10/ssis-error-code-dts-e-oledberror-an-ole-db-error-has-occurred-reasons-and-troubleshooting.aspx
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Access Violation in DllMain of coherence.dll

I have an issue with C++ project, that using coherence (version 3.7). During loading the exe file dialog box is shown with the message: "The application failed to initialize properly (0xc0000005)". After clicking "OK" the process terminates.
Running under debugger I discovered the error place:
The error: 0xC0000005: Access violation writing location 0x00000010.
The call stack:
 ntdll.dll!_RtlpWaitForCriticalSection@4() + 0x5b bytes
 ntdll.dll!_RtlEnterCriticalSection@4() + 0x46 bytes
 iphlpapi.dll!76d626fd()
 [Frames below may be incorrect and/or missing, no symbols loaded for iphlpapi.dll]
 iphlpapi.dll!76d6605b()
 dnsapi.dll!_IpHelp_GetAdaptersInfo@4() + 0x32 bytes
 dnsapi.dll!_NetInfo_Build@4() + 0x2c bytes
 dnsapi.dll!_NetInfo_Get@8() + 0x28 bytes
 dnsapi.dll!_GetDnsServerRRSet@8() + 0x36 bytes
 dnsapi.dll!_DnsQuery_W@24() + 0xa8 bytes
 mswsock.dll!_myhostent_W@0() + 0xf8 bytes
 mswsock.dll!_RNRPROV_NSPStartup@8() + 0x47 bytes
 mswsock.dll!_NSPStartup@8() + 0x20dc bytes
 ws2_32.dll!NSPROVIDER::Initialize() + 0xa7 bytes
 ws2_32.dll!NSCATALOG::LoadProvider() + 0x4a bytes
 ws2_32.dll!LookupBeginEnumerationProc() + 0x154e bytes
 ws2_32.dll!DCATALOG::EnumerateCatalogItems() + 0x25 bytes
 ws2_32.dll!NSQUERY::LookupServiceBegin() + 0x98 bytes
 ws2_32.dll!_WSALookupServiceBeginW@12() + 0x84 bytes
 ws2_32.dll!_WSALookupServiceBeginA@12() + 0x6f bytes
 ws2_32.dll!getxyDataEnt() + 0x5d bytes
 ws2_32.dll!_gethostname@8() + 0xa7 bytes
 coherence.dll!coherence::native::NativeInetHelper::getLocalHostName() Line 250 + 0x43 bytes C++
 coherence.dll!coherence::net::InetAddress::getLocalHost() Line 84 + 0x10 bytes C++
 coherence.dll!coherence::util::`anonymous namespace'::InetAddressInfo::InetAddressInfo() Line 56 + 0xd bytes C++
 coherence.dll!coherence::lang::factory<coherence::util::`anonymous namespace'::InetAddressInfo>::create() Line 389 + 0x44 bytes C++
 coherence.dll!coherence::lang::class_spec<coherence::util::`anonymous namespace'::InetAddressInfo,coherence::lang::extends<coherence::lang::Object,void>,coherence::lang::implements<void,void,void,void,void,void,void,void,void,void,void,void,void,void,void,void> >::create() Line 143 + 0x12 bytes C++
 coherence.dll!coherence::util::`anonymous namespace'::getInetAddressInfo() Line 252 + 0x2a bytes C++
 coherence.dll!coherence::util::`anonymous namespace'::`dynamic initializer for 'coh_static_init_func255''() Line 255 + 0xf bytes C++
 msvcr80.dll!78131742()
 coherence.dll!_CRT_INIT(void * hDllHandle=0x00440000, unsigned long dwReason=0, void * lpreserved=0x0012fd30) Line 316 + 0xf bytes C
 coherence.dll!__DllMainCRTStartup(void * hDllHandle=0x00440000, unsigned long dwReason=0, void * lpreserved=0x00000000) Line 492 + 0x8 bytes C
 coherence.dll!_DllMainCRTStartup(void * hDllHandle=0x00440000, unsigned long dwReason=1, void * lpreserved=0x0012fd30) Line 462 + 0x11 bytes C
 ntdll.dll!_LdrpCallInitRoutine@16() + 0x14 bytes
 ntdll.dll!_LdrpRunInitializeRoutines@4() + 0x205 bytes
 ntdll.dll!_LdrpInitializeProcess@20() - 0x96d bytes
 ntdll.dll!__LdrpInitialize@12() + 0x6269 bytes
 ntdll.dll!_KiUserApcDispatcher@20() + 0x7 bytes
According to [http://msdn.microsoft.com/en-us/library/ms682583(v=vs.85).aspx] :
The entry-point function should perform only simple initialization or termination tasks. It must not call the LoadLibrary or LoadLibraryEx function (or a function that calls these functions), because this may create dependency loops in the DLL load order. This can result in a DLL being used before the system has executed its initialization code. Similarly, the entry-point function must not call the FreeLibrary function (or a function that calls FreeLibrary) during process termination, because this can result in a DLL being used after the system has executed its termination code.
Because Kernel32.dll is guaranteed to be loaded in the process address space when the entry-point function is called, calling functions in Kernel32.dll does not result in the DLL being used before its initialization code has been executed. Therefore, the entry-point function can call functions in Kernel32.dll that do not load other DLLs. For example, DllMain can create synchronization objects such as critical sections and mutexes, and use TLS. Unfortunately, there is not a comprehensive list of safe functions in Kernel32.dll.
Windows 2000: Do not create a named synchronization object in DllMain because the system will then load an additional DLL.
Calling functions that require DLLs other than Kernel32.dll may result in problems that are difficult to diagnose. For example, calling User, Shell, and COM functions can cause access violation errors, because some functions load other system components. Conversely, calling functions such as these during termination can cause access violation errors because the corresponding component may already have been unloaded or uninitialized.
Perhaps the coherence developers should define init/cleanup functions (i.e. coherence_init(), coherence_cleanup()) and perform all initialization/cleanup actions there.

The test with many dll's does not reproduced this issue. I don't have much time to continue playing with it. BTW look at the simple test application log (the source of the test you can find on my another thread: {thread:id=2286271}) You can see how many times called LoadLibrary() from coherence.dll!DllMain (marked in red). And it doesn't matter, that it works most of the time. It is so called undefined behavior.
Started "TEST.EXE" (process 0x1694) at address 0x00400000 by thread 1. Successfully hooked module.
Loaded "NTDLL.DLL" at address 0x7C900000 by thread 1. Successfully hooked module.
Loaded "KERNEL32.DLL" at address 0x7C800000 by thread 1. Successfully hooked module.
DllMain(0x7C900000, DLL_PROCESS_ATTACH, 0x00000000) in "NTDLL.DLL" called by thread 1.
DllMain(0x7C900000, DLL_PROCESS_ATTACH, 0x00000000) in "NTDLL.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C800000, DLL_PROCESS_ATTACH, 0x00000000) in "KERNEL32.DLL" called by thread 1.
DllMain(0x7C800000, DLL_PROCESS_ATTACH, 0x00000000) in "KERNEL32.DLL" returned 1 (0x1) by thread 1.
Injected "DEPENDS.DLL" at address 0x08370000 by thread 1.
DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in "DEPENDS.DLL" called by thread 1.
DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in "DEPENDS.DLL" returned 1 (0x1) by thread 1.
Loaded "COHERENCE.DLL" at address 0x10000000 by thread 1. Successfully hooked module.
Loaded "WS2_32.DLL" at address 0x71AB0000 by thread 1. Successfully hooked module.
Loaded "ADVAPI32.DLL" at address 0x77DD0000 by thread 1. Successfully hooked module.
Loaded "RPCRT4.DLL" at address 0x77E70000 by thread 1. Successfully hooked module.
Loaded "SECUR32.DLL" at address 0x77FE0000 by thread 1. Successfully hooked module.
Loaded "MSVCRT.DLL" at address 0x77C10000 by thread 1. Successfully hooked module.
Loaded "WS2HELP.DLL" at address 0x71AA0000 by thread 1. Successfully hooked module.
Loaded "MSVCP80.DLL" at address 0x7C420000 by thread 1. Successfully hooked module.
Loaded "MSVCR80.DLL" at address 0x78130000 by thread 1. Successfully hooked module.
Loaded "IMAGEHLP.DLL" at address 0x76C90000 by thread 1. Successfully hooked module.
DllMain(0x77FE0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "SECUR32.DLL" called by thread 1.
DllMain(0x77FE0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "SECUR32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77E70000, DLL_PROCESS_ATTACH, 0x0012FD30) in "RPCRT4.DLL" called by thread 1.
DllMain(0x77E70000, DLL_PROCESS_ATTACH, 0x0012FD30) in "RPCRT4.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77DD0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "ADVAPI32.DLL" called by thread 1.
DllMain(0x77DD0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "ADVAPI32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77C10000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCRT.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "InitializeCriticalSectionAndSpinCount") called from "MSVCRT.DLL" at address 0x77C379C2 and returned 0x7C80B8C9 by thread 1.
DllMain(0x77C10000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCRT.DLL" returned 1 (0x1) by thread 1.
DllMain(0x71AA0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "WS2HELP.DLL" called by thread 1.
DllMain(0x71AA0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "WS2HELP.DLL" returned 1 (0x1) by thread 1.
DllMain(0x71AB0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "WS2_32.DLL" called by thread 1.
DllMain(0x71AB0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "WS2_32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x78130000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCR80.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "FlsAlloc") called from "MSVCR80.DLL" at address 0x78133001 and returned NULL by thread 1. Error: The specified procedure could not be found (127).
[snip]
GetProcAddress(0x7C800000 [KERNEL32.DLL], "GetSystemWindowsDirectoryW") called from "MSVCR80.DLL" at address 0x78131F1A and returned 0x7C80ADC9 by thread 1.
DllMain(0x78130000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCR80.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C420000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCP80.DLL" called by thread 1.
DllMain(0x7C420000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCP80.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76C90000, DLL_PROCESS_ATTACH, 0x0012FD30) in "IMAGEHLP.DLL" called by thread 1.
DllMain(0x76C90000, DLL_PROCESS_ATTACH, 0x0012FD30) in "IMAGEHLP.DLL" returned 1 (0x1) by thread 1.
DllMain(0x10000000, DLL_PROCESS_ATTACH, 0x0012FD30) in "COHERENCE.DLL" called by thread 1.
GetProcAddress(0x71AB0000 [WS2_32.DLL], "accept") called from "WS2_32.DLL" at address 0x71AB737E and returned 0x71AC1040 by thread 1.
[snip]
GetProcAddress(0x71AB0000 [WS2_32.DLL], "freeaddrinfo") called from "WS2_32.DLL" at address 0x71AB737E and returned 0x71AB2B0B by thread 1.
LoadLibraryA("C:\WINNT\System32\mswsock.dll") called from "WS2_32.DLL" at address 0x71AB4EA0 by thread 1.
Loaded "MSWSOCK.DLL" at address 0x71A50000 by thread 1. Successfully hooked module.
DllMain(0x71A50000, DLL_PROCESS_ATTACH, 0x00000000) in "MSWSOCK.DLL" called by thread 1.
DllMain(0x71A50000, DLL_PROCESS_ATTACH, 0x00000000) in "MSWSOCK.DLL" returned 1 (0x1) by thread 1.
LoadLibraryA("C:\WINNT\System32\mswsock.dll") returned 0x71A50000 by thread 1.
GetProcAddress(0x71A50000 [MSWSOCK.DLL], "NSPStartup") called from "WS2_32.DLL" at address 0x71AB4EB7 and returned 0x71A5A830 by thread 1.
LoadLibraryA("DNSAPI.dll") called from "MSWSOCK.DLL" at address 0x71A5C714 by thread 1.
Loaded "DNSAPI.DLL" at address 0x76F20000 by thread 1. Successfully hooked module.
DllMain(0x76F20000, DLL_PROCESS_ATTACH, 0x00000000) in "DNSAPI.DLL" called by thread 1.
DllMain(0x76F20000, DLL_PROCESS_ATTACH, 0x00000000) in "DNSAPI.DLL" returned 1 (0x1) by thread 1.
LoadLibraryA("DNSAPI.dll") returned 0x76F20000 by thread 1.
GetProcAddress(0x76F20000 [DNSAPI.DLL], "DnsQueryConfigAllocEx") called from "MSWSOCK.DLL" at address 0x71A5C6FD and returned 0x76F27A55 by thread 1.
LoadLibraryW("rpcrt4.dll") called from "RPCRT4.DLL" at address 0x77E8B42D by thread 1.
LoadLibraryW("rpcrt4.dll") returned 0x77E70000 by thread 1.
GetProcAddress(0x76F20000 [DNSAPI.DLL], "DnsApiFree") called from "MSWSOCK.DLL" at address 0x71A5C6FD and returned 0x76F237A1 by thread 1.
GetProcAddress(0x76F20000 [DNSAPI.DLL], "DnsQuery_W") called from "MSWSOCK.DLL" at address 0x71A5C6FD and returned 0x76F22DA3 by thread 1.
LoadLibraryA("iphlpapi.dll") called from "DNSAPI.DLL" at address 0x76F2AB0A by thread 1.
Loaded "IPHLPAPI.DLL" at address 0x76D60000 by thread 1. Successfully hooked module.
Loaded "USER32.DLL" at address 0x7E410000 by thread 1. Successfully hooked module.
Loaded "GDI32.DLL" at address 0x77F10000 by thread 1. Successfully hooked module.
DllMain(0x77F10000, DLL_PROCESS_ATTACH, 0x00000000) in "GDI32.DLL" called by thread 1.
DllMain(0x77F10000, DLL_PROCESS_ATTACH, 0x00000000) in "GDI32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7E410000, DLL_PROCESS_ATTACH, 0x00000000) in "USER32.DLL" called by thread 1.
DllMain(0x7E410000, DLL_PROCESS_ATTACH, 0x00000000) in "USER32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76D60000, DLL_PROCESS_ATTACH, 0x00000000) in "IPHLPAPI.DLL" called by thread 1.
DllMain(0x76D60000, DLL_PROCESS_ATTACH, 0x00000000) in "IPHLPAPI.DLL" returned 1 (0x1) by thread 1.
LoadLibraryA("iphlpapi.dll") returned 0x76D60000 by thread 1.
GetProcAddress(0x76D60000 [IPHLPAPI.DLL], "GetAdaptersInfo") called from "DNSAPI.DLL" at address 0x76F2AB5F and returned 0x76D66051 by thread 1.
GetProcAddress(0x76D60000 [IPHLPAPI.DLL], "GetPerAdapterInfo") called from "DNSAPI.DLL" at address 0x76F2AB5F and returned 0x76D66769 by thread 1.
GetProcAddress(0x76F20000 [DNSAPI.DLL], "DnsRecordListFree") called from "MSWSOCK.DLL" at address 0x71A5C6FD and returned 0x76F25B12 by thread 1.
LoadLibraryA("C:\WINNT\System32\winrnr.dll") called from "WS2_32.DLL" at address 0x71AB4EA0 by thread 1.
Loaded "WINRNR.DLL" at address 0x76FB0000 by thread 1. Successfully hooked module.
Loaded "WLDAP32.DLL" at address 0x76F60000 by thread 1. Successfully hooked module.
DllMain(0x76F60000, DLL_PROCESS_ATTACH, 0x00000000) in "WLDAP32.DLL" called by thread 1.
DllMain(0x76F60000, DLL_PROCESS_ATTACH, 0x00000000) in "WLDAP32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76FB0000, DLL_PROCESS_ATTACH, 0x00000000) in "WINRNR.DLL" called by thread 1.
DllMain(0x76FB0000, DLL_PROCESS_ATTACH, 0x00000000) in "WINRNR.DLL" returned 1 (0x1) by thread 1.
LoadLibraryA("C:\WINNT\System32\winrnr.dll") returned 0x76FB0000 by thread 1.
GetProcAddress(0x76FB0000 [WINRNR.DLL], "NSPStartup") called from "WS2_32.DLL" at address 0x71AB4EB7 and returned 0x76FB1688 by thread 1.
LoadLibraryA("C:\WINNT\System32\mswsock.dll") called from "WS2_32.DLL" at address 0x71AB4EA0 by thread 1.
LoadLibraryA("C:\WINNT\System32\mswsock.dll") returned 0x71A50000 by thread 1.
GetProcAddress(0x71A50000 [MSWSOCK.DLL], "NSPStartup") called from "WS2_32.DLL" at address 0x71AB4EB7 and returned 0x71A5A830 by thread 1.
LoadLibraryA("C:\WINNT\system32\ws2_32") called from "COHERENCE.DLL" at address 0x100A70B4 by thread 1.
LoadLibraryA("C:\WINNT\system32\ws2_32") returned 0x71AB0000 by thread 1.
GetProcAddress(0x71AB0000 [WS2_32.DLL], "getaddrinfo") called from "COHERENCE.DLL" at address 0x100A70C6 and returned 0x71AB2A6F by thread 1.
[snip]
GetProcAddress(0x76F20000 [DNSAPI.DLL], "DnsNameCompare_W") called from "MSWSOCK.DLL" at address 0x71A5C6FD and returned 0x76F2349A by thread 1.
LoadLibraryA("rasadhlp.dll") called from "WS2_32.DLL" at address 0x71AB4FB8 by thread 1.
Loaded "RASADHLP.DLL" at address 0x76FC0000 by thread 1. Successfully hooked module.
DllMain(0x76FC0000, DLL_PROCESS_ATTACH, 0x00000000) in "RASADHLP.DLL" called by thread 1.
DllMain(0x76FC0000, DLL_PROCESS_ATTACH, 0x00000000) in "RASADHLP.DLL" returned 1 (0x1) by thread 1.
LoadLibraryA("rasadhlp.dll") returned 0x76FC0000 by thread 1.
GetProcAddress(0x76FC0000 [RASADHLP.DLL], "WSAttemptAutodialAddr") called from "WS2_32.DLL" at address 0x71AB4FCF and returned 0x76FC1AF3 by thread 1.
[snip]
GetProcAddress(0x76FC0000 [RASADHLP.DLL], "WSNoteSuccessfulHostentLookup") called from "WS2_32.DLL" at address 0x71AB4FF3 and returned 0x76FC13A0 by thread 1.
LoadLibraryA("kernel32.dll") called from "COHERENCE.DLL" at address 0x100AC4E3 by thread 1.
LoadLibraryA("kernel32.dll") returned 0x7C800000 by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "RtlCaptureContext") called from "COHERENCE.DLL" at address 0x100AC4F8 and returned 0x7C90331A by thread 1.
LoadLibraryA("C:\WINNT\system32\DBGHELP.dll") called from "IMAGEHLP.DLL" at address 0x76C97327 by thread 1.
Loaded "DBGHELP.DLL" at address 0x59A60000 by thread 1. Successfully hooked module.
Loaded "VERSION.DLL" at address 0x77C00000 by thread 1. Successfully hooked module.
DllMain(0x77C00000, DLL_PROCESS_ATTACH, 0x00000000) in "VERSION.DLL" called by thread 1.
DllMain(0x77C00000, DLL_PROCESS_ATTACH, 0x00000000) in "VERSION.DLL" returned 1 (0x1) by thread 1.
DllMain(0x59A60000, DLL_PROCESS_ATTACH, 0x00000000) in "DBGHELP.DLL" called by thread 1.
DllMain(0x59A60000, DLL_PROCESS_ATTACH, 0x00000000) in "DBGHELP.DLL" returned 1 (0x1) by thread 1.
LoadLibraryA("C:\WINNT\system32\DBGHELP.dll") returned 0x59A60000 by thread 1.
GetProcAddress(0x59A60000 [DBGHELP.DLL], "SymGetOptions") called from "IMAGEHLP.DLL" at address 0x76C97350 and returned 0x59A7B7AD by thread 1.
[snip]
GetProcAddress(0x7C900000 [NTDLL.DLL], "RtlDestroyQueryDebugBuffer") called from "DBGHELP.DLL" at address 0x59A7E675 and returned 0x7C954BC0 by thread 1.
DllMain(0x10000000, DLL_PROCESS_ATTACH, 0x0012FD30) in "COHERENCE.DLL" returned 1 (0x1) by thread 1.
Loaded "SXWMON32.DLL" at address 0x00CC0000 by thread 1. Successfully hooked module.
Loaded "SHELL32.DLL" at address 0x7C9C0000 by thread 1. Successfully hooked module.
Loaded "SHLWAPI.DLL" at address 0x77F60000 by thread 1. Successfully hooked module.
Loaded "OLE32.DLL" at address 0x774E0000 by thread 1. Successfully hooked module.
DllMain(0x77F60000, DLL_PROCESS_ATTACH, 0x00000000) in "SHLWAPI.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "CreateTimerQueue") called from "SHLWAPI.DLL" at address 0x77F65CF9 and returned 0x7C82BFE6 by thread 1.
[snip]
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DeleteTimerQueueTimer") called from "SHLWAPI.DLL" at address 0x77F65D35 and returned 0x7C821130 by thread 1.
DllMain(0x77F60000, DLL_PROCESS_ATTACH, 0x00000000) in "SHLWAPI.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C9C0000, DLL_PROCESS_ATTACH, 0x00000000) in "SHELL32.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "CreateActCtxW") called from "SHELL32.DLL" at address 0x7C9FAB3E and returned 0x7C8154FC by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "ActivateActCtx") called from "SHELL32.DLL" at address 0x7C9E7639 and returned 0x7C80A6E4 by thread 1.
LoadLibraryW("comctl32.dll") called from "SHELL32.DLL" at address 0x7C9FA774 by thread 1.
Loaded "COMCTL32.DLL" at address 0x773D0000 by thread 1. Successfully hooked module.
DllMain(0x773D0000, DLL_PROCESS_ATTACH, 0x00000000) in "COMCTL32.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "GetSystemWindowsDirectoryW") called from "COMCTL32.DLL" at address 0x7745B789 and returned 0x7C80ADC9 by thread 1.
[snip]
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DeactivateActCtx") called from "COMCTL32.DLL" at address 0x7745B6F4 and returned 0x7C80A715 by thread 1.
DllMain(0x773D0000, DLL_PROCESS_ATTACH, 0x00000000) in "COMCTL32.DLL" returned 1 (0x1) by thread 1.
LoadLibraryW("comctl32.dll") returned 0x773D0000 by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DeactivateActCtx") called from "SHELL32.DLL" at address 0x7C9E76A4 and returned 0x7C80A715 by thread 1.
LoadLibraryW("comctl32.dll") called from "SHELL32.DLL" at address 0x7C9FA8A6 by thread 1.
Loaded "COMCTL32.DLL" at address 0x5D090000 by thread 1. Successfully hooked module.
DllMain(0x5D090000, DLL_PROCESS_ATTACH, 0x00000000) in "COMCTL32.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "InitializeCriticalSectionAndSpinCount") called from "COMCTL32.DLL" at address 0x5D095338 and returned 0x7C80B8C9 by thread 1.
[snip]
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DeactivateActCtx") called from "COMCTL32.DLL" at address 0x5D0FF2BF and returned 0x7C80A715 by thread 1.
DllMain(0x5D090000, DLL_PROCESS_ATTACH, 0x00000000) in "COMCTL32.DLL" returned 1 (0x1) by thread 1.
LoadLibraryW("comctl32.dll") returned 0x5D090000 by thread 1.
GetProcAddress(0x5D090000 [COMCTL32.DLL], "InitCommonControlsEx") called from "SHELL32.DLL" at address 0x7C9FA8B6 and returned 0x5D093619 by thread 1.
DllMain(0x7C9C0000, DLL_PROCESS_ATTACH, 0x00000000) in "SHELL32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x774E0000, DLL_PROCESS_ATTACH, 0x00000000) in "OLE32.DLL" called by thread 1.
DllMain(0x774E0000, DLL_PROCESS_ATTACH, 0x00000000) in "OLE32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x00CC0000, DLL_PROCESS_ATTACH, 0x00000000) in "SXWMON32.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "FlsAlloc") called from "SXWMON32.DLL" at address 0x00CD8086 and returned NULL by thread 1. Error: The specified procedure could not be found (127).
[snip]
GetProcAddress(0x7C900000 [NTDLL.DLL], "ZwQueryVirtualMemory") called from "SXWMON32.DLL" at address 0x00CC1958 and returned 0x7C90D97E by thread 1.
DllMain(0x00CC0000, DLL_PROCESS_ATTACH, 0x00000000) in "SXWMON32.DLL" returned 1 (0x1) by thread 1.
GetProcAddress(0x59A60000 [DBGHELP.DLL], "StackWalk64") called from "IMAGEHLP.DLL" at address 0x76C97350 and returned 0x59A83492 by thread 1.
[snip]
GetProcAddress(0x59A60000 [DBGHELP.DLL], "SymGetModuleInfo64") called from "IMAGEHLP.DLL" at address 0x76C97350 and returned 0x59A7C94E by thread 1.
First chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "KERNEL32.DLL" at address 0x7C812AFB by thread 1.
First chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "KERNEL32.DLL" at address 0x7C812AFB by thread 1.
Thread 2 started in "KERNEL32.DLL" at address 0x7C8106F9.
DllMain(0x7C900000, DLL_THREAD_ATTACH, 0x00000000) in "NTDLL.DLL" called by thread 2.
DllMain(0x7C900000, DLL_THREAD_ATTACH, 0x00000000) in "NTDLL.DLL" returned 1 (0x1) by thread 2.
DllMain(0x7C800000, DLL_THREAD_ATTACH, 0x00000000) in "KERNEL32.DLL" called by thread 2.
DllMain(0x7C800000, DLL_THREAD_ATTACH, 0x00000000) in "KERNEL32.DLL" returned 1 (0x1) by thread 2.
DllMain(0x10000000, DLL_THREAD_ATTACH, 0x00000000) in "COHERENCE.DLL" called by thread 2.
DllMain(0x10000000, DLL_THREAD_ATTACH, 0x00000000) in "COHERENCE.DLL" returned 1 (0x1) by thread 2.
DllMain(0x71AB0000, DLL_THREAD_ATTACH, 0x00000000) in "WS2_32.DLL" called by thread 2.
DllMain(0x71AB0000, DLL_THREAD_ATTACH, 0x00000000) in "WS2_32.DLL" returned 1 (0x1) by thread 2.
DllMain(0x77DD0000, DLL_THREAD_ATTACH, 0x00000000) in "ADVAPI32.DLL" called by thread 2.
DllMain(0x77DD0000, DLL_THREAD_ATTACH, 0x00000000) in "ADVAPI32.DLL" returned 2147344385 (0x7FFDE001) by thread 2.
DllMain(0x77E70000, DLL_THREAD_ATTACH, 0x00000000) in "RPCRT4.DLL" called by thread 2.
DllMain(0x77E70000, DLL_THREAD_ATTACH, 0x00000000) in "RPCRT4.DLL" returned 4294967041 (0xFFFFFF01) by thread 2.
DllMain(0x77C10000, DLL_THREAD_ATTACH, 0x00000000) in "MSVCRT.DLL" called by thread 2.
DllMain(0x77C10000, DLL_THREAD_ATTACH, 0x00000000) in "MSVCRT.DLL" returned 1 (0x1) by thread 2.
DllMain(0x78130000, DLL_THREAD_ATTACH, 0x00000000) in "MSVCR80.DLL" called by thread 2.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DecodePointer") called from "MSVCR80.DLL" at address 0x78132C33 and returned 0x7C9132FF by thread 2.
[snip]
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DecodePointer") called from "MSVCR80.DLL" at address 0x78132D4A and returned 0x7C9132FF by thread 2.
DllMain(0x78130000, DLL_THREAD_ATTACH, 0x00000000) in "MSVCR80.DLL" returned 1 (0x1) by thread 2.
DllMain(0x71A50000, DLL_THREAD_ATTACH, 0x00000000) in "MSWSOCK.DLL" called by thread 2.
DllMain(0x71A50000, DLL_THREAD_ATTACH, 0x00000000) in "MSWSOCK.DLL" returned 1 (0x1) by thread 2.
DllMain(0x76F60000, DLL_THREAD_ATTACH, 0x00000000) in "WLDAP32.DLL" called by thread 2.
DllMain(0x76F60000, DLL_THREAD_ATTACH, 0x00000000) in "WLDAP32.DLL" returned 1 (0x1) by thread 2.
DllMain(0x77C00000, DLL_THREAD_ATTACH, 0x00000000) in "VERSION.DLL" called by thread 2.
DllMain(0x77C00000, DLL_THREAD_ATTACH, 0x00000000) in "VERSION.DLL" returned 1 (0x1) by thread 2.
DllMain(0x00CC0000, DLL_THREAD_ATTACH, 0x00000000) in "SXWMON32.DLL" called by thread 2.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DecodePointer") called from "SXWMON32.DLL" at address 0x00CD7CB0 and returned 0x7C9132FF by thread 2.
[snip]
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DecodePointer") called from "SXWMON32.DLL" at address 0x00CD7D94 and returned 0x7C9132FF by thread 2.
DllMain(0x00CC0000, DLL_THREAD_ATTACH, 0x00000000) in "SXWMON32.DLL" returned 1 (0x1) by thread 2.
DllMain(0x7C9C0000, DLL_THREAD_ATTACH, 0x00000000) in "SHELL32.DLL" called by thread 2.
DllMain(0x7C9C0000, DLL_THREAD_ATTACH, 0x00000000) in "SHELL32.DLL" returned 1 (0x1) by thread 2.
DllMain(0x774E0000, DLL_THREAD_ATTACH, 0x00000000) in "OLE32.DLL" called by thread 2.
DllMain(0x774E0000, DLL_THREAD_ATTACH, 0x00000000) in "OLE32.DLL" returned 1 (0x1) by thread 2.
First chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "KERNEL32.DLL" at address 0x7C812AFB by thread 1.
DllMain(0x5D090000, DLL_PROCESS_DETACH, 0x00000001) in "COMCTL32.DLL" called by thread 1.
Thread 2 exited with code 0 (0x0).
GetProcAddress(0x7C800000 [KERNEL32.DLL], "ReleaseActCtx") called from "COMCTL32.DLL" at address 0x5D0FF202 and returned 0x7C8130FF by thread 1.
DllMain(0x5D090000, DLL_PROCESS_DETACH, 0x00000001) in "COMCTL32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x773D0000, DLL_PROCESS_DETACH, 0x00000001) in "COMCTL32.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "ReleaseActCtx") called from "COMCTL32.DLL" at address 0x7745B656 and returned 0x7C8130FF by thread 1.
DllMain(0x773D0000, DLL_PROCESS_DETACH, 0x00000001) in "COMCTL32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x00CC0000, DLL_PROCESS_DETACH, 0x00000001) in "SXWMON32.DLL" called by thread 1.
DllMain(0x00CC0000, DLL_PROCESS_DETACH, 0x00000001) in "SXWMON32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x774E0000, DLL_PROCESS_DETACH, 0x00000001) in "OLE32.DLL" called by thread 1.
DllMain(0x774E0000, DLL_PROCESS_DETACH, 0x00000001) in "OLE32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C9C0000, DLL_PROCESS_DETACH, 0x00000001) in "SHELL32.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "ReleaseActCtx") called from "SHELL32.DLL" at address 0x7C9FDF7B and returned 0x7C8130FF by thread 1.
DllMain(0x7C9C0000, DLL_PROCESS_DETACH, 0x00000001) in "SHELL32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77F60000, DLL_PROCESS_DETACH, 0x00000001) in "SHLWAPI.DLL" called by thread 1.
DllMain(0x77F60000, DLL_PROCESS_DETACH, 0x00000001) in "SHLWAPI.DLL" returned 1 (0x1) by thread 1.
DllMain(0x59A60000, DLL_PROCESS_DETACH, 0x00000001) in "DBGHELP.DLL" called by thread 1.
DllMain(0x59A60000, DLL_PROCESS_DETACH, 0x00000001) in "DBGHELP.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77C00000, DLL_PROCESS_DETACH, 0x00000001) in "VERSION.DLL" called by thread 1.
DllMain(0x77C00000, DLL_PROCESS_DETACH, 0x00000001) in "VERSION.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76FC0000, DLL_PROCESS_DETACH, 0x00000001) in "RASADHLP.DLL" called by thread 1.
DllMain(0x76FC0000, DLL_PROCESS_DETACH, 0x00000001) in "RASADHLP.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76FB0000, DLL_PROCESS_DETACH, 0x00000001) in "WINRNR.DLL" called by thread 1.
DllMain(0x76FB0000, DLL_PROCESS_DETACH, 0x00000001) in "WINRNR.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76F60000, DLL_PROCESS_DETACH, 0x00000001) in "WLDAP32.DLL" called by thread 1.
DllMain(0x76F60000, DLL_PROCESS_DETACH, 0x00000001) in "WLDAP32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76D60000, DLL_PROCESS_DETACH, 0x00000001) in "IPHLPAPI.DLL" called by thread 1.
DllMain(0x76D60000, DLL_PROCESS_DETACH, 0x00000001) in "IPHLPAPI.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7E410000, DLL_PROCESS_DETACH, 0x00000001) in "USER32.DLL" called by thread 1.
DllMain(0x7E410000, DLL_PROCESS_DETACH, 0x00000001) in "USER32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77F10000, DLL_PROCESS_DETACH, 0x00000001) in "GDI32.DLL" called by thread 1.
DllMain(0x77F10000, DLL_PROCESS_DETACH, 0x00000001) in "GDI32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76F20000, DLL_PROCESS_DETACH, 0x00000001) in "DNSAPI.DLL" called by thread 1.
DllMain(0x76F20000, DLL_PROCESS_DETACH, 0x00000001) in "DNSAPI.DLL" returned 1 (0x1) by thread 1.
DllMain(0x71A50000, DLL_PROCESS_DETACH, 0x00000001) in "MSWSOCK.DLL" called by thread 1.
DllMain(0x71A50000, DLL_PROCESS_DETACH, 0x00000001) in "MSWSOCK.DLL" returned 1 (0x1) by thread 1.
DllMain(0x10000000, DLL_PROCESS_DETACH, 0x00000001) in "COHERENCE.DLL" called by thread 1.
DllMain(0x10000000, DLL_PROCESS_DETACH, 0x00000001) in "COHERENCE.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76C90000, DLL_PROCESS_DETACH, 0x00000001) in "IMAGEHLP.DLL" called by thread 1.
DllMain(0x76C90000, DLL_PROCESS_DETACH, 0x00000001) in "IMAGEHLP.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C420000, DLL_PROCESS_DETACH, 0x00000001) in "MSVCP80.DLL" called by thread 1.
DllMain(0x7C420000, DLL_PROCESS_DETACH, 0x00000001) in "MSVCP80.DLL" returned 1 (0x1) by thread 1.
DllMain(0x78130000, DLL_PROCESS_DETACH, 0x00000001) in "MSVCR80.DLL" called by thread 1.
DllMain(0x78130000, DLL_PROCESS_DETACH, 0x00000001) in "MSVCR80.DLL" returned 1 (0x1) by thread 1.
DllMain(0x71AB0000, DLL_PROCESS_DETACH, 0x00000001) in "WS2_32.DLL" called by thread 1.
DllMain(0x71AB0000, DLL_PROCESS_DETACH, 0x00000001) in "WS2_32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x71AA0000, DLL_PROCESS_DETACH, 0x00000001) in "WS2HELP.DLL" called by thread 1.
DllMain(0x71AA0000, DLL_PROCESS_DETACH, 0x00000001) in "WS2HELP.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77C10000, DLL_PROCESS_DETACH, 0x00000001) in "MSVCRT.DLL" called by thread 1.
DllMain(0x77C10000, DLL_PROCESS_DETACH, 0x00000001) in "MSVCRT.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77DD0000, DLL_PROCESS_DETACH, 0x00000001) in "ADVAPI32.DLL" called by thread 1.
DllMain(0x77DD0000, DLL_PROCESS_DETACH, 0x00000001) in "ADVAPI32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77E70000, DLL_PROCESS_DETACH, 0x00000001) in "RPCRT4.DLL" called by thread 1.
DllMain(0x77E70000, DLL_PROCESS_DETACH, 0x00000001) in "RPCRT4.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77FE0000, DLL_PROCESS_DETACH, 0x00000001) in "SECUR32.DLL" called by thread 1.
DllMain(0x77FE0000, DLL_PROCESS_DETACH, 0x00000001) in "SECUR32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x08370000, DLL_PROCESS_DETACH, 0x00000001) in "DEPENDS.DLL" called by thread 1.
DllMain(0x08370000, DLL_PROCESS_DETACH, 0x00000001) in "DEPENDS.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C800000, DLL_PROCESS_DETACH, 0x00000001) in "KERNEL32.DLL" called by thread 1.
DllMain(0x7C800000, DLL_PROCESS_DETACH, 0x00000001) in "KERNEL32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C900000, DLL_PROCESS_DETACH, 0x00000001) in "NTDLL.DLL" called by thread 1.
DllMain(0x7C900000, DLL_PROCESS_DETACH, 0x00000001) in "NTDLL.DLL" returned 1 (0x1) by thread 1.
Exited "TEST.EXE" (process 0x1694) with code 0 (0x0) by thread 1.
-----

Access Violation

I am running a macro and I get the error message: Runtime Error while excecuting command "VBSStart(FileDlgName)" Error Type: Access Violation Error address: 00000D20 Module Name: GfSBASE.dll. The macro and the database reside on the network and run fine from other computers. I have set up the database in the ODBC Data souce administrator.

I am running Diadem 8.0. The script is located on the network and runs fine from several other computers and has been in use, unchanged, for over a year. The script calls the diadem command CHNCFCFILTCALC from within a do loop. The program must access the database for each channel to get the parameters for how to filter that specific channel, it varies according to how the channel is named. The loop runs through my data set, filtering each channel, until it finds an empty channel name. Then it returns to a menu which allows me to perform other functions.
I added msgbox calls in as you suggested to try and narrow down where the problem is occurring but when I add them in the program does not run the same. For some reason it gets stuck in the do loop and does not increment to the next channel, it keeps trying to filter the first channel no matter how many times I run through the loop.
When I run the script in the script editor, it runs completely fine. The issue doesn’t crop up until I run it in the normal window (not script editor). So I have not been able to narrow it down to much. Plus I get varying errors, I ran it 4 times each with different results. 1st time: crash immediately, no channels filtered, and I got the Access violation that I mentioned earlier, 2nd time: two channels filtered then I get the following message: Exception EAccessViolation in Modul GfSBASE.DLL bei 00002034. Zugriffsverletzung bei Adresse 67D12034 in Modul ‘GfSBASE.DLL’. Schreiben von Adresse 000000011. When I click the OK button the following message appears: the instruction at “0x0136fa10” referenced memory at “0x00000003”. The memory could not be”written”. Click on OK to terminate the program. 3rd time; the program runs and fininshes normally, no problems at all. 4th time: the program filters two of three channels and then stops, the menu system does not pop back up as it should and I have to use the task manager to stop the program.

Access violation messages

Similar Messages

Maybe you are looking for