Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by andrewatfornax

  1. I meant more that the permissions to access the OLD installation were incorrect - the error is stating that it cannot locate the old installation's plugin files, which it needs to do to copy them over to your NEW install (as you may have 3rd party plugins installed).

    If you've specified the correct path, and that is the path to where the OLD installation plugins are, and the files really are there -- then it has to be a permission issue, the new installation's web server configuration is not allowing access to this path.

  2. Hi @Kat,

    With an HTML banner, you can put as many links into a banner as you like.

    However, that's probably not actually what you want. If the customer wants to track impressions, then their banner needs to load a tracking asset which calls back to their system to record the impression. If they customer wants to track clicks, then the hyperlink to their site needs to actually be a link to their click tracking system, which records the click and re-directs the user to their site.

    These, however, are not thing that you should have to worry about. If the client wants these things, they should include them in their banner - normally, you would just deliver their banner as they have created it.

  3. Probably the only way I (or the community) can help is if you can post a clear and complete picture of what you have set up, in detail, and where we can then see the banner(s). The approach of giving us a small amount of information at a time (and not responding to questions that are asked) doesn't help me (or the community) to help you.

  4. HI @firstimpression,

    No, no documentation on this.

    1. You should only have leftovers in the event that data arrives in the tables AFTER the maintenance engine has run to summarise stats for that hour. If you fail to run maintenance for a given hour (or two, or however many), then the next run is supposed to figure out when it was last run, and summarise stats for all the required hours between then and now.

    2. The point that you are running distributed stats is probably the reason you have leftovers - I would guess that central maintenance runs on the hour, but the system to transfer stats from distributed-mode "slaves" (they are not really DB slaves) fails, so the data doesn't arrive in time for central maintenance to see it. That's why you have to use the republish script to deal with the missing data.

    There is no solution to this, but as a suggestion to make it happen less frequently:

    1. Put good monitoring and alerting in place to ensure that the data transfer works; and

    2. Delay when central maintenance runs to give the data transfer process more time to complete.

    If you can, you can even hook #2 up to #1, and only run central maintenance once you know the data transfer is done. But this would have to all be your own custom code.... 

  • Create New...