Unable to find sites folder after reboot

[BeamingBaby]

Hi all,

After a PC reboot, Sellerdeck starts with "Error - No sites in Current Directory"
There then follows a convoluted series of steps which I had to log in order to open my sites (we have 5 sites):

1. Click OK
2. Site directory dialog opens, click Browse
3. Navigate through to sites folder and click OK
4. Error window opens "Error ODBC Microsoft . . . failed". Click OK
5. Select database dialog box opens. Navigate through to one of the database.
6. Select ActCatalog.mdb
7. Login dialog opens - click cancel
8. Select DSN datasource dialog opens - click cancel
9. Dialog box opens, asks "Do you want to use existing data?" Click Yes
10 (Here's the clincher!) Enter product key dialog box opens! Re-enter product key code again!

Step 10 means that this has to be available on the desktop in a text file.

We hit upon the above series of steps after numerous other permutations failed!

If Sellerdeck is closed and reopened later, the above doesn't happen - logging in is straighforward. The above steps are only required after a PC reboot.

We have stripped Sellerdeck off the PC completely and performed a reinstall. We've stripped it off and upgraded!

Whilst this problem isn't fatal, it's a real inconvenience.

Any guesses anyone?

[malbro]

Hi all,

After a PC reboot, Sellerdeck starts with "Error - No sites in Current Directory"
There then follows a convoluted series of steps which I had to log in order to open my sites (we have 5 sites):
......

If Sellerdeck is closed and reopened later, the above doesn't happen - logging in is straighforward. The above steps are only required after a PC reboot.

We have stripped Sellerdeck off the PC completely and performed a reinstall. We've stripped it off and upgraded!

Whilst this problem isn't fatal, it's a real inconvenience.

Any guesses anyone?

It looks like you have had a registry failure and have lost the information need to access the site(s) on your machine. Sellerdeck uses ODBC to link to the Access database of the currently open site, the ODBC entry then always points to the database of the last site that was opened. That would be why it works after you have been through the process and then close and restart Sellerdeck.

When you shutdown and restart the PC should then remember those settings so it looks like a operating system problem.

[BeamingBaby]

It looks like you have had a registry failure and have lost the information need to access the site(s) on your machine. Sellerdeck uses ODBC to link to the Access database of the currently open site, the ODBC entry then always points to the database of the last site that was opened. That would be why it works after you have been through the process and then close and restart Sellerdeck.

When you shutdown and restart the PC should then remember those settings so it looks like a operating system problem.

I have noted the ODBC settings and will see if they are reset or changed after a reboot. If so I will assume that, as you say, the ODBC settings aren't being updated to the registry - I will check that too.

[BeamingBaby]

Update.

The ODBC records are fine - no changes to those after a reboot and the problem persists.



Beaming Baby

[chris ashdown]

Could it be a problem with the sites.ini found in the sites folder

[BeamingBaby]

Thank you both for the suggestions.

All users on the network have full permissions on the relevant folder and child folders.

The sites.ini folder is there, yes, and fully populated with data from the sites in the folder.

[NormanRouxel]

Have you tried Windows System Restore? Taking your machine back to a date when it definitely worked may be worthwhile.

Before doing anything, I'd recommend copying the entire Sites folder somewhere safe.

[BeamingBaby]

Have you tried Windows System Restore? Taking your machine back to a date when it definitely worked may be worthwhile.

Before doing anything, I'd recommend copying the entire Sites folder somewhere safe.

Thanks Norman.

This has been considered but the only restore point on the system post dates the installation and as Sellerdeck has been a problem on this PC since day one, there isn't a date when it definitely worked.

I think my only recourse now is to clean Sellerdeck from the machine, clean the HD and do a complex system reinstall. This is not something I relish as it contains the full adobe and office suites, video editing/creating programs, sound editing, rapid application development tools and a host of other programs which demand an attended installation and take forever to install.

Until then I will have to carry on the 10 step startup sequence.

[chris ashdown]

Could you not use another computer to just upload a snapshot on and try it out, at least it would clarify the site side of it

[BeamingBaby]

Could you not use another computer to just upload a snapshot on and try it out, at least it would clarify the site side of it

This is running okay on 4 other pcs on the network with no problem. All snapshot permutations to resolve this issue have been tried. It is most certainly PC related, but I was hoping that the solution would be easier that a complete system re-install such as local settings etc.

[NormanRouxel]

Frankly, I'd abandon that system for a clean one. Your multi-step sequence just to open a site looks like hard work and a mistake there could make things worse.

Another (brave) thing to try would be to install SD on a clean machine with an identical O/S / User / Directory structure as the old. Load one site via a Snapshot to be sure that SD starts and has a known site name. Then copy the entire Sites folder over from the old. Open each site in turn to be sure that works.

Now locate and Export every SellerDeck / 2013 branch from the Registry to a set of files. Delete these branches from the registry on dodgy system. On dodgy system Import registry files to see if that repairs things. It won't fix errors in ODBC branches of the Registry but should clean up any messy SD ones.

I'd also make a backup image the old system first, just in case.

A simpler route on dodgy machine might be to un-install SD, delete any relic registry branches. Then re-install.