Wednesday, April 24, 2013

How to Resolve QuickBooks Error H202

This error usually occurs when switching a company file to multi-user mode.  To resolve this error, you must add a few exceptions in Windows Firewall on your server for the database server processes.  The two processes you must make exceptions for are:

  • QBDBMrgrN.exe
  • QBCFMonitorService.exe

Wednesday, September 19, 2012

2007 Toyota Tundra P0031 P2195

So my truck's check engine light came on and I hooked up my cheapo code reader and pulled the codes.  The codes I got were P0031 and P2195, which appear to be for the bank 1 sensor 1 air fuel ratio sensor.  The bank 1 side is the same side as cylinder 1 on the engine, which is the driver side on my truck.  Sensor 1 is the sensor between the catalytic converter and the engine.  I got under the truck and easily located the sensor, I was very happy to see that it would be easy to change out.  The part I ordered for my Tundra was a Denso 234-9051 from amazon.com, cost me $115.  I swapped out the sensor, cleared the error codes, and everything seems to be working fine now.

Sunday, August 26, 2012

Visual Studio 2010 and Crystal Reports

Just ran into an issue on my new box while working on a Visual Studio 2010 project.  I needed to add a crystalreportviewer to a windows form, but the crystalreportviewer was missing from the toolbox.  Ok, no problem I should be able to add the item to the toolbox, but when I added went through the add item process, the crystalreportviewer control was still missing from the toolbox.  It turns out that I was using the .net 4.0 client profile in the project properties, once I changed the project properties to .net 4.0 the crystalreportviewer control was in the toolbox and ready to be added to my form.

Monday, August 6, 2012

IIS and Integrated Authentication

I have an ASP .Net application that runs on a Windows Server 2008 R2 machine that uses integrated authentication since all of my workstations are joined to the domain and all the users have domain accounts.  The IIS integrated authentication usually works fine, but every now and then when users try to go to the website, IIS will start prompting everyone for their network credentials and the website will not work even when users enter the correct credentials.  After some trial and error I have discovered that restarting the Windows Process Activation Service on the server where IIS is running will clear up the problem and integrated authentication will start working properly again.

Monday, June 18, 2012

Error formatting query, probably invalid parameters [SQLSTATE 42000] (Error 22050)

Ok, so today I had the bright idea to get my MS SQL Server 2008 to run a stored procedure every night that emails me the results of a query so it would be waiting in my inbox first thing every Monday morning.  I created the stored procedure, created the job for SQL Server Agent to run, and tried running the job.  The job failed?  What?  I manually ran my stored procedure just to make sure it was working and it emailed me the results of the query just like it was supposed to.  I looked at the history of the job and found this error:

Error formatting query, probably invalid parameters [SQLSTATE 42000] (Error 22050).  The step failed.

Now wait a minute, I know my query is good because I just manually ran the stored procedure and it worked, so what is wrong?  It took a minute then it hit me, the domain account that SQL Server Agent uses didn't have permission to access the database.  So, I added the SQL Server Agent account to the database, gave it execute permissions on the stored procedure, and success!  The job now runs successfully on schedule.

Here is what my stored procedure looks like that returns the query results in the body of the email:


EXEC msdb.dbo.sp_send_dbmail
@body = 'The first line of the message body',
@subject = 'This is the subject line',
@profile_name = 'DBMail',
@recipients = 'someone@somewhere.com',
@execute_query_database = 'DatabaseName',
@attach_query_result_as_file = 0,

@query = 'SELECT * FROM TABLE'


Saturday, June 16, 2012

MSDART.dll and MSADOX.dll registration errors

I developed an application years ago using Visual Basic 6 and I needed to install the application on my 64 bit Windows 7 machine this weekend, but I kept getting errors while trying to run the installer. Here are the errors I received:

The procedure entry point RegEnumKeyExI could not be located in the dynamic link library MSDART.dll

and:

An error occurred while registering the file c:\windows\system32\MSADOX.dll

To solve this error, I opened SETUP.LST in a text editor and deleted the line that referenced MSADOX.dll.  I saved the file, ran the installer again and the application installed without any errors.  I launched the application and it ran fine.  


Wednesday, June 6, 2012

SNORT on Ubuntu 12.04

So I have been playing around with my new Ubuntu 12.04 box some more and I decided I wanted to install SNORT on it to do some IDS work. I followed the directions here: https://help.ubuntu.com/community/SnortIDS


but when I tried to launch SNORT using this command:

sudo /etc/init.d/snort start
I would get a fail result.

I looked in the syslog:
sudo tail /var/log/syslog
and discovered SNORT was throwing errors related to the database connection.  There is a file named database.conf in /etc/snort/ that should have been modified to include the database connection information.  The original instructions in the link above instructed me to modify /etc/snort/snort.conf to include the database connection information.  This is wrong, the database information should go in /etc/snort/database.conf.

I edited /etc/snort/database.conf to look like this:
output database: log, mysql, user=<user> password=<password> dbname=<dbname> host=<host>
(replace <user>, <password>, <dbname>, and <host> to your settings)

Once I saved the file, I tried starting SNORT again:
sudo /etc/init.d/snort start
And I got a status of OK!

Now I can let SNORT sniff my network traffic and I can use ACID to view the results.