Solving Check-in Problems

Background

Microsoft Project Server provides storage and reporting services to the Microsoft Project Client (MS Project Professional) via the Microsoft Project Server 2013 Queuing System, or in short, the Project Server Queue. This Queue is a waiting line of jobs expected to be processed by Project Server.

Jobs such as Save, Publish or Check- in a Project are sent to this queue to be processed once there are not any other jobs with higher priority in the queue. Projects have to be checked out before opening them and making changes. This prevents other users from opening the project and making changes while the Project is checked out. If a user views the Project while you have it checked out, he or she will see the last version that was checked out, not the version being worked on. Once a Project is checked back in, users can see the changes that have been made.

Although the Queue Service adds multiple benefits to the Microsoft Project Server System, it is not perfect and sometimes jobs are not processed as expected.

Steps to check-in a Project

If a Project appears to be checked out, there are a few steps to correct this situation. They are listed in order, from least to most “destructive”.

·       Check-in Project via PWA

·       Open the project in read only mode and then close it

·       Refresh the list of available Projects

·       Cleaning the local cache

·       Recreate the Project Server Account

Check-in Project via PWA

The first step is to find out if your project is really checked out. Open Project Web Access by opening Internet Explorer and entering this URL:

https://olg.bemopro.com/PWA

Once PWA opens, click on Project Center.
Once in Project Center select the Project Tab from the Top Menu (Ribbon) and click on Check in my projects.

 This will provide you with a list of projects that are checked out depending on your permissions.
If the project you are trying to open is not listed, continue with the next steps for clearing out the local cache.

 Refreshing the list of available Projects

To refresh the list, please open Project Professional and from the main menu select File - > Open, or click on the Open option, or simply press Ctrl-O.

This will open the Open dialog box: 

Double-click on Retrieve the list of projects from Project Server, and that should refresh the state of your project. If the project still shows up as checked out, continue to open the project in read only mode.

 Open the project in read only

Open the project in read only mode and then close it. This will resend the check-in instructions to Microsoft Project. After 20 – 30 seconds, the project should be correctly checked in.

If this fails, continue troubleshooting by Cleaning the local Project Cache in Project Professional.

Cleaning the local Project Cache

Open Project Professional and from the File menu, select Options-> Save -> Local Project Cache - > Clean Up Cache.

Once the dialog box opens, please select the project that you are having problems with:

Note that the project might show up as checked out.

Once you have the project selected, please remove it from your local cache by pressing Remove from Cache:

If the problem is recurring, the next step is to delete the Project Server Account and add a new one.

Most common causes

• Presence of blank rows in the middle of the project.
• Assignments to Summary Tasks.

Project Server 2007: Migration from one domain to another

Brian Smith posted this step by step guide on moving a Microsoft Office Project Server 2007 system from one domain to another. We have gone through this process, and if we had this guide before, it would have been a lot easier to do so.
The guide was created by Lakshmana Rao (Laksh), and the original posting can be found here.

Project Server 2007: Migration from one domain to another
I’ve posted similar information before, but my colleague Lakshmana Rao (Laksh) has come up with a great document on the steps required when you want to move Project Server 2007 between domains. As Laksh points out at the end – please make sure you test this process in a non-production environment first – Hyper-V is perfect for these kind of tests. On with the document…
How to Move Project Server 2007 from one domain to another:
Considerations in this Article:
1. In this setup, the Project Server 2007 Farm has two servers (One Project Server 2007 SP2 Server box and one SQL Server 2005 SP3 Server box.) For multiple servers set up, please see the Note at the end of this article.
2. Current domain name is APAC and new domain name is NORTHAMERICA.
3. In the current set up, user account used for installing Project Server 2007 and as service account where ever is required is APAC\PsvrSrvcAcct
Prior to changing the Servers to the New Domain:
1. In the new domain, ensure that you have same account IDs and names as that of the domain account IDs and names in Project Server and the service accounts used for Project Server 2007.
Otherwise, after migration; we experience issues with user mappings and unknown issues related to resource assignments/ work/Actual work etc.
2. Take Full Farm back up from SharePoint Central Admin, Operations, Perform a back up. (For more details, please refer to “Back up and restore the Project Server 2007 farm” at http://technet.microsoft.com/en-us/library/dd207295.aspx
3. Create a user in PWA using the Local Administrator ID or any local User and add to Project Server Administrators group.
For example, if Application Server host name is PSVRPROD, create a user (PSVRPROD\Administrator) in PWA, Server Settings, Manage Users, New User and assign to Administrator group. (After domain migration, we use this account to login to PWA and perform administrative tasks).
4. Stop the WWW service in Project Server.
5. In SQL Server 2005, note the permissions of Service Accounts used on the SharePoint and Project Server databases. (Note the Server roles and User Mappings of the Service Accounts)
Steps to Move the Servers to New Domain:
Moving SQL Server 2005 box:
1. Join the SQL Server to the new domain.
2. Restart the Server.
3. Login to the server with Admin Privileges and add the respective service accounts to the Local Admin group.
In this scenario, I have added NORTHAMERICA\PsvrSrvcAcct. (Before domain change, APAC\PsvrSrvcAcct was present in Admin group.)
4. Open Services.msc and ensure that the MS SQL Server service is running. You may need to change the ‘Log on’ Account name if the service is using a domain account. Specify the correct service account and start the service.
5. Connect to the SQL Server using SQL Server Management Studio.
6. Expand the Security. Click on Logins.
7. Create Service accounts used in Project Server and provide proper permissions to the SharePoint and Project Server databases. (You need to refer to notes in step 5 in section “Prior to changing the Servers to the New Domain:” and give the same permissions ( Server roles and User mappings to the new service accounts)
In this scenario, I have created NORTHAMERICA\PsvrSrvcAcct in SQL Server and provided the same server roles and user mappings as that of APAC\ PsvrSrvcAcct
8. In MSP_RESOURCES table of Published database, change the domain name of the users.
Use the following query
UPDATE MSP_RESOURCES
SET WRES_ACCOUNT = REPLACE(LTRIM(WRES_ACCOUNT), '', '');
In this scenario, I used,
UPDATE MSP_RESOURCES
SET WRES_ACCOUNT = REPLACE (LTRIM(WRES_ACCOUNT), 'APAC', 'NORTHAMERICA');
Moving Project Server 2007 box:
1. Join the Project Server to the new domain.
2. Restart the Server.
3. Login as local Administrator and add the respective service accounts to the Local Admin group.
In this scenario, I have added NORTHAMERICA\PsvrSrvcAcct. (Before domain change, APAC\PsvrSrvcAcct was present in Admin group.)
4. Ensure that you are able to connect to SQL Server box. (You can use UDL connection test).
5. Follow the KB article, http://support.microsoft.com/kb/934838 and change the farm service accounts and passwords.
6. Ensure that the Project Server Queue, Event, SharePoint Timer services are using the new domain service account. These should have been set by the actions in step 5 so should not need changing manually (worth noting just in case they didn't do step 5 right and think manually changing will put things right),
7. Open IIS Manager and ensure that all the service accounts are changed to the new domain service accounts. If not change them and restart the IIS.
8. Login to SharePoint Central Admin site.
9. Click on Operations, Service Accounts.
10. Select Web Application pool. For Web Service, select “Windows SharePoint Services Web Application”.
11. For each Web Application pool, verify whether the user name is correct. If not update them and restart IIS.
In this scenario, I have checked whether it is NORTHAMERICA\PsvrSrvcAcct.
(Steps 8 -11 are to make sure that the SharePoint reflects the changes)
12. Log in to PWA using local Administrator ID ( created in step 3 of section “Prior to changing the Servers to the New Domain:” )
13. To initiate “User Synchronization for Project Web Access App Root Site and Project WSS Workspaces”, create a new Category (say “TestSync”) from on Server Settings, Manage Groups add users to this group ( do not add the currently logged in user ) and click save. Again, revert back the changes. Delete the newly created category.
14. Once, “User Synchronization for Project Web Access App Root Site and Project WSS Workspaces” is succeeded, synchronize the Project Workspaces from Server Settings, Project Workspaces.
15. Test the server by publishing a new project and existing project as well.
16. Ask users to access the PWA and Project workspaces and test.
Note: If that farm has multiple Application Servers and WFEs, you have to detach all the servers from the farm, except the server that host Central Admin site. Follow the above steps. The, move other servers to new domain and then connect to the farm one after another.
You can also use PSI functions “SynchronizeMembershipForPwaAppRootSite ()” to update PWA WSS Root Site information and “QueueSynchronizeMembershipForWssSite “to update each WSS Workspace. This requires writing a custom code.
As with any major changes, please test in your own environment to ensure these steps work for you before moving a production system.

Windows 7 Beta To RC Upgrade Instructions

I found this great post about upgrading Windows 7 beta to RC. I had this problem, and the fact that it is possible to avoid a full install was very exciting for me.
The original article can be found at www.windows7news.com

The Microsoft Engineering team has outlined how Windows 7 Beta users can upgrade their version of Windows 7 to the soon to be released Release Candidate of Windows 7. The disappointing news is that Microsoft suggests to do a clean install instead as the development changes introduced after the release of the beta of Windows 7 were not always compatible with the upgrades made thereafter.

A clean install on the other hand would mean that all the changes and customizations made to the operating system by the user would be lost. This is a nuisance although everyone knew beforehand that this could happen eventually. Microsoft is suggesting to do a clean install or upgrade from Windows Vista to Windows 7.

The RC, however, is about getting breadth coverage to validate the product in real-world scenarios. As a result, we want to encourage you to revert to a Vista image and upgrade or to do a clean install, rather than upgrade the existing Beta.

The Windows 7 release candidate setup will quit automatically if it recognizes a pre-RC build on the computer system. Microsoft did however publish a workaround for that for users who really need to do it:

1. Download the ISO as you did previously and burn the ISO to a DVD.
2. Copy the whole image to a storage location you wish to run the upgrade from (a bootable flash drive or a directory on any partition on the machine running the pre-release build).
3. Browse to the sources directory.
4. Open the file cversion.ini in a text editor like Notepad.
5. Modify the MinClient build number to a value lower than the down-level build. For example, change 7100 to 7000 (pictured below).
6. Save the file in place with the same name.
7. Run setup like you would normally from this modified copy of the image and the version check will be bypassed.

There you got it. It is still possible to upgrade a pre-release candidate release to the RC of Windows 7. Microsoft did add some words of caution to the article which are quoted below:

These instructions will be brief. Since everyone reading is a well-versed and experienced beta tester you know ALWAYS BACK UP YOUR MACHINE before running any OS installation and NEVER TEST AN OS ON YOUR ONLY COPY OF ANY DATA. Testing a pre-release product means just that—it is testing and it is pre-release. Even though this is a Release Candidate, we are still testing the product. We have very high confidence but even if an error happens once in 1,000,000 we want to make sure everyone is taking the precautions normal for a pre-release product.

One other related caution is INSTALL ONLY OFFICIALLY RELEASED BUILDS FROM MICROSOFT. It will always be tempting to get the build with the “mod” already done but you really never know what else has been done to the build. There’s a thrill in getting the latest, we know, but that also comes with risks that can’t even be quantified. For the RC we will work to release a hash or some other way to validate the build, but the best way is to always download directly from Microsoft.

It basically says to avoid unofficial releases of Windows 7 and to make sure that data has been backed up before starting the installation of beta and release candidate builds.

How to check Project 2007 version using VBA?

I recently went through a lot of trouble to find the version of each client connecting to Microsoft Office Project Server 2007. Luckily, Christophe Fiessinger posted this great entry in his blog.

Advantages of using a 64-bit Operating system with Microsoft Office Project Server 2007

I found this very interesting article while doing some research about an upcoming migration, and I thought I should share it with you.

Although some of the advantages of using 64-bit Operating systems seem obvious, such as increased virtual and physical memory addressing capabilities, others are not so evident, such as improved security and lower cost of ownership.

After reading this article you might be more inclined to migrate your environment to 64-bit software.

Important Information on Service Pack 2

If you have recently installed applied Service Pack 2 (SP2)  for Microsoft Office SharePoint Server 2007, this information is of high relevance to you.

A bug with Service Pack 2 (SP2) that affects all customers that have deployed it for SharePoint Server 2007 has been identified.

During the installation of SP2, a product expiration date is improperly activated. This means SharePoint will expire as though it was a trial installation 180 days after SP2 is deployed. The activation of the expiration date will not affect the normal function of SharePoint up until the expiration date passes. Furthermore, product expiration 180 days after SP2 installation will not affect customer’s data, configuration or application code but will render SharePoint inaccessible for end-users. Please read further information at the official SharePoint blog, http://blogs.msdn.com/sharepoint/archive/2009/05/21/attention-important-information-on-service-pack-2.aspx

Other great resource is Brian Smith's Blog:

http://blogs.msdn.com/brismith/archive/2009/05/20/project-server-2007-license-type-set-to-trial-after-loading-office-server-service-pack-2-sp2.aspx

 

CACTUSS and SALSSA Videos and Power Point Presentation

Hi everyone,

As I promised, I am uploading the videos showing how to install SQL Reporting Services 2005.
I hope you enjoyed the meeting. I am working to create additional material for having a next presentation soon, please keep checking my blog for any future events.
I enjoyed both groups tremendously and thank everyone that could attend.

The installation video is available here.

The configuration video is coming later on today.

If you want a copy of the Power Point presentation, please send me a request to Virgilio.Arciniegas@CatapultSystems.com

Look forward to see you soon in the next meeting.

SQL Reporting Services Presentation in San Antonio

I will be presenting at SALSSA on May 20th.
The title of the presentation is "Creating reports for Microsoft Office Project Server 2007 using SQL Server Reporting Services"
Please mark your calendars.
When: Wednesday May 20th, 6:00pm – 8:00pm
(Always the third Wednesday of the month)

Where: New Horizons
8200 IH 10 West Suite 500

Topic: Creating reports for Microsoft Office Project Server 2007 using Reporting
Services

Presenter:
Virgilio Arciniegas, MCSE - MCAD – MCDBA – MCITP
Senior Consultant
CATAPULT SYSTEMS INC.

Give away:
A one year free subscription to Learn Visual Studio .Net with over 500 online
videos and a one year free subscription to Learn SQL Server with over 20 hours
of videos.

More Info:
jim.steiner@rackspace.com
www.salssa.com

Pizza and soda will be provided. All are welcome.

SQL Reporting Services Presentation in Austin

I will be presenting at CACTUSS on May 19th.
The title of the presentation is "Creating reports for Microsoft Office Project Server 2007 using SQL Server Reporting Services"
Please mark your calendars.
Location:
Microsoft Technology Center
Stonebridge Plaza, Building One
9606 N. Mopac Expressway, Suite 200
Austin, TX 78759
When:
05/19/2005
5:30 pm

New requirements for SharePoint Server 2010

The new requirements for SharePoint Server 2010, hence Project Server 2010 have been disclosed on TechEd:


- SharePoint Server 2010 will be 64-bit only
- SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2
- SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005
- SharePoint Server 2010 will require a standards based browser to author content (XHTML 1.0 compliant) so will not support IE 6.

You can read more about this at Brian Smith's blog.