Firstly, I executed the installsqlstate.sql on to my server and then I wrote sessionstate code.
<sessionState mode="SQLServer" sqlConnectionString="data source=idealserver;user id=sa;password=**" cookieless="false" timeout="20" allowCustomSqlDatabase="true"/>
Then I run my web project, it did not work and it returned an error like
Unable to use SQL Server because ASP.NET version 2.0 Session State is not installed on the SQL server. Please install ASP.NET Session State SQL Server version 2.0 or above.
I don't understand the warning and I don't know how I will continue.
It seems that you may have installed the wrong version. Try running installsqlstate.sql located at
system drive\Windows\Microsoft.NET\Framework\version\v2.0.50727
Related
I have attempting to upgrade a web application that uses .NET Framework 4.5 to 4.8.
The application runs on a server that both compiles and runs the application, so I installed the .NET Framework 4.8 Developer Pack. I restarted the server and it has booted up successfully.
TeamCity successfully built and compiled the application and Octopus successfully deployed as per usual. However, when I now attempt to access the website, I get a 404 at the login page.
Looking at the folder structure, the file is definitely there. The code builds and runs successfully on my local machine, allowing me to login and perform any function on the system.
Is there something that I have missed running or doing on the server to get this to work?
Edit: Request for IIS Configuration
The configuration of this hasn't changed since I've upgrade the .NET Framework but here is what I have. If this isn't the configuration that is being asked about, please let me know.
Bindings
Everything else has been left as the default values.
I'm working with IBM MobileFirst 7.1, and trying to get integration for ISAM working. So far I've been working with the sample application provided here, but I'm having issues with it when working with 7.1 MobileFirst client-side tools.
If I download and unzip the v3.5 integration package, and unzip the ISAMforMobileFirst test project, and I build it with the v7.0 CLI, it builds successfully. However, if I build it with the v7.1 CLI, I get an error like this:
Migrating project from version 7.0.0.00.20150211-0917 to version 7.1.0.00.20150807-0630.
[Error:
BUILD FAILED
/Applications/IBM/MobileFirst-CLI-7.1/mobilefirst-cli/node_modules/generator-worklight-server/lib/build.xml:497: com.worklight.upgrader.UpgradeEngineException: FWLPL0019E: Migrating the ISAMforMobileFirst project from version 7.0.0.00.20150211-0917 to version 7.1.0.00.20150807-0630 has failed because Cannot parse /Users/ferriera/Downloads/AmWorklightAdapter-3.5/sample/ISAMforMobileFirst/server/conf/authenticationConfig.xml
at com.worklight.upgrader.WLUpgradeEngine.upgradeProject(WLUpgradeEngine.java:271)
at com.worklight.upgrader.ant.UpgraderTask.execute(UpgraderTask.java:100)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
A colleague also sees this exact error in MobileFirst Studio 7.1 (in Eclipse) so I'm guessing it's not a CLI-specific error.
I would assume that support for something has changed in authenticationConfig.xml in 7.1, and this hasn't been reflected in the migrator.
A few questions:
Is ISAM integration supported in 7.1?
Whilst I realise the sample application isn't technically supported in 7.1, if/since ISAM integration is, in theory it should be feasible to make it work. What's changed in authenticationConfig.xml syntax?
Edit: looks like the failure happens due to the following: <parameter name="embedded-pki-bridge-ca-p12-file-path" value="<file-path>"/> and more specifically: <file-path>.
Change it to the actual file path, and it will not fail importing.
Nothing in the authenticationConfig.xml file is about ISAM really; it's all declarations of realms, login modules, security tests...
There is a clear failure, and a PMR should be opened.
As for a local workaround, I've attempted to remove segments in the file that I thought might trigger it, but did not succeed to find a pattern that causes it...
I am running into a strange problem after deploying my site to AppHarbor.
I always get this error :
Exception Details: System.Data.MetadataException: Schema specified is not valid
It is clearly linked with my connection string (which works perfectly on my dev machine)
<add name="DbEntities" connectionString="metadata=res://*/Models.DbModel.csdl|res://*/Models.DbModel.ssdl|res://*/Models.DbModel.msl;provider=System.Data.SqlClient;provider connection string="Server=xxx.sqlserver.sequelizer.com;Database=xxx;User ID=xxx;Password=xxx;MultipleActiveResultSets=True;App=EntityFramework"" providerName="System.Data.EntityClient" />
I dont use EF code first so I cannot remove the metadata section.
Any idea what to do to fix it ? I couldnt find anything to help me get over this...
For Info I am using VS 2012, .Net 4.0, EF 4.4
The AppHarbor knowledge base has info on using the SQL Server add-on, including setting the metadata-string: http://support.appharbor.com/kb/add-ons/using-sequelizer
Using Websitepanel ver1.1 on my hosting provider and trying to adjust a website (ASP.NET MVC2) to run under .NET 4 integrated pipeline mode.
Every time i apply this setting i get the following error (to be correct: it doesn't matter if i choose 4.0 or 4.0 integrated pipeline):
System.Web.Services.Protocols.SoapException:
Server was unable to process request.
---> Error executing 'UPDATE' task on 'my_website.com' WEB_SITE
---> Server was unable to process request.
---> Object reference not set to an instance of an object.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at WebsitePanel.EnterpriseServer.esWebServers.UpdateWebSite(WebSite site)
at WebsitePanel.Portal.WebSitesEditSite.SaveWebSite()
Is there something I can do about this? Is there something I'm doing wrong? Setting back to .NET 2.0 or 2.0 pipeline works like a charm!
If you are having a VPS, log into the server Try changing the application pool to 4.0 classic instead of 4.0 integrated from IIS manager >> sites >> basic settings. Also make sure that MVC2 is compatible with asp.net 4.
You can edit the corresponding web.config page to change the asp version by changing the corresponding version line to 4 instead of 2.
Please let us know by changing the application pool to 4.0 classic. If you are not having administrator password, Ask your hosting provider support to do this.
Also ask them to check the event viewer logs to know further about the issue.
The main problem is Websitepanel version 1.1
To solve this error, you need to request your hosting provider to upgrade the websitepanel version to 2.0
.NET 4.0 provides better support for aplications, also .NET 2.0 has been deprecated by several web hosting providers.
We developed an web application using visual studio 2008. In my development PC, the application is working fine. In production server I am getting the following exception "ASP.NET AJAX CLIENT FRAMEWORK FAILED TO LOAD". What should I do to make it work?
Thanks,
P.Gopalakrishnan.
I'd start with making sure all of the appropriate service packs are applied and that the 3.5 framework is actually installed on the box.
Also, make sure any assembly you reference that isn't part of your deployment is gac'd on the machine. Check version numbers.
All else being equal, I'd guess the server is just way out of date on it's updates.