We have recently set up new tridion content manager server as well as content delivery server (Tridion 5.3). We are using .net in content delivery.
When we try to publish from content manager we are getting below mentioned error.
Access is denied for the user NT AUTHORITY\SYSTEM: directory services are not enabled.
Can anyone suggest what might be the issue.
We have changed Publishing Target as per new url.
Thanks
I'll take a guess. Have you configured SYSTEM as a directory service impersonation user?
Related
I have trouble with working my site on IIS Server.
I read and tried the recommendations from Stack Overflow and other sites, but without success.
When installing the site on the IIS Server Version 10.0.17134.641 (on the my local computer) the following error occurred:
enter image description here
During development everything all worked fine. And when I try to post a site on local IIS Server, such an error occurred. Home page show normal. But when I try to register or log in have error above.
I'm confused because:
1) The publication took place in the "Folder", on the IIS pointed the way to it.
2) I'm install: Runtime & Hosting Bundle 2.2.3 for ASP.NET Core/.NET Core on Windows from this site: https://dotnet.microsoft.com/download/thank-you/dotnet-runtime-2.2.3-windows-hosting-bundle-installer
And in the module of my site are present: AspNetCoreModule, AspNetCoreModuleV2
3) I'm set "Application Pool" for this site in IIS Server next:
enter image description here
4) I'm "Edit Permissions..." for this site where I added and allow all permissions for next users: IUSR, IIS_IUSRS to "Security"
5) Also turn on next Windows features: enter image description here
Site written on ASP.NET Core MVC 2.2 with Use Entity Framework Core also the same version
With what it can be connected?
With database connection?
Or with configure IIS Server?
Or configure Website?
Thanks:)
SOLVED:
1) I have to add: 'app.UseDeveloperExceptionPage();' in Configure method Startup.cs file my project - It's help to show more details for errors.
2) In Microsoft SQL Server Management Studio need create a new user in Security -> Logins (in the same nesting level as the 'Databases' folder). User must have name like your application pool in IIS Server. In Default database General tab set your using database. And then need to set for user next role: sysadmin in Server Roles
I am trying to deploy an asp.net 4 app to a new microsoft server 2008 R2
I have set up the application as I have done dozens of times before and set the folder permissions appropriately.
I have tried setting the application pool name directly to have write permissions
I have tried setting IUSR, IIS_IUSRS, NETWORK SERVICE and Users.
I have confirmed that windows authentication is disabled and anonymous is enabled as well as forms authentication is enabled. Logging in works fine i can access all pages normally except if i try to write to the folder. Then a password is required box pops up which looks like windows authentication (even though its disabled)
Every post here states and in my past experience says if I set the folder permissions for the defaultidentity application pool it should work, but for some reason this server wont let me do it!
Any help would be most appreciated.
Welp this turns out to be a really weird one. For some reason when SQL reporting services is installed it reserves the folder name "Reports" in any IIS Web application folder regardless of whether your actually using Reporting services. Its not created by default or anything, but if you happen to create folder titled "Reports" dont expect to access anything from it. After many hours of frustration it turns out it's a random reservation which doesn't throw any error just somehow overrides your authentication protocol to use windows authentication for their reserved folder.
Thanks Microsoft!
After upgrade from Tridion 5.3 to Tridion 2011 SP1, when we publish any page it is getting failed with error "You do not have permission to perform this action" Preview of pages is working fine. We tried to check exactly in which stage issue is coming but after double click on failed transaction it just shows the error message under "Publishing Process Details" Tab. I am Administrator in Tridion CMS. Is it related to configuration of cd_deployer_conf or cd_storage_conf.?
It seems that issue is related to user access getting below error message on CME server in cd_Transport.log
An unexpected error occurred while polling: IP:PORT/httpupload.aspx reason: Unauthorized
In event log on CME getting below error :
You do not have permission to perform this action.
Component: Tridion.ContentManager.Publishing
Errorcode: 0
User: NT AUTHORITY\SYSTEM
There is something wrong with your permissions on the HttpUpload app. Make sure that the user it's executing as has permissions to the Content Deployer location for incoming content.
Do this by checking the Application Pool's identity to see what user it is. IIS 7.5 uses ApplicationPoolIdentity as the default user, which is changed from previous versions where the default was NetworkService (here is a little more about that). If you set the app pool's identify back to what you used in 5.3, it should do the trick.
The error suggests that there is a permissions problem for the user(may be NetworkService) writing the files on behalf of the SDL Tridion Content Delivery Deployer.
If you are unsure of which user is writing files on behalf of the SDL Tridion Content Delivery Deployer then you should be able to use a file system monitoring application such as Process Monitor (available from Microsoft TechNet: http://technet.microsoft.com/en-us/sysinternals/bb896645) - please run this, reproduce the issue and then look for 'Access Denied' events.
This should let you know which user is performing the write action - provide this user with access to write to the directory and see if error disappear.
Maybe this will help, according to SDL LiveContent
The new TOM.NET API is still functionally a read-only interface during rendering and publishing. That is, you cannot create, update or delete Content Manager items while your Template is executing. This behaviour also applies to the now deprecated TOM API, meaning that if you have Templates that use the TOM API and perform write actions, these Templates will now fail.
If you do want your old TOM templates to be able to write to the Content Manager, you can configure the Content Manager to allow writing during rendering and publishing. You enable Templates to write to the Content Manager as by opening the Tridion Content Manager configuration file <Tridion.ContentManager.config> (located in the config sub-folder of the Tridion Content Manager root location), and adding an attribute <allowWriteOperationsInTemplates>, set to true, to the element called <tridion.contentmanager.security>.
Source: "Backwards compatibility issues in Content Manager" page on SDL LiveContent
We have an old ASP.NET application hosted in IIS6/Win2k3. It's a document generation application that uploads the documents to SharePoint 2003. The application uses an application pool under the user sharepointservice, which is the administrator of the SharePoint site. The web application, which has been recently migrated to .net 2.0 from 1.1, uses NTLM authentication to identify our intranet users.
As the IT administrators are on holidays, I, the developer, has been given local admin rights to the Win2k3 box. The issue is, whenever I deploy the website, though the documents are uploaded appropriately to the SharePoint site via the application, the users are not able to download them. The error is
HTTP Error 403 - Forbidden: Access is denied
I know the IT guys use a service account, not their domain user accounts.
I have already tried to modify the permissions in IIS for that website. I even put Everyone and <Domain>\Users to have read access to all of those folders, to no avail. I've scoured the net, there are no definitive answers. Am I missing something else?
I hate answering my own question, but this did it for me:
The application pools for the SharePoint site were modified from the default. So I reset them, including the AppPools for _layouts, _vti_bin, and _wpresources. Their AppPools are now the default, and are the same.
This link gave me the lead.
You are probably being prompted by permissions for the file system. Check the directories where IO is happening and make sure the user sharepointservice is using in the app pool has read/write permissions.
I just had this problem and solved it after following these instructions:
http://support.microsoft.com/kb/2543306
It seems the webapplication took so long that it hadn't created everything correctly when the IIS timed out. So I was receiving strange errors like yours.
I've just installed IIS on my machine and tried to create a simple default page site.
On the creation of the project the VS said that it could not configure the server and I sould do it manually.
I opened IIS and "created" the site and gave it a name
I also changed the security tab to allow anonymous access, and the asp.net version to 2.0
when i try to browse to the site i get 403
A 403 means "Forbidden", see here, but this can have different causes...
Maybe ASP.NET is not enabled on your server?
See this for more information...
Is the folder in your My Documents? Try moving it outside there, the stuff in your user profile isn't necessarily accessible to IIS.