Dentrix Database Upgrade Problem

[Steven857@]

Good Evening Everyone,

I have been trying to upgrade Dentrix G6.6 to the new G7.1. If I install G7.1 with a blank database, the install goes smoothly. If I upgrade from G6.6, I receive an error saying "Error Creating .\DentrixSQL.dbs\UsrInfo database file.

This is what I've tried in no particular order:

1. Reinstalled Dentrix
2. Restored my database from backup
3. Ran dbsweep utility
4. Reset the Communication files and Workstation ID

Any help with this would be greatly appreciated.

Thanks,
Steven

 

[Markverhyden]

Right click>Run as Admin?

 

[Steven857@]

That’s what I thought originally. I tried running it as an administrator but got the same error

 

[marley1]

Probably some corruption and you need one of Dentrix tools. Gotta wait till AM believe they are closed.

6.6 had all the updates?

 

[Steven857@]

Yes it was totally up to date. My service plan just expired I’m trying to see if I can fix it in my own before paying them a fortune to fix it. Would you happen to know which tool I would need?

 

[YeOldeStonecat]

I don't have the answer....but with medical software, I'd stronnnnnnnnnnnngly recommend you insist your clients keep up their support contract. I'd not want to put my neck across the table working on a medical clients primary LOB app without vendor support.

We get Dentrix support remoted into clients servers..and let them do their thing.

 

[mikeroq]

My service plan just expired I’m trying to see if I can fix it in my own before paying them a fortune to fix it.

Don't you mean the client's service plan?

 

[Steven857@]

That’s what I meant lol. It was a typo. That’s true. I’ll try to get them back on the service plan

 

[marley1]

Henry Schein has a bunch of tools that they keep in their side and transfer as needed.

Dbsweep I find rarely does.

Honestly they charge like 150 for the call. What do you care? Pay for it and add the extra hours into your bill.

No service contract is silly. Dental is cheap, avoid them.

 

[JoeMcDonalds]

Its an SQL Data base error i would suggest you take marley's advice and contact support have them ressolve this on incident bassis and add it to your bill.