Cascade Skyline - with Microsoft Logo and Project Support header - author Brian Smith

  • Brian Smith's Microsoft Project Support Blog

    Is your Project Server 2007 queue running a few minutes slow?

    • 7 Comments

    Not sure if you remember the problem we had with Daylight Savings Time last year - but basically when adding jobs to the queue they have a time when they should be processed - and most times this time is "now" or the current time.  Well with the DST problem "now" was actually set in one hour's time - so some jobs just sat there for a while.

    We have seen a couple of recent cases where time differences between servers can give this same problem.  A server puts a job on the queue and the timestamp for "now" gets set a couple of minutes in the future - because the SQL Server machine doesn't have the same time as the Project Server machine.  When the queue gets to this job it will just let it sleep until the right time arrives.  This can look like a slow queue, when in fact it is doing what it is told.  Keeping your servers clocks in sync will avoid this problem.  The ULS logs will show this as jobs sleeping when there does appear to be any reason.  In most "sleeping" cases the reason appears in the log - such as a missing custom field in the reporting DB will put a project reporting publish to sleep.

    Technorati Tags: Project Server 2007

  • Brian Smith's Microsoft Project Support Blog

    Join the Project Server Developer Community

    • 1 Comments

    Apologies if you have already read this on the Programmability blog - but an excellent chance to share your development experiences with others - and hopefully learn some stuff too!

    Leveraging the development aspects of Project Server 2007 spans a wide range of skills.  PWA customizations (ASP.NET), workflow development, line of business applications integration using the PSI, extending Project Server functionality using server side events, specialized reporting from the Project Server databases and experience using VSTO are all areas of discussion. 

    The Project Server Product Group currently supports these efforts through channels such as the this Blog, the Programmability Weblog, Project.Server Discussion, Project.Developer Discussion, and the Project 2007 Team Blog.

    To streamline and augment the existing efforts, we are seeking developers to join the already established Project.Developer Discussion Group

    By joining we invite you to share and discover knowledge about Project Server 2007's highly extensible out-of-the-box developer's platform, access Project Server Developer best practices, utilize a technical window back to the MS Project Server Development Group, and take part in several specialized webcasts on Development topics coming up in the next couple months.

    To identify yourself as someone that would like to join the Development Community, please contact Joyce Bileau, v-joyceb@microsoft for more information.

    To join, go to http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.project.developer

  • Brian Smith's Microsoft Project Support Blog

    Project Resource Kit for Project Server 2007 Released!

    • 40 Comments

    This is now available for download at http://www.microsoft.com/downloads/details.aspx?FamilyId=A33D253C-6424-48E4-B87E-0861D1977BB7&displaylang=en.  Just had an e-mail from Phil Smail with these details:

    The Project Resource Kit for Project 2007 has released. It’s available for x86 and x64 and the tools are English only

    The PRK consists of the following tools:

    · Portfolio Analyzer Views Migration: Allows an administrator to bulk edit the location of an analysis server for multiple data analysis views.

    · Project Server Settings Backup and Restore (Playbooks): Allows an administrator to backup Project Server settings and restore those settings to another Project Server.

    · Project Server Data Populator: Allows an administrator to populate Project Server with projects, resources and other objects. Useful for helping capacity and performance testing.

    · Project Workspace Site Relinker: Allows an administrator to relink the connection between Project Server and Project Workspace sites.

    · View Effective Rights: Allows an administrator to query the Project Server to determine the effective permissions of users against projects or resources.

    Full documentation will appear in the next couple of weeks but I’ll get early docs up on the Project blog either today or tomorrow

     

    I'll be finding time to play with these over the next few days - and see the settings backup and restore tool as a really useful one.  This may be something we use in support to get configuration details of your servers if we are investigating an issue that isn't data related - so we don't need the full database set - but need to know how you have configured your server.

    Enjoy!  And let us know how you get on with these.

    Technorati Tags: Project Server 2007

  • Brian Smith's Microsoft Project Support Blog

    Failure Audit message in SQL Server - Event ID: 18456 every minute?

    • 10 Comments

    This is a event log error I have seen in Project Server 2007 on various farms going right back to the Beta and I finally found some time to track it down.  It didn't seem to be breaking anything on my server, but made it difficult to read the logs and see other "important" stuff.  This is the error:

    Event Type:    Failure Audit
    Event Source:    MSSQLSERVER
    Event Category:    (4)
    Event ID:    18456
    Date:        1/17/2008
    Time:        1:29:00 PM
    User:        DOMAIN\User
    Computer:    SERVERNAME
    Description:
    Login failed for user 'DOMAIN\user'. [CLIENT: <local machine>]

    I did a SQL Profiler trace to see where it was coming from and discovered the cause was a SQL Server Agent job called SharedServices_DB_Job_DeleteExpiredSessions that was running every minute.  The reason for the failure was that I did not have a SharedServices_DB on that server.  I did once - but my test server gets changed around a fair bit and this was a remnant that didn't get cleaned up. Not sure if it would normally get removed and if I did something bad which left it hanging around. 

    This could also happen with Microsoft Office SharePoint Server 2007 even if Project isn't installed as it relates to the Shared Services Provider.  To disable the job you can go to SQL Management Studio, and connect to your database engine, then expand SQL Server Agent - select the Disable option. 

    image

    There will likely be other valid jobs there too - for your real SharedServices databases that still exist.  The bad one will show that it has failed when last executed if you look in the Job Activity Monitor.

    image

    Not a big problem - but at least disabling will keep the logs looking clean, and will save a few CPU cycles for some real work.

    Technorati Tags: Project Server 2007

  • Brian Smith's Microsoft Project Support Blog

    What is special about the "Administrator Account" when provisioning a new PWA site?

    • 3 Comments

    Nothing much really.  But we do often get the question "How do I change the administrator account?"  If you go to the Manage PWA Page then you will see that it is greyed out.  You can't change it here - but then you don't really need to.  This account is just put in the database so that you have an admin in the system and you can log in.    I guess this can be a problem if the person is the only admin - and is not available to log in, but the admin's first job should be to create the second admin.  The first administrator is also set as the primary administrator of the site collection created for the PWA site.  You can update the user in this case using stsadm -o siteowner.  The parameters for this command are -url <url of site> -ownerlogin <DOMAIN\user> -secondarylogin <DOMAIN\user>.  You could also use stsadm to add users to Project Server using the -o projcreateentity flag.  See Christophe's posting for full details of stsadm commands for project.

    One gotcha we have come across when provisioning against an existing set of databases is that if the account you use for the administrator account already exists in the database then it must also be an active user.  If it is an inactive account then the provision will fail with event ID of 7013 and 6966.

    Technorati Tags: Project Server 2007

Page 76 of 92 (460 items) «7475767778»