web stats
Error after 2.0 Upgrade - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #1  
Old 11-02-2010, 08:06 AM
Meike Meike is offline
Mirth Newb
 
Join Date: Sep 2009
Posts: 15
Meike is on a distinguished road
Unhappy Error after 2.0 Upgrade

Hi everyone,

After upgrading to 2.0 I get the following error everytime I click the channels screen....

Only a few of my channels have been restored.

Can someone suggest what to do now?


org.apache.commons.httpclient.ProtocolException: Unable to parse header: --- The error occurred in derby/derby-channel.xml.
com.mirth.connect.client.core.ServerConnection.exe cutePostMethod(ServerConnection.java:99)
com.mirth.connect.client.core.Client.getChannel(Cl ient.java:179)
com.mirth.connect.client.ui.Frame.retrieveChannels (Frame.java:2119)
com.mirth.connect.client.ui.Frame$16.doInBackgroun d(Frame.java:2084)
com.mirth.connect.client.ui.Frame$16.doInBackgroun d(Frame.java:2081)
javax.swing.SwingWorker$1.call(Unknown Source)
java.util.concurrent.FutureTask$Sync.innerRun(Unkn own Source)
java.util.concurrent.FutureTask.run(Unknown Source)
javax.swing.SwingWorker.run(Unknown Source)
java.util.concurrent.ThreadPoolExecutor$Worker.run Task(Unknown Source)
java.util.concurrent.ThreadPoolExecutor$Worker.run (Unknown Source)
java.lang.Thread.run(Unknown Source)


Thanks in advance!
Meike
Reply With Quote
  #2  
Old 11-02-2010, 09:53 AM
jacobb jacobb is offline
Mirth Employee
 
Join Date: Aug 2006
Location: Irvine, CA
Posts: 1,218
jacobb is an unknown quantity at this point
Default

Try clearing your Java cache:

Control Panel > Java > Settings > Delete Files...

Also make sure you're using Java 1.6.
__________________
Jacob Brauer
Director, Software Development
NextGen Healthcare

Reply With Quote
  #3  
Old 11-02-2010, 12:46 PM
TMarz TMarz is offline
OBX.2 Kenobi
 
Join Date: Jul 2009
Posts: 61
TMarz is on a distinguished road
Unhappy Same Error

I am getting the same error but for postgres which makes sense because that is the db I am using. I tried clearing my java cache but no dice.

Anyone else having this problem?

Code:
org.apache.commons.httpclient.ProtocolException: Unable to parse header: --- The error occurred in postgres/postgres-channel.xml.  
com.mirth.connect.client.core.ServerConnection.executePostMethod(ServerConnection.java:99)
com.mirth.connect.client.core.Client.getChannel(Client.java:179)
com.mirth.connect.client.ui.Frame.retrieveChannels(Frame.java:2119)
com.mirth.connect.client.ui.Frame$16.doInBackground(Frame.java:2084)
com.mirth.connect.client.ui.Frame$16.doInBackground(Frame.java:2081)
javax.swing.SwingWorker$1.call(Unknown Source)
java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
java.util.concurrent.FutureTask.run(Unknown Source)
javax.swing.SwingWorker.run(Unknown Source)
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.Thread.run(Unknown Source)
Reply With Quote
  #4  
Old 11-02-2010, 01:10 PM
jacobb jacobb is offline
Mirth Employee
 
Join Date: Aug 2006
Location: Irvine, CA
Posts: 1,218
jacobb is an unknown quantity at this point
Default

Do you guys have any other errors in your error log before these? If you can identify a specific channel that's causing the problem it would definitely help.
__________________
Jacob Brauer
Director, Software Development
NextGen Healthcare

Reply With Quote
  #5  
Old 11-02-2010, 01:16 PM
jacobb jacobb is offline
Mirth Employee
 
Join Date: Aug 2006
Location: Irvine, CA
Posts: 1,218
jacobb is an unknown quantity at this point
Default

If you can't find any other information or log messages it might help us identify the problem if you sent us an export of your channel table in the database. If you want to email that, you can send it to jacobb@mirthcorp.com
__________________
Jacob Brauer
Director, Software Development
NextGen Healthcare

Reply With Quote
  #6  
Old 11-02-2010, 02:32 PM
TMarz TMarz is offline
OBX.2 Kenobi
 
Join Date: Jul 2009
Posts: 61
TMarz is on a distinguished road
Default More info...

The good news is that I am only testing the upgrade process on a separate server or I would be freaking out.

So I looked all through postgres-channel.xml at the specific part of the ResultsMap where it defines the channels and their attributes. I can find no inconsistencies. The column names all match what is in the db. The error I got in the server log indicated it had a problem with the SOURCE_CONNECTOR column but again I see nothing wrong.

The thing that gets me is that Mirth2.0 can obviously read other tables in the db(person for example, else I wouldn't have been able to log in). I also have no problem with my old code templates which loaded just fine. It seems to just be the channel table.

With this in mind, I truncated the channel table and restarted the mirth service and postgres. No errors at all. I then imported a couple channels (via the Administrator) and they saved successfully. While I am encouraged at this, I know this is not a viable process for upgrading my 300+ facilities.
Even if I wanted to do a mass export of all channels before the upgrade and then re-import them it would be problematic since the shell functionality to export * is broken until 2.0.

Jacob if you still want a copy of my channel table, I can provide it for you in the morning.
Reply With Quote
  #7  
Old 11-02-2010, 03:32 PM
jacobb jacobb is offline
Mirth Employee
 
Join Date: Aug 2006
Location: Irvine, CA
Posts: 1,218
jacobb is an unknown quantity at this point
Default

Send me an export of your 1.8.2 channel table that you are trying to upgrade, or the entire database with a truncated message table.
__________________
Jacob Brauer
Director, Software Development
NextGen Healthcare

Reply With Quote
  #8  
Old 11-03-2010, 02:49 AM
Meike Meike is offline
Mirth Newb
 
Join Date: Sep 2009
Posts: 15
Meike is on a distinguished road
Default

Hi guys,

deleting the Java cache didn't work for me either....

I checked the log and it says something like: error migrating source connectors... (please see attachement).

At the moment I'm evaluating Mirth to be the Integration Solution for our company, maybe with an enhanced Support Contract somewhere in the future or Mirth Training possibilities.
So I'm rather a beginner and have no deeper knowledge about the code, database or xml structure Mirth is using. I have no live environment so far, but tested quite a bit with it.

The problem is that I didn't export all of my channels before upgrading.
If I don't resolve this issue, does that mean I've lost the missing channels?

Any further help would be much appreciated!

Thanks,
Meike
Attached Files
File Type: txt mirth.log.txt (38.3 KB, 6 views)
Reply With Quote
  #9  
Old 11-03-2010, 06:04 AM
Meike Meike is offline
Mirth Newb
 
Join Date: Sep 2009
Posts: 15
Meike is on a distinguished road
Default another question...

I installed this SQuirrel SQL client....

How can I /Can I extraced the channel config xml file out of the database?

Then it should be possible to re-import this file into my Mirth 2.0 install, right?

Should I check anything else in the database?

Thanks,
Meike
Reply With Quote
  #10  
Old 11-03-2010, 10:26 AM
jacobb jacobb is offline
Mirth Employee
 
Join Date: Aug 2006
Location: Irvine, CA
Posts: 1,218
jacobb is an unknown quantity at this point
Default

Meike, your log was very helpful.

Though you should have followed the guide and done a backup of your server configuration, which would include your channels, your channels are still in the database.

Based on your log, it looks like everything worked fine except for selecting certain connectors from the database. Unfortunately, it looks like a database error, so we're looking into what can cause that specific error.

For immediate resolution, you can manually connect to your database, and follow the following logic:
Code:
SELECT ID, SOURCE_CONNECTOR, DESTINATION_CONNECTORS FROM CHANNEL;

Replace all "com.webreach.mirth" with "com.mirth.connect".

UPDATE CHANNEL SET SOURCE_CONNECTOR = ?, DESTINATION_CONNECTORS = ? WHERE ID = ?
(replace ? with the updated source connectors and destination connectors)
We're looking into why this error would have happened in the first place, preventing all of your connectors stored from being migrated. If you could describe the process you followed for upgrading that might help us out.

If we find a bug in Mirth Connect that is causing this issue we'll go ahead and release a script or something that you can run to do this for you, but if you follow the above logic it should resolve your issues now. If the above process is too complicated for you, you will have to wait until we learn more about the issue and can release a script to resolve it.
__________________
Jacob Brauer
Director, Software Development
NextGen Healthcare

Reply With Quote
Reply

Tags
2.0, channel error, upgrade, upgrade issues

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 10:46 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
Mirth Corporation