an ASP.NET Open Source CMS & eCommerce platform
Search:
Skip Navigation LinksHome > DotShoppingCart Forums > Support > Installation > Problems of Suit 2.5
Last Post 12/22/2008 3:18:29 PM By Bahram. 3 replies.
12/19/2008 3:19:23 PM
Bahram
Posts: 878
Joined: 12/8/2008
Location:Vancouver, BC Canada
Problems of Suit 2.5
 
These are error encountered in V 2.5
 
1- I had a Suite 2.5 installation,. I set the theme as legacy. So when login as admin there was no response and i was not able to enter store section.
 
2- I deleted database and source and recreated from scratch now I see there is two License file in two location - There is error 400 - could not open a connection to database.
Ho can I remove the license key or make them valid.
 
Bahram
 
 
12/19/2008 4:07:27 PM
lukezy
Posts: 2109
Joined: 6/12/2007
Location:WA, US
Re: Problems of Suit 2.5
Could you please remove everything including installation folder, database and encryption file folder? And then install everything from scratch. After installation you won't see the license file until you install the license key.
DotShoppingCart Staff
12/22/2008 1:29:49 PM
Bahram
Posts: 878
Joined: 12/8/2008
Location:Vancouver, BC Canada
Re: Problems of Suit 2.5 still Goes on with new Installaion
 
 
I cleaned anything and installed a new source in new folder and run instDSC with new database name: These are the problems.
1- Runing the website from the server I can login as admon but not enter admin section.
2- I can do the it froma another PC and it message me to install the licence key
3- I can enter admin section from my server by typing ...\Site\Admin after the webname but some of the features wont work (theme selection and logout and I have to close the window
4- Installing License key wont work or no response, But It is done thru the other PC and not the host server.
5-Even after installing Licence, The Admin Enable button and logout Are still not working on the host server.
 
Bahram
12/22/2008 3:18:29 PM
Bahram
Posts: 878
Joined: 12/8/2008
Location:Vancouver, BC Canada
Resolved
The issues resolved. The browser ActiveX setting was the cause.
 
Thanks,