2 Problems after migration Project Server 2007 to 2010

Hi Everyone!!
I have 2 issues after migrate MS Project Server 2007 to Project Server 2010, in fact i had a lot issues, but i can solve almost all, so after solve all issues, just is pendings 2 issues very rare:
Backgrounds:
Migrated from: Windows Server 2008R2 - SQL Server 2008 R2 - Proejct Server 2007 with WSS 3.0 - All updates are up to date (CU is up to date) and all platform is ok
To: Windows Server 2008R2 - SQL Server 2008 R2 - Project Server 2010 SP2 - SharePoint Server 2010 SP2 - All updates are up to date (CU is up to date) and all platform is ok
3 Servers in the Farm, ----> 1WFE-1WAPP-1DB
Issues:
In the Project Center, some migrate Project don't show the icon with image about project documents, risk and issues although that project effectively have documents , risk and issues
In "Server Settings" , in section "Operational Policies" in "Project Sites" almost all projects don't show the URL with Project Site
For the issues 1 and 2, i tried some things:
Re publish all projects (approx 700 projects) with a script via PowerShell available in technet
Run the Wizard Again
Rebuild Solution
Restart the all Servers in the Farm
Restart Services ----> IIS - Project EventService - ProjectQueue - SharePoint Timer
and i can't solve it yet!!!
Please Any Ideas?
Erick Gutiérrez PMI Membership #ID 2089740 MTCS - Microsoft Project Server Managing Projects

Have you restored content DB successfully?
for point 2 have you performed:
have you synchronized project site under server setting --> operational policies --> Bulk Update Project
Sites
http://pwmather.wordpress.com/2012/10/08/projectserver-2010-bulk-update-project-site-issue-ps2010-msproject-sp2010-sharepoint/
after doing this publish all the project which are having issue it may solve your 1st issue.
You can check if below condition is applies to you (PWA 2007)
You may need to use the WSS site re-linker tool –
now built in to Server Settings in PWA as “Bulk Update Project Sites”. If you have changed URL die to a different port then re-linking should get your sites in order. In upgrade scenarios the “Previous Site Path” Web application might show as a GUID
in the drop down – however it still works and will re-link the sites.
http://technet.microsoft.com/en-us/library/cc197498(v=office.12).aspx
kirtesh

Similar Messages

Problem after installation Project Server 2013 CU September 9, 2014

Dear All,
I have some problems after installation
Project Server 2013 CU September 9, 2014 (Hotfix 2883072) on 3 level farm
Before installing CU, I have installed
SP1 for Project Server 2013, installation and configuration was successful.
Then I have installed CU and I have not get any errors during installation process. Then I have restarted servers and in SharePoint health analyzer got an error about patch/installation status
on WFE server.
I checked in Windows installed updates and hotfix is installed. I checked in SharePoint Update and Upgrade history and there were no errors during installation. But when I checked in Manage
Patch Status list I found an information:
Language Pack for SharePoint and Project Server 2013 - Russian
Microsoft Project Server Russian Language Pack 15.0.4420.1017 Installed
Hotfix for Microsoft Project Server 2013 (KB2883072) 64-Bit Edition
15.0.4649.1001 Missing/Required
Microsoft Project Server 2013
Microsoft Project Server English Language Pack 15.0.4571.1502 Installed
Hotfix for Microsoft Project Server 2013 (KB2883072) 64-Bit Edition
15.0.4649.1001 Missing/Required
Service Pack 1 for Microsoft Project Server 2013 (KB2880553) 64-Bit Edition
15.0.4571.1502 Installed
Microsoft Project Server Web Front End Server
15.0.4571.1502 Installed
Hotfix for Microsoft Project Server 2013 (KB2883072) 64-Bit Edition
15.0.4649.1001 Missing/Required
Service Pack 1 for Microsoft Project Server 2013 (KB2880553) 64-Bit Edition
15.0.4571.1502 Installed
If I run installation again I get message that nothing will be updated - no update needed.
Please help, how I can install missed packages?

The problem was solved !
I solve it using two ways:
1. I have installed the hotfix for Project Server - Hotfix for Project Server 2013 October 14, 2014 KB 2889959 (Projectserverwfe-x-none.msp, Projectservermui-Language-Code.msp)
2. using command
Psconfig -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures -cmd installcheck -noinstallcheck
After two actions I was able to run SharePoint Configuration Wizard and upgrade database. Configuration completed successful.

Steps to migrate Project Server 2007 from SQL Server 2005 to SQL Server 2008?

We need to migrate Project server 2007 from SQL Server 2005 to SQL Server 2008.
1. Is it as simple as doing backup and restore of databases and pointing Project Server to the new DB server? Or there are some specific steps that should be followed?
2. Article at
http://technet.microsoft.com/en-us/library/dd207290(office.12).aspx is about moving databases from one DB server to another (same versions). At one place, it mentions to
backup all databases but at another place it mentions that
You should only back up the Draft and Published databases from the source database server.
What should be done when moving from 2005 to 2008?
Regards,
Amit
Gupta

High Level step you can get this form Tech net or MSDN too
Shut down the SharePoint servers (App / Web)
backup all of the SharePoint and Project
Server databases from the SQL 2005 server
copy these over to the new SQL 2008 server and restore all of
the databases with the same names
script out all of the logins used by SharePoint/PS from the SQL 2005 server and create these on the SQL 2008 server
script out the Delete expired sessions SQL job from the SQL 2005 server and create this on the SQL 2008 server - or create them manually on the SQL 2008 server
repoint the SQL server DNS Alias from the SQL 2005 server to the SQL 2008 server, if SharePoint and Project Server was installed using the actual SQL server name and no alias, you can create a DNS alias for the old SQL 2005 server name that points to the SQL
2008 server. This is so that the SharePoint servers can still connect to the same SQL server name
Start up the SharePoint servers
kirtesh

Migrating Exchagne Server 2007 to 2010 DAG....

Hi,
One of my customer request to migrate their existing Exchange server 2007 to a latest version. They are currently using Office 2003 package so I think we can only migrate to Exchange server 2010 due to compatibility issue of Office Outlook with Exchange 2013.
We need to implement DAG solution with 2 server and I know that I can install Exchange Server 2010 SP3 over Windows Server 2012 stranded edition. We hope to implement one server in the Head office and the other server is gong to be fixed in DR site that
connects the Head Office via a IPSec VPN tunnel.
We have several ADs. 3 in Head Office, One in remote site and one in DR site.
HO-Primary AD   :   Windows server 2003 R2 32bit    Standard    :   Schema,Domain,RID,PDC,Infra and a GC
HO-DC01       :   Windows server 2008 R2 64bit Standard    :   GC
HO-ADC       :   Windows server 2008 R2 64bit Standard    :   GC
ROADC       :   Windows server 2008 R2 64bit Standard    :   DC
DR-ADC       :   Windows server 2008 R2 64bit Standard    :   DC. Will change to GC when installing DAG
Domain Functional Level   :   Windows server 2003
Forest Functional Level   :   Windows server 2003
Current Exchange 2007 setup has only one server with Hub,Mail and CAS role installed. Also there is a Edge transport role installed in the perimeter network.
We are planning to purchase 2 brand new servers for Exchange DAG and hope to retire the old server after migrating completed My concern is that I've never done a Exchange Migration in this type of a setup where mix server OS and lower Functional level exists.
It would be great if you could let me know what should i look before planning this migration.
Are there any known issues of the current setup I need to be aware of while migrating?
Is there a complete guide available that I can refer?
Please be kind enough to support me to find accurate information to plan and execute this migration.
Thanks in advance.
Tharaka

Hi Tharaka,
In addition to Steve's suggestion, I would like to clarify the following thing:
When you migrate Exchange 2007 to Exchange 2010, you need to stand up the new environment, create a 'legacy' name space (or rename 'owa' is an option), and then move mailboxes to the new environment.
Here is a thread about migration from Exchange 2007 to Exchange 2010 for your reference.
migration of exchange server 2007 to 2010
http://social.technet.microsoft.com/Forums/en-US/0d0d031d-46ed-4806-ada5-6590346caa74/migration-of-exchange-server-2007-to-2010?forum=exchangesvrdeploylegacy
What's more, about Exchange 2010 DAG, here are some helpful threads for your reference.
Database Availability Group Design Examples
http://technet.microsoft.com/en-us/library/dd979781(v=exchg.141).aspx
Understanding Database Availability Groups
http://technet.microsoft.com/en-us/library/dd979799(v=exchg.141).aspx
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Project Server Error Event ID 6971 when upgrading from Project Server 2007 to 2010.

Hi All,
I get the following error when trying to import a project server site from PS 2007 to PS 2010. The error occurs after the provisioning is completed. The initial error with event id 7381 is:
"ProjectSite post provision setup completed with errors"
This error is followed by Event Id 6971 and the following error text. I checked the site and I do see the sub sites under the main project server site, but the actual PWA site is not created and integrated with the project server components. The
database upgrade of all the 4 Project Server databases went through ok. I am not sure how to fix this problem. Any help that you guys can provide is great appreciated.
Failed to provision site "Testsite "with error: Microsoft.Office.Project.Server.Administration.ProvisionException: Membership synchronization failed. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request)
at Microsoft.SharePoint.SPWeb.InitializeSPRequest()
at Microsoft.SharePoint.SPWeb.InitWebPublic()
at Microsoft.SharePoint.SPWeb.get_Language()
at Microsoft.Office.Project.Server.BusinessLayer.SharePointSecurityHelper.DeleteRoles(SPWeb web)
at Microsoft.Office.Project.Server.BusinessLayer.SharePointSecurityHelper.ConfigureDefaultPWAWSSSecurityModel(SPSite topSite, SPWeb web)
at Microsoft.Office.Project.Server.BusinessLayer.Admin.<>c__DisplayClass18.<QueueUpdateUsersAddRemoveStatusOnPwaRootsAndWorkspaces>b__17()
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2()
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.Office.Project.Server.BusinessLayer.Admin.QueueUpdateUsersAddRemoveStatusOnPwaRootsAndWorkspaces(Dictionary`2 deletedUserUidsLoginNames, Guid[] addedUserUids, Boolean isFullSync, Boolean syncWorkspaces)
at Microsoft.Office.Project.Server.BusinessLayer.Admin.SynchronizeMembershipForPwaAppRootSite()
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.SynchronizePwaMembership(ProjectProvisionSettings provset, ProjectSite projectSite)
--- End of inner exception stack trace ---
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.SynchronizePwaMembership(ProjectProvisionSettings provset, ProjectSite projectSite)
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)
Thanks,
Anand.

Hi Anand,
Thanks for the info.
Basic rule for DB attach method is, we should not change Project Web Application site collection name. E.g of old site was /PWA , when we move databases from one farm to another site should
be provisioned as /PWA. Brian Smith's excellent blog article can help you to understand common issues
As per the error message posted earlier, looks like you are trying to provision PWA site as “Testsite”
Correct me if I am wrong
http://blogs.msdn.com/b/brismith/archive/2011/02/07/project-server-2010-common-project-web-app-pwa-provisioning-problems.aspx
Verify that you are not using one of the reserved outline code or custom field
http://technet.microsoft.com/en-us/library/ee662500.aspx
Custom field and lookup table name conflicts
Hrishi Deshpande – Senior Consultant DeltaBahn
Blog | < |
LinkedIn
Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you.This can be beneficial to other community members reading the thread.

Mailflow Problem After Migrating Mailbox From 2007 to 2013

I thought I was at the point of migrating our mailboxes from 2007 to 2013. I had created a new test mailbox on the 2013 server and changed all the DNS and virtual directories for the legacy on the 2007 server and was able to successfully send mail
to the test mailbox out and in both internally and externally. Then I migrated my first mailbox from 2007 to 2013 and things went south.
I CAN NOT:
Send e-mail from a mailbox on the 2007 server to the migrated mailbox on the 2013 server.
Send e-mail from migrated mailbox to external e-mail address.
I CAN:
Send e-mail from the migrated mailbox to a 2007 mailbox and the test mailbox on the 2013 server.
Send e-mail from the internet to the migrated mailbox and the 2013 test mailbox.
I unfortunately am running Exchange 2013 with CU6 (I am already aware of the activesync issue and delegation crash issue but saw the info too late).
Suggestions please!!

Hi,
Before going further, I'd like to ask the following questions to troubleshoot the issue:
1. Could you send email from 2007 mailbox to the test mailbox on 2013 server?
2. Did you get any NDR message when sending email to the migrated mailbox failed?
In addition, I recommend you try the following methods to find out the root cause:
1. Try to use message tracking tool in exchange 2007 server ,it will help us to find the email which was sent to the migrated mailbox .
2. Run the following command to check the permission groups of the receive connector:
Get-Receiveconnector |fl Name,PermissionGroups,Exchangeversion
Best regards,
Niko Cheng
TechNet Community Support

Unable to save/publish Projects on Project Server 2010() using Project Pro 2007 and 2010

Hi,
Recently we have upgraded from Project Server 2007 to 2010 SP-2 (BCM enabled) environment and from last few days we are getting issue with Project Plans where PMs are not able to update Projects means save and publish the Project using MS Project 2010/2007.
Whenever PMs try to open project using MS Project 2010 SP-2, it gets load successfully but when they hit save and publish no jobs are getting fired up nothing is happening. Only way to get out from MS Project 2010 window is to close the Project window and
and click discard changes. No error and exception windows are popping out in MS Project 2010, no error/problem/issue clue at all from MS Project 2010.
But when I try to update this Project plan for very first time using MS Project 2007 Sp-2 then I am getting below error
for any subsequent save and publish using MS Project 2007-SP2 getting below error
As an alternative I have tried to open this Project Plan using web and there it is getting opened saved and published successfully from PWA absolutely no issue.
Also I have saved this Project locally as XML and saved and published it on Server successfully. But after someday again this project got corrupt PMs started getting same problem again
I have also looked at ULS logs but not getting anything useful there.
So any guesses why this could happen that can give me pointers to find actual root cause, please let me know.
Thanks much !!!
Sachin Vashishth MCTS

Used below steps to fix the Projects on MSP 2010.
1) Open corrupted project in MS Project connected to PS 2010 Prod env.
2) Goto > Resource > Add Resource > Build Team From Enterprise
3) Check is there any local resource who has not replaced with corresponding enterprise resource. If yes then replace all those local resources with enterprise resource. If not then move to next step.
4) Open resource sheet view and sort or filter by local resources.
5) Then add few columns in resource sheet view like "Windows User Account, Email Address , Base Calendar etc".
6) Now check has any local resource having enterprise attribute assigned to it, if yes then delete or assign local value as appropriate.
7) Then GoTo > File > Save & Send > Save as project file > Save for sharing (at local location)
8) Close project plan window and click "Yes" to save changes.
9) Restart MS Project 2010 and open your project from local location.
10) Then Goto > File > Save & Send > "Publish to Project Server". This will open "Import Project Wizard" to validate Resources and Task in Project.
11) Then in Import Project Wizard window at left hand side click "Map Resource" to validate project resources.
12) This will "Map Project Resource to Enterprise Resource " check all the resources highlighted with "Red" font and map "Standard" calendar to local resources.
Note: Don't worry about local resource assigned "Standard calendar" but still highlighted "Red".
13) Then click "OK" and click on "Continue to step 2" at bottom of "Import Project Wizard".
14) Make sure you get number of errors 0 in step 2, else click on validate resource and take proper corrective action as explained in step 6.
15) If you leave at least one resource as a local resource (unmapped to an enterprise resource), you will see the local resource in the Import Resource grid on the right side
of the Confirm Resources page.
Examine the value in the "Import" column (if not able to see this column then insert this as new column) for the local resource .
The default value is "Yes", then change the value in the "Import" column
to "No", else system will import the local resource as an enterprise
resource.
16) Then "Continue to step 3, 4 and 5".
17) Then at Step 5 , Save project to Project Server by clicking "Save as" link.
18) Then publish the project to update the plan at PWA 2010.
Sachin Vashishth MCTS

How to Migrate MS Project Server 2007 to 2013

Hi
Can any one share some reference for migrating Project Server 2007 to 2013.
As in general process--
We can take the backup and and restore it in 2013 environment.
How to migrate Portfolio Server?
After restroring any steps need to be followed.
Please guide.
Thanks
Geeth If you feel that the answer which i gave you is Helpful please select it as Answer/helpful.

Hello,
For Portfolio Server 2007 options, review this guide:
http://www.microsoft.com/en-us/download/details.aspx?id=20815
Also see:
http://blogs.technet.com/b/projectadministration/archive/2010/07/21/anouncing-project-portfolio-server-2007-migration-documentation-to-project-server-2010-just-released.aspx
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Project Server 2010:- How to add Own Workspace filter in workspace web part like project server 2007

Hi All,
I am using project server 2010.
Can some one advise me how can I add Own Workspace filter option in workspace web part like project server 2007 which is showing all projects name page by page. There no filter option available. I am not sure if there is any out of box feature.
Thanks in Advance..

Nitin,
PS2010 shows by default the workspaces you have permissions to. Unfortunately, there is no more filtering options available.
The only solutions are to write a custom webpart, or develop your own SSRS Report, which you can customize the way you want.
Refer to Paul's excellent blog post on this topic here:
http://pwmather.wordpress.com/2011/08/05/custom-projectserver-project-site-workspace-view-in-pwa-ps2010-ps2007-epm-msproject-ssrs/
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

How to migrate Project Server 2003 to Project Online?

Hi Guys,
Is it possible to migrate Project Server 2003 to Project Online directly? I heard we normally have to take 3 hops for this;
1. Project Server 2003 - Project Server 2007 migration.
2. Project Server 2007 - Project Server 2010 migration.
3. Finally, Project Server 2010 - Project Online migration.
Is there a migration tool we can use to simply jump from Project Server 2003 to Project Online?
Thank You,
Arnel

NO, directly you can not migrate. You have to follow the sequence
1. Project Server 2003 to project server 2007
2. Project Server 2007 to project server 2010
3. Project Server 2010 to project server 2013 online.
Unfortunately we dont have nay tool which will help us to do this .
Microsoft has a virtual machine (2007) that you can use to jump to 2007. Basically the databases of 2003 must be converted to 2007. Once this is done (database at 2007) you can use this database as start point to be converted to 2010.
Microsoft has virtual machine for 2010 too if you want you can use it rather than creating your own environment.
Don't use 2007 backward compatibility mode in 2010, we experienced some issues with it.
kirtesh

Copy Custom toolbar from one instance to another in Project server 2007

Hi,
I am currently using project server 2007. We have a number of instances in our Project server enivoronment. Is it possible to copy customized toolbar from one instance to another? If yes, how?
Thanks in advance

Hi Khaldun,
As per my reply in your previous post, here is a link explaining how to use the organizer:
Http://blogs.msdn.com/b/project/archive/2010/10/22/tips-and-tricks-copy-custom-views-filters-tables-and-other-elements-to-other-projects.aspx?Redirected=true
Basically, just copy the toolbar from the global source instance into a blank project file. Then do the same operation from the blank file containing your toolbar into the destination global model, still using the organizer.
Hope this helps.
Guillaume Rouyre - MBA, MCP, MCTS

After upgrading Exchange Server 2007 to SP3 with update rollup 13, OWA not working

Hi,
We have just installed Service Pack 3 and update rollup 13 on our Exchange Server 2007, but unfortunately our OWA has gone inaccessible.
PROBLEM- The following error comes up when we try to access OWA :
Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: Object reference not set to an instance
of an object.
Call stack
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication()
Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart(Object sender, EventArgs e)
Inner Exception
Exception type: System.NullReferenceException
Exception message: Object reference not set to an instance
of an object.
Call stack
Microsoft.Exchange.Clients.Owa.Core.Configuration.CheckPublicFolders(ADSystemConfigurationSession session, ADObjectId[] pfdbIds, Boolean& allLegacy, Boolean& allLater)
Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor(ADSystemConfigurationSession session, String virtualDirectory, String webSiteName, ADObjectId distinguishedName, Boolean isPhoneticSupportEnabled)
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration()
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
ACTION TAKEN SO FAR :
1. Removed OWA virtual directories and recreated them again.
2. IIS has been reset.
3. Restarted the HUB/CAS server.
4. Created public folder database.
Even after doing all these activities, owa is still inaccessible. Please help.
Regards,
Ankur

Hi Ankur,
From your description, you can't access to OWA after upgrading Exchange server 2007 to SP3 rollup 13. Firstly, please locate to C:\ExchangeSetupLogs and make sure that it is a successful installation. If not, this issue often occurs.
If it is a successful upgrading, please follow the steps below for troubleshooting.
1. Open IIS Manager, click Default Web Site -> Authentication, make sure that Anonymous Authentication and Windows Authentication are enabled.
2. Click Default Web Site -> SSL Settings, check "Require SSL" and click Ignore.
3. Click Default Web Site -> HTTP Redirect, check Redirect (enter your
https://URL), check "Only redirect" box and Status code Found 302.
4. Expand Server Configuration -> Client Access ->double click owa ->Authentication tab. Check the Basic Authentication and check the Use forms-based authentication button Logon Format: Domain\user name.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Can't create data analysis views in windows 7/project server 2007

In Project Server 2007, when trying to create a new Data Analysis view or edit an existing one, we get the following error: "An error was encountered in loading the page". Using the F12 developer tools, I tracked it down to the following line:
"cn = new ActiveXObject("ADODB.Connection"), and in javascript the more specific error is "Automation server can't create object".
I assumed it was a browser permissions issue, and so I ensured the site is in trusted sites, and set the security level to low, but the same error is still occurring.
This error only occurs for users who are on Windows 7. This page works fine for users on Vista. The Windows 7 box has IE 9, the Vista box has IE 7.
Is Project Server 2007 supported in Windows 7/IE 9? Is there another security setting to look for?
edit: I have also checked the registry on the client and confirmed that adodb.connection is registered, and the dll exists.
Thanks,
Mike G.

Hi Mike,
If you refer to
this link, IE9 is supported by PS2007. Anyway, in the F12 developer tool, try to set the default browser to IE8. Also add the PWA url to the compatibility site settings in IE.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Unable to view Data Analysis in Project Server 2007

Hi,
I am currently using Project server 2007. One of our PM is not able to view Data Analysis information which are available to other PM.
It says 'The query cannot be processed. Either the user doesn't have access to Analysis service Database or the database doesn't exist"
We checked the following.
Tools >
Internet options > Security tab > Click Trusted Sites >
Custom Level > Search for Access data source across domains and its enabled.
Kindly advice. Thanks in advance!

Hi Nathik,
You should also check that the PM in question has not been granted specific permission. If he doesn't have the "View OLAP Data" and "View Data Analysis" permissions, he will not be able to use the data analysis. Also check
that the PWA URL is in the trusted site of IE. Finally press CTRL F5 to clean IE cache. Check also that the OLAP cubes were successfully built.
A good way for you to debug is to use your admin account on his machine to see if it is a permission issue or a IE setting issue.
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

Can only access emails through OWA after migration from exchange 2007 to 2013

can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
needed RCA ... plz help..

Hi,
From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

2 Problems after migration Project Server 2007 to 2010

Similar Messages

Maybe you are looking for