Hi .
an issue was brought to my attention from 1 of my clients ....
after an upgrade the users were not receiving any alerts or emails when tasks were being assigned.
ok ..so first port of call being to check and see exactly where things go pear shaped .....
I looked at he exchange event logs and found out that the email message is coming through but with all the wrong email address .... weird ...so a full AD Sync was done and still the issue persists ...
hmmm ..... *scratching my head ...*
then i started looking at the 2007 Plumbing which the upgrade was built on ....
i then found the user list ......and PRESTO ......this is where it was getting all the OLD email values ...
SOLUTION:
Delete the entries in the user list and Re-Sync the AD ... this is what solved my problem .. :)
Regards
Bradley
Thursday, September 15, 2011
Friday, September 9, 2011
Error MOSS MA not found whill creating a Synch Connection string
Hi.
While doing a rountine Health check on a Application sharepoint server ...i noticed that the synchronisation connection that i set up before just DISSAPEARED .... :(
so i tried to create a new connection and got this error ....
so to fix this you RESTART the 2 Forefront Identity Services and then stop and restart the User profile Synchronization service ....
Then just go back to the Synchronization connection and you should see your old connection .... just RUN the Synch Job and you are done ...
Regards
Bradley
While doing a rountine Health check on a Application sharepoint server ...i noticed that the synchronisation connection that i set up before just DISSAPEARED .... :(
so i tried to create a new connection and got this error ....
so to fix this you RESTART the 2 Forefront Identity Services and then stop and restart the User profile Synchronization service ....
Then just go back to the Synchronization connection and you should see your old connection .... just RUN the Synch Job and you are done ...
Regards
Bradley
Wednesday, September 7, 2011
Connect a PerformancePoint scorecard item to an Excel Services report
Hi
this is just for my reference ....
http://technet.microsoft.com/en-us/library/hh393965.aspx ... thanks DARRYL for the link ...
Regards
Bradley
this is just for my reference ....
http://technet.microsoft.com/en-us/library/hh393965.aspx ... thanks DARRYL for the link ...
Regards
Bradley
Friday, August 26, 2011
Assembling Documents on SharePoint 2010 Sites by Merging Content
Hi
nice article i found on merging content when using document sets ....
http://msdn.microsoft.com/en-us/library/ff519529.aspx
Regards
Bradley
nice article i found on merging content when using document sets ....
http://msdn.microsoft.com/en-us/library/ff519529.aspx
Regards
Bradley
Tuesday, August 23, 2011
TechEd 2011 in Durban ICC
Hi.
So who else will be attending this event ...
It will be taking place in Durban 17th till the 20th of October 2011 ...
Here is a link if more information is required ... http://www.teched.co.za/.
Regards
Bradley
So who else will be attending this event ...
It will be taking place in Durban 17th till the 20th of October 2011 ...
Here is a link if more information is required ... http://www.teched.co.za/.
Regards
Bradley
Thursday, August 18, 2011
Getting a "Created By" field and assigning its value to an SPUser object
Hi.
i always have to get the SPUser object and i always forget so i guess i will document it so i can refer back to it .... here goes ..
SPUser spUser = null;
SPFieldUser field = itemEvent.Fields.GetFieldByInternalName("Author") as SPFieldUser;
if (field != null && itemEvent["Author"] != null)
{
SPFieldUserValue fieldValue = field.GetFieldValue(itemEvent["Author"].ToString()) as SPFieldUserValue;
if (fieldValue != null)
{
spUser = fieldValue.User;
}
}
Nice and simple ...and works like a charm ... :)
Bradley
i always have to get the SPUser object and i always forget so i guess i will document it so i can refer back to it .... here goes ..
SPUser spUser = null;
SPFieldUser field = itemEvent.Fields.GetFieldByInternalName("Author") as SPFieldUser;
if (field != null && itemEvent["Author"] != null)
{
SPFieldUserValue fieldValue = field.GetFieldValue(itemEvent["Author"].ToString()) as SPFieldUserValue;
if (fieldValue != null)
{
spUser = fieldValue.User;
}
}
Nice and simple ...and works like a charm ... :)
Bradley
Tuesday, August 16, 2011
A Microsoft SharePoint Foundation compatible application could not be found
Hi.
this has been a nagging issue with a prestine 2010 Upgrade from 2007 ..
some users were getting the error "The Document could not be opened for editing. A Microsoft Sharepoint Foundation compatible application could not be found to Edit the document."
So i searched through all the articles on Google but all of these were for Sharepoint 2007 with office 2007 or earlier, which did not solve my problem ....
So the solution that solved my problem was to enable SharePoint Support features and you do this by going to Control panel => Programs and features => go to the office installation and click "Change" => then change the following feature SharePoint Support features to "Run from my computer".
once this has been done Restart the computer.....
then go to control panel again and run a REPAIR on the office installation......
restart the computer and you should be good to go ....
this is what worked for one of my clients ....
this has been a nagging issue with a prestine 2010 Upgrade from 2007 ..
some users were getting the error "The Document could not be opened for editing. A Microsoft Sharepoint Foundation compatible application could not be found to Edit the document."
So i searched through all the articles on Google but all of these were for Sharepoint 2007 with office 2007 or earlier, which did not solve my problem ....
So the solution that solved my problem was to enable SharePoint Support features and you do this by going to Control panel => Programs and features => go to the office installation and click "Change" => then change the following feature SharePoint Support features to "Run from my computer".
once this has been done Restart the computer.....
then go to control panel again and run a REPAIR on the office installation......
restart the computer and you should be good to go ....
this is what worked for one of my clients ....
Subscribe to:
Posts (Atom)
