m2chaudh
asked on
Sharepoint email alerts/notifications for new docs/tickets
Old server was running Sharepoint3.0(same server as where Exchange2007 was running) . New server is running Sharepoint 2010 foundation(seperate DC for Sharepoint). We did migration and everything look like it went over smoothly except that, we have a ticketing system internally, when someone creates a ticket, we should be getting email as notification, but we dont.
I'm new to SharePoint,
This is what I've checked so far for the settings:
-Outgoing email settings: Outbound SMTP server, From address field, Reply-to address, and Character set are all setup correctly, and identical to the old SharePoint 3.0 which hasnt been retired yet but is still working.
-Server in Farm:
Server Services Running Status
__________________________
Exchange2007 Not Configured No Action Required
Exchange2007.company.com " " " " "
HEADOFFICE(new Sharepoint) Sharepoint 2010 Shows all the services are running
Mail.company.com Not Configured No Action required
Since I'm not so familiar with SharePoint, I dont really know how to begin troubleshooting this problem. Can someone help me please? Thanks.
I'm new to SharePoint,
This is what I've checked so far for the settings:
-Outgoing email settings: Outbound SMTP server, From address field, Reply-to address, and Character set are all setup correctly, and identical to the old SharePoint 3.0 which hasnt been retired yet but is still working.
-Server in Farm:
Server Services Running Status
__________________________
Exchange2007 Not Configured No Action Required
Exchange2007.company.com " " " " "
HEADOFFICE(new Sharepoint) Sharepoint 2010 Shows all the services are running
Mail.company.com Not Configured No Action required
Since I'm not so familiar with SharePoint, I dont really know how to begin troubleshooting this problem. Can someone help me please? Thanks.
ASKER
I checked for that folder on foundation but it doesnt exist in inetpub. Whereas it does exist in SharePoint 3.0 server but no files in any folders, all folders are empty inside mailroot\
Sharepoint timer service is running on the SharePoint 2010 foundation server, infact all SharePoint services are running.
This was passed on to me, I didn't do the initial migration. The Sharepoint 3.0 is still the companies fully functional Company website however, Sharepoint 2010 server exists and I'm not sure how to check if migration to new 2010 was even successfull. I cannot browse to it.
I checked IIS and I can only browse to SharePoint central administration but not Sharepoint-80.
Sharepoint timer service is running on the SharePoint 2010 foundation server, infact all SharePoint services are running.
This was passed on to me, I didn't do the initial migration. The Sharepoint 3.0 is still the companies fully functional Company website however, Sharepoint 2010 server exists and I'm not sure how to check if migration to new 2010 was even successfull. I cannot browse to it.
I checked IIS and I can only browse to SharePoint central administration but not Sharepoint-80.
why cant you browse the share point site. do you have a share-point 2010 site then. something that you can see.
may be no alerts are set.
I believe once migrated alerts from 2007 to 2010 they wont work becoz the alert template wont be same.
try creating new alerts in the new site then see if you getting the notifications.
may be no alerts are set.
I believe once migrated alerts from 2007 to 2010 they wont work becoz the alert template wont be same.
try creating new alerts in the new site then see if you getting the notifications.
"Outbound SMTP server" is your Exchange or local smtp server (on SP foundation machine)?
ASKER
Outbound smtp is exchange server.
The Tech who has been working on this for a while, just informed us, the acutal migration had failed...so it wasn't even worth working on this in the first place?
The Tech who has been working on this for a while, just informed us, the acutal migration had failed...so it wasn't even worth working on this in the first place?
it depends on why migration was failed.
It can to fail if only one custom solution is not deployed on new farm if it was on previous. Anyway, you have to search in logs first.
It can to fail if only one custom solution is not deployed on new farm if it was on previous. Anyway, you have to search in logs first.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is what worked and resolved my issue after researching a bit more on Google.
go to the SharePoint server where smtp is installed for.
go to c\Inetpub\Mail root folder there are folders with in it. pickup, queue folders check the contents of each folder if there are the email contents. if there are .eml files then your network is not letting the email out. if there are not them might me SharePoint timer service is not working well...