Erik Geurts

Try editing your config file in the "var/" folder.
Change :
The part which says "mysql" to "mysqli" at the following section :
 
[database] type=mysql

When a 500 error occurs, Apache (or whatever webserver software you use) will log the cause of that error. I recommend reviewing the error log or discussing this with your hosting provider or sysadmin. Once the cause of the error has been fixed, you should be good to go again.

Have you checked if all the plugins were correctly migrated during the upgrade?

This can be achieved by creating a contract campaign. You can give it a target of X impressions per day (or a total number of Y impressions over the entire lifetime of the campaign. See http://documentation.revive-adserver.com/display/DOCS/Creating+a+Campaign#CreatingaCampaign-Contractcampaigns for more information about contract campaigns or perhaps start at http://documentation.revive-adserver.com/display/DOCS/User+Guide for all available end-user documentation.

Require SSL is just for the ad management UI, it does not affect ad delivery.

Statistics are updated once per hour at the top of the hour.

You only have to put one zone's invocation code on your website. I usually call that the primary zone.
That primary zone delivers a banner with the third party's tag in it. 
If the third party is unable to deliver a paid ad of their own, they will serve your own passback zone's invocation code. And that zone (let's call it the secondary zone) delivers one of your own alternative banners, closing the sequence.
So the secondary zone is not placed directly onto your site, it will appear through the third party's system automatically, if and when needed. 
This setup is also referred to as daisy chaining or waterfall. 

Adding the click macro to the source URL of the iframe means that a click will be counted for every single impression. You should remove that.
The real answer to your question is that clicks inside iframes can not be counted.

Sorry to disappoint you, but since the ad server is completely unaware of what's going on inside the iframe, it is impossible to count clicks on this type of externally hosted banner.

I haven't received anything. I will check the spam folder, if I find your message I will reply.

I would like to suggest having a look at the Advanced Video Ads plugin that you can find here:
http://www.adserverplugins.com/advanced-video-ads-plugin-for-revive-adserver/
 
This plugin will enable you to traffic a third party VAST2 tag (we call this a Network Video Ad) as a banner, and then to serve that into any VAST2 compliant video player.
 
Full disclosure: this product has been developed and is being sold by my company.

I don't think that cookie-based targeting has ever been possible the way you describe it. This is not a standard feature of Revive Adserver, and never has been.
 
One way to achieve this is by means of this third-party plugin named TargetiX:
http://www.adserverplugins.com/retargeting-plugin-for-revive-adserver/
 
Full disclosure: this plugin was developed by me and partner Matteo Beccati and licenses are sold through my company. The proceeds of this type of activity enable us to spend unpaid time on the open source project.

In the dimensions of a zone, you can enter the width or the height (or both) as a * instead of a fixed number. This means the size becomes a wild card.
 
Let's suppose you make a zone of 300 pixels wide and * pixels high. You can then link banners from campaigns, with sizes like 300x250 but also 300x600.

This is a known issue in v3.1.0 which has been fixed in v3.2.0.

You'll have to enter the width and height (mandatory).
 
I would also recommend that you set the click tracking to "do not alter".

That article you linked to is related to DFP. not Revive Adserver.

Revive Adserver v3.2.0 (a beta was released recently) has a new feature: asynchronous javascript tags. See also:
http://www.revive-adserver.com/blog/beta-version-of-revive-adserver-v3-2-0-released/
 
Do note, though, that expanding ads will never be possible, in case of iframes (even friendly iframes).

Hi there,
 
Please start by having a look at this blog post: http://www.revive-adserver.com/blog/can-revive-adserver-support-vast-2-0/
 
Full disclosure, the paid plugin mentioned and linked in that blog post is a product of my company.

Out of the box, Revive Adserver v3.x only supports the VAST1 specifications, and it does not have support for creating pre-roll ads that are essentially using VAST2 tags from third parties.
 
I would like to suggest having a look at the Advanced Video Ads plugin that you can find here:
http://www.adserverplugins.com/advanced-video-ads-plugin-for-revive-adserver/
 
This plugin will enable you to traffic a third party VAST2 tag (we call this a Network Video Ad) as a banner, and then to serve that into any VAST2 compliant video player.

Full disclosure: this product has been developed and is being sold by my company.

You could have a look at this commercial plugin: http://www.adserverplugins.com/in-banner-video-ads-plugin-for-revive-adserver/
Full disclosure, this plugin is developed and sold by my company.

No extra HTML tags or code is added in the AdSense code. All Revive Adserver does is add (after the ad itself) an additional bit of code known as the listener (as described in my previous reply).
Don't worry, thousands of sites have been displaying their AdSense tags via Revive Adserver for more than a decode, and I have never heard of any problems coming from that.

Revive Adserver delivers the Google AdSense code unaltered. All it does is deliver an additional snippet of code to the browser, known as a 'listener' that attempts to recognize that a click has happened on that AdSense ad. Since the code is not altered, there is no reason even even wonder what Google's opinion on that might be.

I don't think this should work any different for the async invocation codes vs the traditional javascript codes. There must have been another reason why it started to work.

If you want to use "is equal to", you need to paste in the full URL, so even the http:// part.
I would recommend using 'contains' however, much easier, and also works on partial URL.

Can you post a screen shot of the delivery options of one of those banners?