| Added: November/25/2006 at 2:14pm | IP Logged
|
|
|
I have used ASPPhotogallery for a long time, since the very first version in fact.
The Album stopped working. Not a problem and I just let it ride as I was busy with life, but I need to get it to work now and am having a problem.
There are a ton of other MSAccess database driven web sites on this server, so this is not an issue with MSAccess.
I went ahead and bought and downloaded the Pro Version. I checked for changes as detailed in your conversion document and found that the old databases already had the new changes and all of the picture files had already been renamed. I then remembered that I had already bought the pro version and that it was the upgrade from the old version to the new that initially caused this problem.
The old version has been installed under aspphotogallery, so I installed the new one under gallery. So, this was basically a new install in its own folder.
However, the problem was the same.
When you load the album, its like it freezes up. If you wait long enough (5 minutes plus) it will load the background, but locks the browser up so tight you have to force the workstation down by turning the power off.
This is in Explorer 7.0 or Firefox 2.0. This is the same problem I saw under Explorer 6.0. The server is Windows Server 2000.
I always use the OLEDB connection and you and I had discussed this years ago which resulted in your OLEDB add on :-)
So, I changed the connection string to the OLEDB connection string and received the following error instantly:
"There is not enough storage area for this operation"
This did not make much sense.
I also noted at this point that I could no longer delete the database on the server or renames it as I got a sharing violation. So I rebooted the server.
Once the server was back up everything looked fine. I uploaded the new connection string, checked to make sure it was mapping to the correct database, and tried to load the album home page. Same result. It hangs for a long time, finally loading the background, but locking the browser on the workstation.
This is weird and I thought you might have some answers.
Ken
|