SQLCE dll not found when starting parse

[GoogleCodeExporter]

What steps will reproduce the problem?
1. i downloaded the program
2. unrared it to a folder on my desktop
3. ran KParser.exe

What is the expected output? What do you see instead?
i expected it to start working and parse the file, instead i got an error
about some file not working... here's the error log.

Wednesday, June 11, 2008 12:46 AM
WaywardGamers.KParser.ParserCore, Version=1.0.3025.40898, Culture=neutral,
PublicKeyToken=null
Error severity level: Error

System.IO.FileNotFoundException

System.IO.FileNotFoundException: Could not load file or assembly
'System.Data.SqlServerCe, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system
cannot find the file specified.
File name: 'System.Data.SqlServerCe, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91'
   at WaywardGamers.KParser.DatabaseManager.CreateConnections()
   at WaywardGamers.KParser.DatabaseManager.CreateDatabase(String
newDatabaseFilename)
   at WaywardGamers.KParser.Monitor.Start(String outputFileName)
   at WaywardGamers.KParser.ParserWindow.StartParsing(String outputFileName)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind
failure logging.
To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].

What version of the product are you using? On what operating system?
I am running the newest version that you have on your project home on a
vista 64 system.  i have been having trouble working with all of the direct
parsers tonight (first time i've played in a long time).  

Please provide any additional information below.

Original issue reported on code.google.com by Adal...@gmail.com on 11 Jun 2008 at 4:50

[GoogleCodeExporter]

just woke up and realized that i had made a mistake on the above post.  the 
problem
is not when i run the program, it occurs when i attempt to begin a parse.  
sorry for
the confusion.

Original comment by Adal...@gmail.com on 11 Jun 2008 at 1:16

[GoogleCodeExporter]

Updated summary.

Known workaround: copy System.Data.SqlServerCe.dll from the folder it was 
installed
into (normally C:\Program Files\Microsoft SQL Server Compact 
Edition\v3.5\Desktop) to
KParser's directory.

Original comment by Kinemati...@gmail.com on 11 Aug 2008 at 5:51

• Changed title: SQLCE dll not found when starting parse

[GoogleCodeExporter]

I realized there may be a more fundamental error here.  Make sure SQLCE 3.5 is
installed as specified in the readme.txt file.

Original comment by Kinemati...@gmail.com on 16 Sep 2008 at 3:57

[GoogleCodeExporter]

Tentative issue:

The assembly file System.Data.SqlServerCe.dll -should- be installed into the 
Global
Assembly Cache during the installation of SQLServerCE 3.5.  To check if it 
actually
did, look in the directory C:\Windows\Assembly for the assembly named
System.Data.SqlServerCe.

If it exists, fall back to the previously stated workaround.  If it does not 
appear
to be in the Assembly directory, copy the dll file from C:\Program 
Files\Microsoft
SQL Server Compact Edition\v3.5\Desktop to C:\Windows\Assembly to install the 
service
in the Global Assembly Cache.

Original comment by Kinemati...@gmail.com on 7 Dec 2008 at 11:40

[GoogleCodeExporter]

OK, trying to track down this SQLCE problem, I'm going to need some help from 
those
who are experiencing the bug, or who had the bug and fixed it by copying the 
SQLCE
DLL to the KParser directory (delete said DLL for this test).

On the download page ( http://code.google.com/p/kparser/downloads/list ) I've 
posted
a zip of a log viewing program.  The file name is FUSLOGVW.zip, and it contains
FUSLOGVW.exe (Fusion Log Viewer).  It's part of the Windows SDK, but I figure 
you
don't want to download a 1.3 GB install for just this program.

Run the program and change the Settings as follows:

1) Set it to Log All Binds to Disk.
2) Enable the Custom Log Path and point it at a directory you can find easily. 
(eg:
C:\Temp)

Then run KParser and either try to open a parse or start a new parse, whatever
generates the error.

Once the error is generated, go back to the FUSLOGVW window and hit Refresh.  
You
should now see a bunch of binding attempts in the window.  Look for the one 
where the
Description starts with System.Data.SqlServerCe (please note what version is 
listed
there as well).

Double-clicking that line (or hitting the View Log button) will bring up a web 
page
of the details of the attempt (the actual HTML file is saved in Default\KParser 
under
the directory you specified).  This is the main one I want data on.

In addition, check any other assembly loads to see if any of them say that the
operation was not successful (should be the second line of each log entry).  If 
you
see any of those, include them as well.

Once you have that, please attach the info to this bug (the original HTML file 
from
the log directory is fine).

Also, you can go back to Settings and put it back on Log Disabled.

Hopefully this will help in actually solving this rather annoying problem.

Original comment by Kinemati...@gmail.com on 20 Feb 2009 at 1:08

• Changed state: Accepted

[GoogleCodeExporter]

Made changes to include the required .dlls for SQLCE and modify the app.config 
file
to reference them when run.  Will see if that's sufficient to kill this bug 
once and
for all.

Original comment by Kinemati...@gmail.com on 29 Oct 2009 at 5:21

[GoogleCodeExporter]

As the SQLCE files are now included in the install, this bug shouldn't show up
anymore.  No recent reports of this problem.  Marking fixed.

Original comment by Kinemati...@gmail.com on 18 Dec 2009 at 8:52

• Changed state: Fixed