|
|
Rank: Member
Joined: 10/5/2008 Posts: 15 Location: Countryside in Switzerland
|
I just installed GalleryServerPro_v2_1_3196 and the installation was successful, but I'm not able to login as a user. I tried the installtion several times and I'm sure the user/password are correct, in the DB is the information correct as well, but I get the error "Your login attempt was not successful. Please try again. " everytime. When I install the Version GalleryServerPro_v2_0_2898 all works.
I'm using a Windows Server 2008 with IIS 7 and all reqirements should be set.
I really would like to use the newest version.
Thanks for any hint.
|
|
Rank: Administration
Joined: 8/3/2007 Posts: 847 Location: Fort Atkinson, WI
|
Are you upgrading an earlier version or are you running the installer as a fresh version?
Are you using SQLite or SQL Server?
Roger Martin Lead Developer for Gallery Server Pro
|
|
Rank: Member
Joined: 10/5/2008 Posts: 15 Location: Countryside in Switzerland
|
Oups sorry forgot to mention. I'm running the installer as a fresh version, no upgrading. I'm using MS SQL Server 2005. Cheers
|
|
Rank: Administration
Joined: 8/3/2007 Posts: 847 Location: Fort Atkinson, WI
|
OK. Do you have another installation of GSP where you might have a saved cookie of your logon info? Go to those (including the demo site) and explicitly log off. Or tell your browser to delete all saved cookies. Or use a browser that you've never logged on to GSP with. Then try the install again. During my testing I would run the installer several times on the same machine. I noticed that I would have the same problem if I ran the installer while I was logged on to another GSP app.
Roger Martin Lead Developer for Gallery Server Pro
|
|
Rank: Member
Joined: 10/5/2008 Posts: 15 Location: Countryside in Switzerland
|
Yes I had another installation of GalleryServerPro_v2_0_2898 on this Server. I removed this installtion, also I removed the DB. After I tried to install the new Version with a new DB.
Now I tried to do the installtion again from another PC from where I never accessed the old version, but the same, still not able to login.
I also tried to do the installation again after deleting all the cookies and other files in releation with the browser, but no success.
|
|
Rank: Administration
Joined: 8/3/2007 Posts: 847 Location: Fort Atkinson, WI
|
It sounds like you are doing all the right things. I just downloaded the latest code and installed as a fresh web application using a fresh SQL Server 2005 database, and I was able to log in just fine. This was with Windows Server 2008 and IIS 7.
I am not sure what else to suggest. If you are able to give me remote access, I would be happy to help troubleshoot.
There is one other thing that can cause this issue, and that is if the applicationName specified for the membership provider in web.config does not match the application name in the aspnet_Applications table. But this really shouldn't be an issue when you are installing to a new database because the name defaults to "Gallery Server Pro" in both places.
As a last resort, provide your web.config file and I'll see if anything jumps out. Just make sure you delete your SQL Server password if it's in there.
Roger Martin Lead Developer for Gallery Server Pro
|
|
Rank: Member
Joined: 10/5/2008 Posts: 15 Location: Countryside in Switzerland
|
I ckecked the applicationName in the web.config and in the aspnet_Application table and it is identical. I provide my web.config file: Quote: <?xml version="1.0" encoding="UTF-8"?> <configuration> <configSections> <sectionGroup name="system.web"> <section name="galleryServerPro" type="GalleryServerPro.Configuration.GalleryServerProConfigSettings, GalleryServerPro.Configuration" allowDefinition="MachineToApplication" restartOnExternalChanges="true" requirePermission="false" /> </sectionGroup> <section name="cachingConfiguration" type="Microsoft.Practices.EnterpriseLibrary.Caching.Configuration.CacheManagerSettings, Microsoft.Practices.EnterpriseLibrary.Caching" requirePermission="false" /> <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"> <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"> <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication" /> <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"> <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="Everywhere" /> <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication" /> <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication" /> </sectionGroup> </sectionGroup> </sectionGroup> </configSections>
<connectionStrings> <clear /> <add name="SQLiteDbConnection" connectionString="Data Source=|DataDirectory|galleryserverpro_data.sqlite;Version=3;" /> <add name="SqlServerDbConnection" connectionString="server=192.168.2.208;uid=GalleryServer;pwd=Password;Trusted_Connection=no;database=GalleryServer;Application Name=Gallery Server Pro" /> </connectionStrings>
<cachingConfiguration defaultCacheManager="Cache Manager"> <cacheManagers> <add expirationPollFrequencyInSeconds="60" maximumElementsInCacheBeforeScavenging="1000" numberToRemoveWhenScavenging="10" backingStoreName="Null Storage" name="Cache Manager" /> </cacheManagers> <backingStores> <add encryptionProviderName="" type="Microsoft.Practices.EnterpriseLibrary.Caching.BackingStoreImplementations.NullBackingStore, Microsoft.Practices.EnterpriseLibrary.Caching" name="Null Storage" /> </backingStores> </cachingConfiguration>
<appSettings />
<system.web>
<pages theme="HelixBlue" styleSheetTheme=""> <controls> <add tagPrefix="CA" namespace="ComponentArt.Web.UI" assembly="ComponentArt.Web.UI" /> <add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> </controls> </pages>
<galleryServerPro configSource="config\galleryserverpro.config" />
<!-- <trust level="Full"/> -->
<globalization uiCulture="auto:en" culture="auto:en-US" />
<xhtmlConformance mode="Strict" />
<compilation debug="false"> <assemblies> <add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" /> <add assembly="System.Web.Extensions.Design, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> </assemblies> </compilation>
<!-- The <authentication> section enables configuration of the security authentication mode used by ASP.NET to identify an incoming user. The timeout is set to 129,600 minutes by default, which is 90 days. This allows the user to be automatically logged in (requires selecting the "Remember Me" checkbox during login which sets a persistent cookie). Note that when the user clicks "Log out", the persistent cookie is removed and the user will have to log in next time. --> <authentication mode="Forms"> <forms loginUrl="login.aspx" defaultUrl="default.aspx" protection="All" timeout="129600" slidingExpiration="true" /> </authentication>
<authorization> <!-- <deny users="?" />--> </authorization>
<!-- Configure the Membership provider.--> <membership defaultProvider="SQLiteMembershipProvider"> <providers> <clear /> <add applicationName="Gallery Server Pro" passwordFormat="Clear" minRequiredNonalphanumericCharacters="0" minRequiredPasswordLength="2" maxInvalidPasswordAttempts="50" enablePasswordReset="true" enablePasswordRetrieval="true" passwordAttemptWindow="10" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" connectionStringName="SQLiteDbConnection" name="SQLiteMembershipProvider" type="GalleryServerPro.Data.SQLite.SQLiteMembershipProvider" /> <add applicationName="Gallery Server Pro" passwordFormat="Clear" minRequiredNonalphanumericCharacters="0" minRequiredPasswordLength="2" maxInvalidPasswordAttempts="50" enablePasswordReset="true" enablePasswordRetrieval="true" passwordAttemptWindow="10" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" connectionStringName="SqlServerDbConnection" name="SqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" /> </providers> </membership>
<!-- Configure the Role provider.--> <roleManager enabled="true" cacheRolesInCookie="true" cookieProtection="Validation" defaultProvider="SQLiteRoleProvider"> <providers> <clear /> <add applicationName="Gallery Server Pro" connectionStringName="SQLiteDbConnection" name="SQLiteRoleProvider" type="GalleryServerPro.Data.SQLite.SQLiteRoleProvider" /> <add applicationName="Gallery Server Pro" connectionStringName="SqlServerDbConnection" name="SqlRoleProvider" type="System.Web.Security.SqlRoleProvider" /> </providers> </roleManager>
<!-- Configure the Profile provider.--> <profile defaultProvider="SQLiteProfileProvider"> <providers> <clear /> <add applicationName="Gallery Server Pro" connectionStringName="SQLiteDbConnection" name="SQLiteProfileProvider" type="GalleryServerPro.Data.SQLite.SQLiteProfileProvider" /> <add applicationName="Gallery Server Pro" connectionStringName="SqlServerDbConnection" name="SqlProfileProvider" type="System.Web.Profile.SqlProfileProvider" /> </providers> <properties> <add name="ShowMediaObjectMetadata" defaultValue="false" type="String" allowAnonymous="true" /> </properties> </profile>
<anonymousIdentification enabled="true" />
<httpHandlers> <remove verb="*" path="*.asmx" /> <add verb="*" path="ComponentArtUploadProgress.axd" type="ComponentArt.Web.UI.UploadProgressHandler, ComponentArt.Web.UI" /> <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> <add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="false" /> </httpHandlers>
<httpModules> <add name="ComponentArtUploadModule" type="ComponentArt.Web.UI.UploadModule, ComponentArt.Web.UI" /> <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> </httpModules>
<sessionState mode="InProc" timeout="60" />
<!-- The <customErrors> section enables configuration of what to do if/when an unhandled error occurs. The mode attribute must be one of these values: Off (No redirection is performed; all users get detailed error message), On (all users are redirected to friendly error page), RemoteOnly (local users see detailed error message, remote users are redirected) --> <customErrors mode="RemoteOnly" defaultRedirect="error/error.aspx"> <error statusCode="403" redirect="error/error_404.aspx" /> <error statusCode="404" redirect="error/error_404.aspx" /> </customErrors>
<!-- Enable / disable tracing. --> <trace enabled="false" pageOutput="false" localOnly="false" mostRecent="true" writeToDiagnosticsTrace="false" requestLimit="200" />
<!-- Gallery Server 1.x had the home page at index.aspx, so provide automatic redirection if users had a bookmark to the old location. --> <urlMappings enabled="true"> <add url="~/index.aspx" mappedUrl="~/default.aspx" /> </urlMappings>
</system.web>
<!-- The maxRequestLength attribute specifies the maximum upload size (KB). To prevent requests larger than 2 GBytes, use maxRequestLength="2097151" The executionTimeout attribute specifies the maximum number of seconds a request is allowed to execute before being automatically shut down by ASP.NET. For 8 hours, use executionTimeout="28800". --> <location path="task/addobjects.aspx"> <system.web> <httpRuntime maxRequestLength="2097151" executionTimeout="28800" /> </system.web> </location>
<location path="task/synchronize.aspx"> <system.web> <httpRuntime executionTimeout="86400" /> </system.web> </location>
<location path="task/transferobject.aspx"> <system.web> <httpRuntime executionTimeout="3600" /> </system.web> </location>
<location path="admin/backup-restore.aspx"> <system.web> <httpRuntime executionTimeout="3600" /> </system.web> </location>
<system.diagnostics> <switches> <!--0 = Off, 1 = Error, 2 = Warning, 3 = Info, 4 = Verbose --> <add name="TraceLevelSwitch" value="0" /> </switches> <trace autoflush="true" indentsize="2"> <listeners> <!-- <add name="WebPageTraceListener" type="System.Web.WebPageTraceListener, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/> <clear/> Use clear in non-Full trust environments, or delete tracing altogeter --> </listeners> </trace> </system.diagnostics>
<system.web.extensions> <scripting> <webServices> <profileService enabled="true" readAccessProperties="ShowMediaObjectMetadata" writeAccessProperties="ShowMediaObjectMetadata" /> <jsonSerialization maxJsonLength="2147483647" /> </webServices>
<scriptResourceHandler enableCompression="true" enableCaching="true" /> </scripting> </system.web.extensions>
<system.webServer> <!-- By default IIS 7 restricts uploads larger than about 30 MB. To allow larger uploads, use the <requestFiltering> element to set a new value. The attribute maxAllowedContentLength is in bytes, so to set a new value of 2 GB, use 2147483648 (2 * 1024 * 1024 * 1024). Note: If you get an error that requestFiltering cannot be overriden you must edit %windir%\System32\inetsrv\config\applicationHost.config file and change the string: <section name="requestFiltering" overrideModeDefault="Deny" /> to: <section name="requestFiltering" overrideModeDefault="Allow" />
<security> <requestFiltering> <requestLimits maxAllowedContentLength="2147483648"/> </requestFiltering> </security> --> <validation validateIntegratedModeConfiguration="false" /> <modules> <remove name="ScriptModule" /> <add name="ComponentArtUploadModule" type="ComponentArt.Web.UI.UploadModule, ComponentArt.Web.UI" /> <add name="ScriptModule" preCondition="integratedMode" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> </modules> <handlers> <remove name="WebServiceHandlerFactory-Integrated"/> <remove name="ScriptHandlerFactory" /> <remove name="ScriptHandlerFactoryAppServices" /> <remove name="ScriptResource" /> <add name="ComponentArtUpload" verb="*" path="ComponentArtUploadProgress.axd" type="ComponentArt.Web.UI.UploadProgressHandler, ComponentArt.Web.UI" /> <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> <add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> <add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> </handlers> <defaultDocument> <files> <clear /> <add value="default.aspx" /> </files> </defaultDocument> </system.webServer> </configuration>
Thanks a lot for your time :-)
|
|
Rank: Administration
Joined: 8/3/2007 Posts: 847 Location: Fort Atkinson, WI
|
OK, I see a problem. Web.config is telling GSP to use SQLite for the membership, roles, and profile providers. Change these to the SQL Server versions: Code:<membership defaultProvider="SqlMembershipProvider">
...
<roleManager enabled="true" cacheRolesInCookie="true" cookieProtection="Validation" defaultProvider="SqlRoleProvider">
...
<profile defaultProvider="SqlProfileProvider"> You better go into ~/config/galleryserverpro.config and check the data provider there, too. Scroll to the end and make sure it specifies SQL Server: <dataProvider defaultProvider="SqlServerGalleryServerProProvider"> The installer *should* have updated these, but it appears it may not have in your case. If you confirm this was the issue, I'll dig into the code to look for a bug.
Roger Martin Lead Developer for Gallery Server Pro
|
|
Rank: Member
Joined: 10/5/2008 Posts: 15 Location: Countryside in Switzerland
|
Yep that did the trick . . . now it works. :-)
I just corrected the web.config file. The galleryserverpro.config file was OK.
Thank you very much.
Greetings from Switzerland.
|
|
Rank: Administration
Joined: 8/3/2007 Posts: 847 Location: Fort Atkinson, WI
|
Excellent! My guess is that the Network Service account does not have modify permission to the directory containing the web.config file and it failed silently instead of alerting you to the issue. I will look at the code and fix it.
Roger Martin Lead Developer for Gallery Server Pro
|
|
Rank: Member
Joined: 10/5/2008 Posts: 15 Location: Countryside in Switzerland
|
Yep the Network Service account didn't have modify permission and the setup routine informed me to add the connectionstring manually, but didn't mentioned the other parameters. thx
|
|
Rank: Administration
Joined: 8/3/2007 Posts: 847 Location: Fort Atkinson, WI
|
I identified the bug and fixed it. It will be in the next release.
Thanks for reporting it!
Roger Martin Lead Developer for Gallery Server Pro
|
|
Rank: Member
Joined: 10/5/2008 Posts: 15 Location: Countryside in Switzerland
|
cool . . . no prob
thx
|
|
Rank: Member
Joined: 11/1/2007 Posts: 12 Location: US
|
I get the following after installing (extracting files) on a Windows Server 2008 x64. There doesn ot appear to be any instruction for configuring IIS 7.0.
Server Error in '/' Application.
Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>
Please advise, Niles
|
|
Rank: Member
Joined: 11/1/2007 Posts: 12 Location: US
|
Never mind. I just figured it out. I needed to convert to application in IIS 7.0
Thanks, Niles
|
|
|
Guest |