Tridion 20ll SP1
While Installing CDS at step 'the HTTP Upload server role as a .NET Web site' we are facing various issues.
After following all the steps in the installation guide, we get the error "CS0103: The name 'Tridion' does not exist in the current context" while browsing the httpupload.aspx page.
As per guide, the expected output should be 'SDL Tridion ASPX Upload Page'.
Could you please help?
Check that your Web App contains all of the correct DLLs, and a config folder with the correct configuration XML files, and a lib folder with all the correct JARS. Most likely you are missing some of the Tridion DLLs like Tridion.ContentDelivery.dll.
Related
I am trying to deploy an ASP.NET 5 application to my 64-bit Windows Server 2008 R2 server. I created a blank web application and set up a file system publish profile using dnx-clr-win-x64.1.0.0-beta4. I copied the results from the publish location to a folder on my server and created a new virtual directory with a .NET 4.0 app pool pointing at the wwwroot folder of my application. However, when I try to browse to the site, I get this error:
Could not load file or assembly 'dnx.clr.managed' or one of its
dependencies. The system cannot find the file specified.
Description:
An unhandled exception occurred during the execution of the current
web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details:
System.IO.FileNotFoundException: Could not load file or assembly
'dnx.clr.managed' or one of its dependencies. The system cannot find
the file specified.
The same steps on my local PC (where I have Visual Studio 2015 installed) work correctly so it seems like I need to install something else on my server. I have already installed .NET 4.6 on this server without success. Does anyone know what I am missing?
I found the solution thanks to this question: Azure deployment : Could not load file or assembly 'dnx.clr.managed' or one of its dependencies. The system cannot find the file specified
At first I thought that wasn't the answer because it didn't work when I changed my publish profile from dnx-clr-win-x86.1.0.0-beta4 to dnx-clr-win-x64.1.0.0-beta4. However, I later noticed that approot/packages folder didn't have the x64 package. So I deleted everything and re-published with my new profile and the page loaded.
Change the dependencies file to the current version, whether it is 1.0.0-beta7 or 1.0.0-beta6 ensure that you go to nuget package manager and install the appropriate version rebuild the solution you should see file updates from your output windows.
We are installing SDL Tridion 2011 sp1. After reading installation manual we came accross some queries.
How the incoming folder is created on CDS ? Do we need to create it manually or it will be created by startCDinstaller.bat?
In our case we will be publishing content using http/https so we will follow step 6.4.5 of installation manual. In this step nothing is mentioned about creation of incoming folder.
Is it must to run startCDinstaller.bat so that required assemblies will be registered, and config and Jar files are copied to CDS server ?
Our CDS server architecture is:
Our portal (display site) is configured in the IIS which is pointing to d:\Inetpub\Myportal
HTTPUpload website is configured in the IIS which is pointing to d:\Inetpub\MyHTTPUpload
How the incoming folder is created on CDS ? Do we need to create it manually or it will be created by startCDinstaller.bat?
A : It depends. If your IIS site App Pool user has permissions to create it will create automatically. But, I would recommend you create this manually and provide permissions to the AppPool User.
http://sdllivecontent.sdl.com/LiveContent/content/en-US/SDL_Tridion_2011_SPONE/task_663JDNNNDHDH889595JDJDJD
Configure the IIS user who will be executing the HTTPUpload.aspx Web page to have modify access to the Content Deployer location for incoming content. By default, the IIS user is the identity running the SDL Tridion Application Pool (which typically is the Network Service user).
Is it must to run startCDinstaller.bat so that required assemblies will be registered, and config and Jar files are copied to CDS server ?
A : It is not must to run the startCDinstaller.bat. If you are running as .net Web Application, the dll/jars/config will be simply to be copied under /bin directory.
My personal preference is always configure manually (and most follow the same procedure - universal procedure). Check below documentation for steps to be followed.
http://sdllivecontent.sdl.com/LiveContent/content/en-US/SDL_Tridion_2011_SPONE/task_708AA488429D4457AC303DD121B22183
Please follow Nuno's excellent installer guide here
The HTTPUpload website is your 'Deployer' and the URL of that site you put into the Publish Target. Try hitting it in the browser first.
I did not use the .bat file - Nuno's instructions are all that is needed.
So I am trying to convert the Latest repository from BlogEngine. They are using MVC3. Now I moved all the files, Renamed App_Code-->Set to Compile. Converted all the Files to Web Application. My only problem is I keep getting:
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0103: The name 'Helpers' does not exist in the current context
<div>#Helpers.ExtensionsHelper.GetExtensions(true)</div>
BlogEngine.NET doesn't really use MVC, but it uses Razor web pages that usually installed with MVC 3 or Webmatrix. If you don't have those installed, you need to move DLLs from downloaded lib/Razor folder into application's /bin folder.
I'm receiving the following error when deploying a feature containing ASP.NET pages to our development SharePoint servers:
System.InvalidOperationException: The type specified in the TypeName property of ObjectDataSource 'odsYears' could not be found.
Our .dll is being deployed to the GAC and our pages are being deployed to the the respective Features directory in the 12 hive. We are not receiving this error on our Sandbox SharePoint server. I disassembled the .dll to be sure the class was being deployed and everything looked ok.
Does anyone have any ideas on why this would not work on one of our SharePoint environments?
Thanks.
Found the error, I needed to add a reference to our .dll in the "assemblies" node of the SharePoint web.config file - in case anyone else comes across this.
ObjectDataSource is by default disabled in the SafeControls section of the web.config.
We've implemented some SOAP client code on our ASP.NET site that calls up a remote service. Implementation was basically done by using Visual Studio "Add Web Reference" wizard, adding proper 'using remote.service.namespace' to the code and calling the service.
Code works perfect locally(from Visual Studio), but fails on production web server with missing assembly reference error:
CS0246: The type or namespace name 'remote.service' could not be found (are you missing a using directive or an assembly reference?)
I have a sneaky suspicion that I am not deploying everything properly, maybe some one can point out what is that I am missing there?
Thanks!
Additional info:
Project is a Website.
ASP.NET version 2.0 installed and used as a target on both dev box and production server.
Proxy file generated by WSDL.exe is deployed into the root folder of the website, same folder where the page resides. Global namespace(default) was used for proxy class generation.
If this is a WebSite project, then the proxy file should reside inside the App_Code folder
You mentioned the proxy dll is placed on "the root folder of the web site, where the page resides".
You should place the dll inside the "bin" folder. If the folder is not there create it.
The Web Service client stack in .NET does runtime generation of the proxy client (from the annotations in the class generated by wsdl.exe/svcutil.exe). this generated file typically ends up in one of your servers temp directories (there's one under the main windows tree somewhere). The problem is that the ASP.NET user account doesn't have rights to write to this particular temp directory, but doesn't notice at the time it writes the file, so you end up with an error with it trying to load the generated file back. You can end up in the situation depending on the exact installation order on your server. Once you find the right directory you can simply fix the NTFS perms on the directory to solve the problem.
Did you copy the App_WebReferences folder and all its contents to the server?
Does other parts of your ASP.NET site work?
Does your site target 3.5 and possibly 3.5 is not installed on the production server?
Is this a Web Site, or a Web Application Project? I bet it's a Web Site.