I would like to enable logging on publishing on a SDL Tridion 2011 SP1 implementation. How do I enable publishing logging, raise/lower the detail level and change the location to a custom location away from the %TRIDION_HOME%?
You must enable Publisher logging in the Tridion MMC snap-in (Publisher settings).
Once this is done, you can control the location, level and details of the logging by editing the file:
\Tridion\bin\TCMPublisher.exe.config
Related
I have a desktop application that makes a call to an asp page on the web server. The web server is currently returning a 500 server error and I cannot figure out how to get more detail.
There doesnt seem to be anything in the Event Viewer: Windows Logs->application.
Is there a setting I can make or another place I can find logs? Seems like this would be a typical issues but I cannot find any information on this.
(Also, the stack trace does not come through to the client application)
You can enable "trace logging" on IIS Manager. It fill create bunch of XML files you can easily investigate using IE installed on the server. (other browsers may fail to process xslt style files)
From Technet:
Open IIS Manager and navigate to the level you want to manage. For information about opening IIS Manager, see IIS 7.0: Open IIS Manager. For information about navigating to locations in the UI, see IIS 7.0: Navigation in IIS Manager.
In the Connections pane, click Sites.
In Features View, select the site for which you want to enable trace logging.
In the Actions pane, under ``Configure, click Failed Request Tracing.
In the Edit Web Site Failed Request Tracing Settings dialog box, select Enable to enable logging for this site.
In the Directory text box, type the path where you want to store the log files or click the browse button (...) to find a location on the computer. The default is %SystemDrive%\inetpub\logs\FailedReqLogFiles.
In the Maximum number of trace files text box, type the maximum number of trace log files that you want to keep, and then click OK.
PS: don't bother IIS 7.0, almost same as IIS 8.x
This should be a comment but comments don't let me add an image.
This is a screenshot of Matt Browne's comment. Upvote his comment if you find this helpful.
If you don't see the "Failed Request Tracing Rules" button, then you need to enable "Tracing" tracing in Server roles.
Here it is:
There is also this configuration that needs to be set:
I had to restart my machine in order for the server configuration to be recognized in IIS.
I have a classic asp application that is very old an d I want to make it work, any help would be appreciated because I don't have much idea on how to do so
Check this threads on stack over flow -
How to guide for getting a classic asp application working under IIS 7.0
How to deploy classic asp website?
OR
check this steps also -
To use the UI on Windows Server 2008 or Server 2008 R2
Click Start, point to Administrative Tools, and then click Server Manager.
In Roles Summary, click Add Roles.
Use the Add Roles Wizard to add the Web Server (IIS) role.
For detailed instructions about how to install a default IIS 7 Web server, see Deploying a Static Content Server (IIS 7).
On the Select Role Services page, note the preselected role services that are installed by default, and then select the following additional role services:
ASP
Request Filtering
ISAPI Extensions
On the Summary of Features to Install page, confirm your selections, and then click Install.
On the Installation Results page, confirm that your installation of the Web Server (IIS) role and required role services completed successfully, and then click Close.
To verify that IIS installed successfully, type the following into a Web browser:
http://localhost
You should see the default IIS 7 Welcome page.
To use the UI on Windows Vista or Windows 7
Click Start, and then click Control Panel.
In Control Panel, click Programs, and then click Turn Windows features on or off.
In the Windows Features dialog box, click Internet Information Services to install the default features, and then select the following additional features:
ASP
Request Filtering
ISAPI Extensions
Click OK to close the Windows Features dialog box.
To verify that IIS installed successfully, type the following into a Web browser:
http://localhost
You should see the default IIS Welcome page.
I'm working on creating a report page for an ASP.NET project, the url to that page is
'localhost/reports'
But for some reason, the SQL Server reporting page is turned on and now there is a url conflict.
So my url now redirects me to the following url:
'localhost/Reports/Pages/Folder.aspx'
It seems the behavior of '/reports' is overwritten by the SQL Report Service site. I would like to know how to turn on/off the db service(report browsing) site manually or by DDL change
You can turn of the entire reporting service in the SQL Server Configuration Manager or you can go to the Reporting Services Configuration Manager and change the Report Manager URL to point to a different location. The default is /Reports.
If you look under "Internet Information Services (IIS) Management", I usually just search for it from start menu, you will see an app pool for reporting services/SSRS with a Reports entry under it. You will probably also see an entry under Default Website. Unfortunately different versions of IIS manager will look different. If you find the "Reports" entry under the Websites/Sites entry, and right click you may have a Properties or Manage Virtual Directory option. Basically IIS handles routing requests to different web applications. So each web application that wants to handle a certain base URL must be configured here. Often times this is done without your knowledge through a deployment or install process, but for more complex setups you might modify IIS directly.
Basically you have a situation where your app and SSRS both have a path in IIS that responds to /reports/. As JodyT answered, the correct solution is to modify the Reporting Manager URL(which likely in turn modifies IIS). I wouldn't be surprised if you had to reboot or run IISReset to get this change picked up. It's hard to say sometimes, but hopefully not.
Change Configuration for SSRS.
Follow these Step:
Open Reporting Services Configuration Manager
Click on Reporting Manager URL
In virtual Directory Change Folder Name 'Reports' to 'Reports2'
Click Apply
Now Check website
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 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?