Office Hours (and maybe Medisoft) Error 6610

Posts related Medisoft software.
Post Reply
FMSEMO
Posts: 11
Joined: Tue Nov 29, 2011 3:29 pm

Office Hours (and maybe Medisoft) Error 6610

Post by FMSEMO » Thu Jun 13, 2013 2:11 pm

I just reinstalled Medisoft Network Professional v17 SP2 on 3 new desktops running Windows 7 (formerly was using XP Pro). Old computers were hard-wired; new are now wireless. Am using a new virus software: Webroot. Office Hours starts and works fine, but later gives many Error 6610 messages (The Advantage Database Server did not respond to a database request in a timely manner...). These particular computers/users typically don't access Medisoft itself. I see suggestions that this is a wireless problem or possibly a virus/firewall setting problem. Any comments that might help me would be appreciated.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: Office Hours (and maybe Medisoft) Error 6610

Post by Gavin Walker » Thu Jun 13, 2013 4:41 pm

Wireless networks are much less reliable than wired networks. Your computer can disconnect from the WIFI for a number of reasons.

1. Interference.
2. Other WIFI networks are in the area and your computers are roaming to try to get the best connection.
3. Only one computer can communicate on a WIFI channel at a time. One of your computers might be hogging all the bandwidth from the other two computers. Most of the cheaper routers cannot divide out the bandwidth evenly between multiple computers. I more expensive wireless router can fix this.
4. Medisoft requires a constant 100mbps connection. A 150mbps WIFI connection is not the same if you have multiple computers. So you might not have enough bandwidth for 3 computers over WIFI.
5. Power saving features of the new computers could be shutting off the WIFI adapter or Windows itself could be going to sleep.
Gavin Walker
Walker Tek Solutions, LLC
417-890-6777 x0
fax: 417-763-6386

aunknown2
Posts: 8
Joined: Sat Nov 09, 2013 4:57 pm

Re: Office Hours (and maybe Medisoft) Error 6610

Post by aunknown2 » Sat Nov 09, 2013 4:59 pm

Conversion began at: 11/9/2013 1:47:13 PM
Converting from version v14 SP1 with conversion version: 17.3.3.437

Version 15 Conversion Log

Updating OHAPP Table had an error.
EADSDatabaseError: cpQryConvert: Error 7200: AQE Error: State = HY000; NativeError = 5070; [iAnywhere Solutions][Advantage SQL][ASA] Error 5070: The given data type is not valid for the requested operation. Not a valid logical value. Restructure failed on record 237.
Alter Table OHAPP
Add Column [Cell Phone] Char(13);

Updating OHAPP table failed.
Updating OHAPP Table had an error.
EADSDatabaseError: cpQryConvert: Error 7200: AQE Error: State = S0000; NativeError = 2121; [iAnywhere Solutions][Advantage SQL Engine]Column not found: Cell Phone -- Location of error in the SQL statement is: 42
Update OHAPP Set [Cell Phone] = '' Where [Cell Phone] IS NULL

Updating OHAPP table failed.

Version 16 Conversion Log


Version 17 Conversion Log

Updating OHApp Table had an error.
EADSDatabaseError: cpQryConvert: Error 7200: AQE Error: State = HY000; NativeError = 5070; [iAnywhere Solutions][Advantage SQL][ASA] Error 5070: The given data type is not valid for the requested operation. Not a valid logical value. Restructure failed on record 237.
Alter table ohapp
Add Column [Service Type Code] char(2);

Updating OHApp table failed.

Version 17 SP3 Conversion Log

Updating OHApp Table had an error.
EADSDatabaseError: cpQryConvert: Error 7200: AQE Error: State = HY000; NativeError = 5070; [iAnywhere Solutions][Advantage SQL][ASA] Error 5070: The given data type is not valid for the requested operation. Not a valid logical value. Restructure failed on record 237. ** Script error information: -- Location of error in the SQL statement is: 116 (line: 3 column: 3)
IF NOT EXISTS (SELECT * FROM system.columns
WHERE (PARENT = 'OHAPP' AND NAME = 'RepeatId')) Then
ALTER TABLE OHAPP
ADD COLUMN RepeatID Integer
ADD COLUMN [End Date] Date
ADD COLUMN Unit Char( 8 )
ADD COLUMN Skips Integer
ADD COLUMN Day Char( 14 );
ENDIF;




Updating OHApp table failed.
Conversion had errors.

aunknown2
Posts: 8
Joined: Sat Nov 09, 2013 4:57 pm

Re: Office Hours (and maybe Medisoft) Error 6610

Post by aunknown2 » Sat Nov 09, 2013 4:59 pm

can some one please help

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: Office Hours (and maybe Medisoft) Error 6610

Post by Gavin Walker » Mon Nov 11, 2013 9:37 am

You have some sort of corruption in your appointment table. Try going back to Medisoft v14 sp1 and purge your old appointment and then upgrade. That might help

Post Reply