search

luboshl / aseisql

Automatically exported from code.google.com/p/aseisql
0 stars 0 forks source link

Application failed to initialize properly (0xc0000005) #79

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
Start application and prompt for "The application failed to initialized
properly (0xc0000005). Click on OK to terminate the application.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
XP SP3

Please provide any additional information below.

Original issue reported on code.google.com by ycho...@gmail.com on 18 May 2010 at 10:15

GoogleCodeExporter commented 9 years ago 
I have the same problem:
1. install client ASE 15.0.2, OS WinXP/SP3,
2. configurated sql.ini, SybaseCentral conected normaly.
3. changed dll libraries with c:\sybase_client_install_folder\OCS-15_0\scripts 
copylibs.bat
5. installed ASEISQL without errors. 
6. Start application ASEISQL nd prompt for "the application failed to 
initialize 
properly (0xc0000005)"

Original comment by roman.ko...@gmail.com on 21 May 2010 at 1:26

GoogleCodeExporter commented 9 years ago 
My problem resolved after doing the following (not sure which one did the work 
actually)
For details, pls refer to http://code.google.com/p/chromium/issues/detail?id=38

1) Back up the registry on an affected system.
2) Open the registry on the Agent system by entering regedit from a run prompt.
3) Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysPlant.
4) Open the Start DWORD.
5) Change the value to 4 to disable the drivers.
6) Reboot the system to commit the changes.

- Goto Run
- Type "regsvr32 /U msimtf.dll"
- Click on OK
Again,
- Goto Run
- Type regsvr32 /U msctf.dll
- Click on OK

Original comment by ycho...@gmail.com on 24 May 2010 at 2:00

GoogleCodeExporter commented 9 years ago 
Greate! Thank You!

1. At first I ran libs without restart - doesn't work
2. Then change "Start DWORD" and reboot - and it works!

I think works the first deсision (Change "Start DWORD") and somehow connected 
with 
Symantec Endpoint...

Original comment by roman.ko...@gmail.com on 24 May 2010 at 9:17

GoogleCodeExporter commented 9 years ago 
Thanks to ycho168 for resolving the problem.

Original comment by daggett....@gmail.com on 25 May 2010 at 5:51