Geek Answers Handbook

Problem connecting to the Tridion broker database

I'm not quite sure what is happening, but on our site there are several problems that are supported by Tridion 2011 SP1, which I only think is caused by the db broker

1, loading the website results in an error using the environment data module:

[NullReferenceException: the reference to the object is not set to the instance of the object.] Tridion.ContentDelivery.AmbientData.HttpModule.OnRequestStart (sender of the object, EventArgs e) +292 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.ExecutionStep.ExecuteStep.ExecuteStep.Execution +79 System.Web.HttpApplication.ExecuteStep (step IExecutionStep, Boolean, and completed synchronously) +269

2, the audience manager profile is not synchronized between the broker and the subscription management databases, receiving the following errors from the logs:

Error getting synchronization package from view system with URL: [URL] Profilesync.aspx. Message class java.sql.SQLException No data access object for AudienceManagerProfile java.sql.SQLException: no data access object for AudienceManagerProfile

3, Publishing the publication of the website repeatedly fails during the transportation phase, returning: Transport error: failed to transfer tcm_0-10689-66560.Content.zip using HTTPS

I know that this sounds like several problems at once, but my site works until another web publication is added to the project. Since then, we get these errors and would like to think that all this is connected with the problem with brokerage db.

Does anyone come across something like this?

UPDATE: I should also add the fact that dynamic linking also stopped working, which strengthens my faith in the problem of connecting to the broker database or with it.

+4
source share
3 answers

This is full of loaded questions, oh .. boy .. let them take one by one.

You have verified that your license file is valid and has not expired recently.

I would first allow the license file. If not, see below.

First, adding publication publication publication publication has no effect on the CDA site. Therefore, I would completely rule it out.

Secondly, your site works until the publication is added. It cannot be. There should be some changes changed / added to your website. Sometimes updated configurations, but APPPool were not recycled, so you do not see the impact. At a later time, when AppPool is restarted / redesigned, you will notice errors and perhaps give the impression that the site will suddenly break.

  • Have you checked your configs and dll twice?
  • Can you directly connect to your database with a broker user ID / password?
  • Recently, there have been some changes in the firewall, try connecting to the database from CDA Server
+2
source

For # 3, I had the same problem ... is it possible that adding a new publication increased the package size from less than 30 MB to more than 30 MB? If so, check IIS request filtering -> Edit the parameter settings and view the maximum allowable content length. This default value is 30 MB, and for us, increasing this size by something larger than the size of our package solved the problem of the transfer error (since IIS will simply reject our transports due to the size exceeding 30 MB).

+1
source

About Problem # 1: Maybe you have a Tridion.ContentDelivery.AmbientData.HttpModule configured in Web.config but not enough java installation? Do you have cd_ambient_conf.xml in the configuration folder? And cd_ambient.jar in lib?

About issue # 2: you seem to be missing the DAO audience manager (data access objects). Does your cd_storage_conf.xml have the following:

<StorageBindings> <Bundle src="AudienceManagerDAOBundle.xml"/> </StorageBindings>

About issue # 3: is there more information in the cd_transport.log or Windows event viewer?

I agree with Ram that the added publication could not cause this. It looks like your installation on the CD was somehow changed. Have you done an update or something else?

+1
source

More articles:


All Articles