Erik Geurts

Have you made the corresponding changes to the folder names in the configuration file (to be found in the 'var' folder)?

Have you checked https://www.revive-adserver.com/support/requirements/ and https://www.revive-adserver.com/support/installation/ ?

Please open a new topic for new subjects.

Since Google continue to change their code, click tracking on AdSense tags most likely doesn't work anymore. Since the count of clicks on AdSense tags is their call anyway, there are plans to remove that form of third party click tracking entirely. See also: https://github.com/revive-adserver/revive-adserver/issues/565 Please let us know here or on Github why it would be important for you to be able to count those clicks nevertheless.

Iframe invocation code and companion positioning won't work together since the two iframes are essentially separate and completely independent mini-webpages that aren't "aware" of each other.

No Dutch on these forums, since that would be useless to anyone not able to read the language. Never, ever, post login data on a public forum. It is almost certain your ad system and the server it runs on, has already been compromised and loaded with all sorts of unwanted things. I recommend re-installing the entire server. Meanwhile, you didn't answer the question:

Are you perhaps changing the width and the height of the banner after uploading it into Revive Adserver?

Ok, this isn't helping very much. What was the last version you used that you considered to be 'fast'?

What was your previous version?

I'd laugh too, but it's actually not very funny...

I'm sorry, but without that domain name, it's not something we can investigate.

Based on the information you gave, there's nothing I can do. Please consider posting that test page somewhere and sharing a link with us.

Have you reviewed https://www.revive-adserver.com/faq/troubleshooting-banner-delivery/ ? In particular: are you certain there are banners linked to the zone? And that there is at least one banner of type remnant with no delivery limitations? Also, you say: "get a blank page all the time". This can mean many things: the ad server timing out, or being very slow, or returning a 500 error.

Maintenance is designed to calculate the statistics for the previous hour only. Running at more than once an hour doesn't do anything for the current hour.

Delivery data is logged in so-called 'bkt' (short for bucket) tables during the hour. Logging is by banner by zone. It is about requests (if you've enabled that), impressions, clicks, and conversions. At the top of the new hour, a maintenance process runs that collects that raw delivery data and summarizes it into another set of tables. We recommend using job to trigger the maintenance process (this is called Scheduled maintenance), but if you can't setup a cron job you can also use the substitute (which is called Automatic maintenance), being triggered by a banner being delivered in the new hour. Your database user must have "all privileges" on the database in order to be able to create and delete some temporary tables during the maintenance process. So in short: no, statistics don't appear in real time, but they should update once per hour. More information about your issue may be here: http://documentation.revive-adserver.com/display/DOCS/No+Statistics

I suggest upgrading to the most recent version, which is v3.2.4, first. This may already fix the issue and it will also close several known security issues that you don't want to have open anyway.

Well, that's the setting, and it should work when you change it. If it doesn't, it must be a local thing. One final thing you can try, after setting it to 0, is to clear the content of the /var/cache folder (because the UI's menus and links are also cached there).

Best place to look is in your webserver's access_log.

It looks like you did a new install. In new installs, Direct Selection is disabled by default, in upgrades, it's maintained as it always was. Look in your config file, there is a setting in the [UI] section that controls this. I still don't understand how Direct Selection is going to help fix an issue you have with Flash banners as mentioned in your original post.

Can you post a screen shot of where you think it's supposed to be?

Revive Adserver was first released in September 2013, so ... I've never used Direct Selection myself, so I wouldn't know where to look. Anyway: if you have error messages while logging in/being logged in, I'd think you should fix those first.

Direct selection is definitely still available, but we are considering to deprecate it in a future release: https://github.com/revive-adserver/revive-adserver/issues/588

Probability of the outcome of a calculation (a complex one as you have found out). It can be changed manually. You're trying to fix a symptom, I'd recommend trying to find the cause and correcting that.

I don't agree. In many experiments we've done, MyISAM turned out to be more efficient than InnoDB. I understand about table locking vs row locking, but the test results proved that MyISAM holds its own rather well.

Feel free to call me Erik anytime (the K is important). I have no idea what you mean by 'sharing'. Please elaborate.