Home Forums Discussions Problems can't connect to imported items

Last Friday we lost electrical power for a couple of hours. When the power came back, AC came back up but we could not direct our computers to the imported folder on the server. This folder has all our scanned items in it. Nor can we import our lab from LabCorp. The lab from Labcorp that we had imported previously is available but the scanned records can't be found. When I go directly on the server, these items are physically present and can be opened (they are both Tiff and PDF files). So why can't the AC program find these files? We are using 4.05 (I think). Any ideas? We called Customer Service and had them stumped. We are going to be turfed to a higher power tomorrow. Dave

We had that problem once.

It started because when the auto back up at the end of the day was done, there was no space (my mistake, I had not deleted old backups). So it hung. We could open the charts but not the imported items.

I deleted old backups. Made some wiggle room for the program to run. Told all the staff to log out.

I had to go to admin utility and run: find missing import utility and follow those 3 steps. Those missing links were restored.

In about 3-5 mins, Bingo all was well.

Thanks for the quick reply. Tried as suggested but doesn't seem to have made a difference. Still can't connect to imported items. Any other ideas? Dave

That's a tough one. I always worried about that with Access. I think I would do it systematically.

First, (which I am sure you have) run Amazing Utilities. When you run Check Amazing Charts under health check, make sure there is an entry for imported items. There should be.

I think if it were I, I would download and install the whole system onto a machine that is not on the network. Then detach and copy the databases and Imported Items to that machine. I would try running the fix corrupt databases. I suppose you could do that right away, but I would hate to screw it up.

It would be interesting to see if you could move to a separate machine, copy Imported Items and attach to it. Another option would be to use a good copy from a backup to connect and then sync with the updated copy. But, that is where I would do everything in a "sandbox."

Are you using an uninterruptible power supply? Is the databases are in use and there is a sudden outage, you can get corrupted databases.

Hi, talked with Dan today. He thinks that the connection between the program and the imported file has been broken and is irretrievable. Our last good back up was last friday. He wants to go back to there, reload and see if the connection can be rebuilt. Problem is we loose 3 days worth of notes from the system. We have printed them and plan to scan or reenter them. But we also loose all info about prescription refills, messages, etc. Not a good situation. I was going to go ahead with the backup plan but have decided to wait and see if you all have any other ideas.

Bert's idea of doing a sync between the two programs sounds interesting. Basically we would have to load everything onto one machine now, then take the server back to last friday with the back up and then synch the two machines? Other ideas?
Thanks Dave

If you want the best idea?

http://www.experts-exchange.com

You can do the six day trial. Ask the question concisely but with enough detail that the experts have it. Put the question under SQL Server 2005. Then wait for the answers. It may be unfixable.

If you do that, and I would highly suggest it, send me the link so I can follow along.

Bert, if I were to copy our current AC with notes, addenda, ekg's current as of today on a different machine than the server, and then do a restore from backup to the server, wouldn't I be able to do a synch between the two versions and get a sum total copy with no loses? I want to avoid losing what we have done this week. Does that seem doable? Dave

That's not a bad thought. I think syncing would be my last resort. And, I wouldn't sync directly to a good copy of the program on the server unless you have a good backup. Even then I would be careful. I would look at it like First Do No Harm.

Try this first. Install a completely fresh copy with SQL Server Express onto a separate machine and run AC there. Then maybe add a few imported items. Make sure everything works. Then make a backup of the one on the server that is up to date but the Imported Items aren't working. Move this .enc file to the new computer or just browse to it. Now using restore from the brand new install, restore the new machine using the backup and overwrite everything. Possibly, just hoping, that by doing this something allows the SQL Server Engine to allow the database to connect to imported items.

2. If this doesn't work, do the above but use an .enc backup from the up to date version on your present server and then add the imported items and run.

If this doesn't work, let me know, and I have my ultimate idea prior to doing any syncing. The sync is a good idea, but I don't completely trust it yet.

Whatever you do, continue to use the program on the server as is and don't import any new items. Just put them into a folder and import them when we fix this.