Changing default URL for Sharepoint 2010 breaks alert email links...

I changed the sharepoint url from http://{servername} to http://sharepoint/

This broke our email alerts and when lists get updated, no emails get sent out to the "assigned" users.  

If I re-add http://{servername} as an internal url in the alternate access mappings, the emails will then go out, but the link in them are incorrect.  they all point to http://{servername} instead of the new default url I assigned of http://sharepoint.

Any thoughts on what is set wrong and how to fix it?
Who is Participating?
Justin SmithSr. System EngineerCommented:
Ok, you took my response literal.

First line, type . .\invoke-alertfixup.ps1 then press enter
Second line, type invoke-alertfixup -url http://sharepoint -oldurl http://rds then press enter
Justin SmithSr. System EngineerCommented:
You can update URL's in alerts using the Admin Tool kit
ausman89Author Commented:
I couldn't get that to work.

I also tried this: 
It didnt work either.  I created the ps1 file, ran it in the sharepoint shell and immediately ran the next command, but this is the error message I get:

PS C:\Users\administrator.MIDWEST> cd c:/
PS C:\> ./Invoke-AlertFixup.ps1
PS C:\> Invoke-AlertFixup -site http://sharepoint -oldurl http://rds
The term 'Invoke-AlertFixup' is not recognized as the name of a cmdlet, functio
n, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
At line:1 char:18
+ Invoke-AlertFixup <<<<  -site http://sharepoint -oldurl http://rds
    + CategoryInfo          : ObjectNotFound: (Invoke-AlertFixup:String) [], C
    + FullyQualifiedErrorId : CommandNotFoundException

Suggestion [3,General]: The command Invoke-AlertFixup was not found, but does ex
ist in the current location. Windows PowerShell doesn't load commands from the c
urrent location by default. If you trust this command, instead type ".\Invoke-Al
ertFixup". See "get-help about_Command_Precedence" for more details.
PS C:\>
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Justin SmithSr. System EngineerCommented:
I'm assuming you need to dot source the ps1 file.  You do this by running ". .\invoke-alertfixup.ps1", then running your command.

You installed the admin kit and it didn't work?
ausman89Author Commented:
I still cant get the ps1 file to work.

I did install the admin kit.
I tried running the following command and it keeps saying it's invalid:
stsadm -o updatealert -url http://sharepoint -oldurl http://rds

Am I missing something or doing it wrong?  Do I need to restart anything after installing the admin kit?
Justin SmithSr. System EngineerCommented:
the PowerShell commands are what you need to use, as I think the stsadm commands have been removed in 2010.

Can you post a screenshot of your powershelll windows after trying?
ausman89Author Commented:
which command do I want to try again?
Justin SmithSr. System EngineerCommented:
". .\invoke-alertfixup.ps1", then running your invoke-alertfixup command.
ausman89Author Commented:
sharepoint powershell "invoke-alertfixup" error
ausman89Author Commented:
son of a mother duck!
I've done this over and over in 100 different ways, quotes included, excluded, etc. and nothing ever worked...until now.  It worked just now though!!!

I just got an email alert through and the links work!!!  

Thank you so much for fixing my stupidity.
Justin SmithSr. System EngineerCommented:
LOL.  Glad it worked out.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.