New user having install problems on XP

[arun650]

Hello, my wife is a dentist about to start her practice and I thought I'd download and ask her to play with the software. I'm a developer and am still finding the install unintuitive. I can't believe I'm having such a basic issue with the install. I'm not sure if its because my computer has a lot of other stuff installed (Oracle etc).

The problem seems to be with the directory where MySQL. During installation, I left it at the default location:

C:\Program Files\MySQL\MySQL Server 5.5\

However, after MqSQL is installed, I dont see the MySQL directory under c:\program files.

This is the error I see:
----------------
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Program Files\MySQL\MySQL Server 5.5\my.ini'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.Delete(String path)
at FreeDentalInstaller.FormMain.butInstall_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3620 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
OpenDentalInstaller
Assembly Version: 7.8.1.0
Win32 Version: 7.8.1.0
CodeBase: file:///C:/DOCUME~1/arsantha/LOCALS~1/Temp/RarSFX0/Release/OpenDentalInstaller.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3614 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.ServiceProcess
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.



------------------

I'm not sure if I'm doing something obviously wrong. Any help is appreciated.

[wjstarck]

OpenDental database should be under C:\mysql\data. Is it there?

Are you saying MySQL didn't get installed at all (It doesn't look like it)? Maybe the installer got interrupted before MySQL got fully installed. Did you uncheck the configure MySQL server checkbox before it was done (it's not necessary)?

Is there a my.ini file under C:\Program Files\MySQL\MySQL Server 5.5? If so, post the contents of that file. What are the permissions on that file (they probably got munged during the install)?

Did you download and install from the latest installer on the website (should be 11.0.41)?

[arun650]

thanks for the response.

I do see c:\mysql\data.

I don't have c:\program files\mysql

MySQL server 5.5 is available in the list of programs I can uninstall, so its getting installed, but likely not creating the above directory.

I tried this twice, once after uninstalling but no luck. One time I did NOT uncheck the configure MySQL just to see if it helped, it did not.

Also, I'm not sure if OD is getting confused because I see a my.ini under C:\Program Files\Canon\Easy-WebPrint EX with a time stamp of the time I ran the OD install. There are several my*.ini files in the Canon directory and I'm afraid the my.ini has been overwritten by the OD installer.

[wjstarck]

Please post the contents of that my.ini file...

Also, does MySQL show under Services? If so, what does it say when you right click on Properties > General > Path to executable?

[arun650]

Please post the contents of that my.ini file...

Also, does MySQL show under Services? If so, what does it say when you right click on Properties > General > Path to executable?

Yeah, I think the installer is probably to blame. Its clearly doing some flawed checks to see where my.ini exists and making assumptions based on that.

Under services->MySQL->Path, I have "C:\Program Files\Canon\Easy-WebPrint EX\bin\mysqld" --defaults-file="C:\Program Files\Canon\Easy-WebPrint EX\my.ini" MySQL

my.ini contents below:


# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ----------------------------------------------------------------------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
# make sure the server reads the config file use the startup option
# "--defaults-file".
#
# To run run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# To install the server as a Windows service manually, execute this in a
# command line shell, e.g.
# mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# And then execute this in a command line shell to start the server, e.g.
# net start MySQLXY
#
#
# Guildlines for editing this file
# ----------------------------------------------------------------------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]

port=3306

[mysql]

default-character-set=latin1


# SERVER SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
#
[mysqld]

# The TCP/IP Port the MySQL Server will listen on
port=3306


#Path to installation directory. All paths are usually resolved relative to this.
basedir="C:/Program Files/Canon/Easy-WebPrint EX/"

#Path to the database root
datadir="C:/Documents and Settings/All Users/Application Data/MySQL/MySQL Server 5.5/Data/"

# The default character set that will be used when a new schema or table is
# created and no character set is defined
character-set-server=latin1

# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB

# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=100

# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0

# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_cache=256

# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=18M


# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=8

#*** MyISAM Specific options

# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=35M

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=25M

# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K

# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K


#*** INNODB Specific options ***


# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
#skip-innodb

# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=2M

# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1

# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=1M

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=47M

# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=24M

# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=10

[arun650]

Exact same issue on my wife's laptop as well. It has the Canon software installed as well for wireless printing.

Unfortunately, my wife is not getting a good vibe about Open Dental and wants to go with Eaglesoft.

[arun650]

bump

[Rickliftig]

Arun - have your wife review the Dentaltown Forums for Eaglesoft and Open Dental (especially the comments of recent Eaglesoft users who have converted to Open Dental)

Then - bite the bullet and have the Open Dental Staff do a trial install for you (they'll connect through your internet) so that you can have a bug-free installation. (Sometimes our male geek pride gets in the way of expediency )

I can't say enough about how solid Open Dental is and how good the support has been - best of luck in making your decision and best of luck in the New Year.

[jordansparks]

Maybe MySQL installed to C:\Program Files(x86)? Yes, we do installs all day long, so it's easy for us.

[jsalmon]

I've seen this a time or two before but only with computers that have cannon printers...

You should uninstall the current installation of MySQL and then do these steps to correctly install MySQL:
1. Launch the Open Dental Installer
2. Click the Update MySQL button at the top.
3. Copy the MySQL Server path (Ex: C:\Program Files (x86)\MySQL\MySQL Server 5.5\)
4. Click the Install button. (This will start the MySQL installation process)
5. Click next until you see the Choose Setup Type screen with three options of Typical, Custom and Complete.
6. Click on Custom
7. At the bottom of the screen you will see a path that says Location: C:\Program Files... (Yours will most likely have some cannon path here!)
8. Click Browse... now paste the MySQL Server path in the folder name box that we copied in step 3.
9. Then continue as normal with the MySQL installation and you shouldn't get that error once MySQL is finished installing.

[arun650]

Thanks everyone. I called in support and they could not get past the problem.

However, they forwarded my contact information to a developer who actually called me the next day. We had to do a few things (uninstall mysql, reinstall custom, change directory to the right one, since it installs it in the canon dir otherwise).