Wrong URLs in Alerts

Example:
AAM:
1. https://x.x.x - public url/default
2. https://x.x.x:8005 - add internal url/default
3. https://servername:8005 - edit public url/Intranet

By adding no 2, several internal features worked, among them add a user,
upload multiple uploads, edit in datasheet etc.
By adding no 3, search and crawl worked.

When an event send out an alert, the url is no 2.... users cannot access
that url..

I presume the siteurl is passed on by sp to alerttemplates.xml.. is it
possible to tell the system to exclude the ":8xxx"? I have several sites, and
I would like to just to this only once..

Mike
Fri Apr 20 10:01:09 CDT 2007

You don't say which version (SPS 2003 or MOSS 2007) you are asking about.

In SPS 2003 the alerts use the address that was being used by the user to
access the site when he/she created the alert.

I don't know from your question is this info is helpful or not ...

Mike Walsh
WSS FAQ http://www.wssfaq.com
No private e-mail please.

"S L" <SL@discussions.microsoft.com> wrote in message
news:BCFEEF59-CC3E-41B4-996D-ABBA5A60C2C3@microsoft.com...
> Example:
> AAM:
> 1. https://x.x.x - public url/default
> 2. https://x.x.x:8005 - add internal url/default
> 3. https://servername:8005 - edit public url/Intranet
>
> By adding no 2, several internal features worked, among them add a user,
> upload multiple uploads, edit in datasheet etc.
> By adding no 3, search and crawl worked.
>
> When an event send out an alert, the url is no 2.... users cannot access
> that url..
>
> I presume the siteurl is passed on by sp to alerttemplates.xml.. is it
> possible to tell the system to exclude the ":8xxx"? I have several sites,
> and
> I would like to just to this only once..

SL
Mon Apr 23 02:14:03 CDT 2007

Sorry, it's MOSS2007.

The user never see the :8005 address, except when I remove the AAM-entry..
then they get an error: "Page cannot be found", and the url refers to the
:8005 address.

It seems like MOSS2007 uses that url internally.. and the system failes to
work properly without it.. but I don't know for sure.. Please tell me if I'm
wrong.

So; how can I force MOSS2007 to use the public address and not the :8005
address?

"Mike Walsh" wrote:

> You don't say which version (SPS 2003 or MOSS 2007) you are asking about.
>
> In SPS 2003 the alerts use the address that was being used by the user to
> access the site when he/she created the alert.
>
> I don't know from your question is this info is helpful or not ...
>
> Mike Walsh
> WSS FAQ http://www.wssfaq.com
> No private e-mail please.
>
> "S L" <SL@discussions.microsoft.com> wrote in message
> news:BCFEEF59-CC3E-41B4-996D-ABBA5A60C2C3@microsoft.com...
> > Example:
> > AAM:
> > 1. https://x.x.x - public url/default
> > 2. https://x.x.x:8005 - add internal url/default
> > 3. https://servername:8005 - edit public url/Intranet
> >
> > By adding no 2, several internal features worked, among them add a user,
> > upload multiple uploads, edit in datasheet etc.
> > By adding no 3, search and crawl worked.
> >
> > When an event send out an alert, the url is no 2.... users cannot access
> > that url..
> >
> > I presume the siteurl is passed on by sp to alerttemplates.xml.. is it
> > possible to tell the system to exclude the ":8xxx"? I have several sites,
> > and
> > I would like to just to this only once..
>
>

SL
Thu Apr 26 02:42:01 CDT 2007

I've done some further investigations, and when an alert is created, some
info is passed on with it - 'username', 'url to the library' and 'how often
alerts shall be sent' (I suppose 'what changes to items' is also passed on to
the db).

Where can I find those entries in the db, and correct the url's? (Note:
Newbie SQL....)

Is there a simple way to get these url's to point at the public address, and
not an internal address?

Mike
Thu Apr 26 09:48:11 CDT 2007

>Where can I find those entries in the db, and correct the url's? (Note:
>Newbie SQL....)

As always here is the standard warning.

- Microsoft strongly recommend against making any changes directly to the
database. (In fact they even go as far as to advise that you don't even read
it directly which to my mind is overkill).
- Microsoft will probably not support your SP system in future if you have
at some stage amended the database directly.
- Problems with such an amendment may become apparent several months later.
- If you have other problems in future you will never know whether these are
caused by your db amendments or not (also other people will be unable to
help you because they won't have the same environment)
- amendments to the database should only be done either via the UI or via
use of the API.

Mike Walsh
WSS MVP
WSS FAQ http://www.wssfaq.com
No private e-mail please.

"S L" <SL@discussions.microsoft.com> wrote in message
news:8857BE9F-258C-4877-97CA-65B6877DA6B6@microsoft.com...
> I've done some further investigations, and when an alert is created, some
> info is passed on with it - 'username', 'url to the library' and 'how
> often
> alerts shall be sent' (I suppose 'what changes to items' is also passed on
> to
> the db).
>
> Where can I find those entries in the db, and correct the url's? (Note:
> Newbie SQL....)
>
> Is there a simple way to get these url's to point at the public address,
> and
> not an internal address?