Murthy GS's Blogging Spot https://docs.microsoft.com/archive/blogs/murthygs/feed.xml Wed, 17 Apr 2019 04:10:46 GMT en-US hourly 1 Repair of an Outlook 2003 component generates a repair of Project 2007 https://docs.microsoft.com/archive/blogs/murthygs/repair-of-an-outlook-2003-component-generates-a-repair-of-project-2007 Tue, 18 Jan 2011 21:41:54 GMT https://blogs.msdn.microsoft.com/murthygs/2011/01/18/repair-of-an-outlook-2003-component-generates-a-repair-of-project-2007/ Symptoms

If you have Outlook 2003 and Microsoft Office Project 2007 installed on the same computer, a repair of an Outlook 2003 component generates a repair of Project 2007. Additionally, the operating system is restarted.

The Pop up completes after few minutes and again pops up when we receive an email in the outlook 2003 or send an email from the outlook 2003.

OS - Windows xp Pro Sp2 x86

Cause

Having installed the 2 versions of the office products , Outlook 2003 and Project Pro 2007.

Resolution

- Go to Add/remove programs on this computer, look for office 2003.

- Click the change button and do a repair of the product.

- Once this completes do the same for Project 2007.

- Allow it to complete the repair.

- Do a re boot of the machine.

]]> Project Svr 2007 - Dont want to create workspace while publishing a project. https://docs.microsoft.com/archive/blogs/murthygs/project-svr-2007-dont-want-to-create-workspace-while-publishing-a-project Tue, 18 Jan 2011 21:29:24 GMT https://blogs.msdn.microsoft.com/murthygs/2011/01/18/project-svr-2007-dont-want-to-create-workspace-while-publishing-a-project/ Symptoms

When I choose to 'pulish' my project plan via Project, I get a message that says I can publish a workspace. There is also an option to choose the radio button that says 'do not create a workspace at this time'. However, that option is grayed out, so I am forced to create a workspace each time I publish a project. Is there a setting I can change to stop this?

Cause

Becuase of the default setting in -> Browse to PWA -> Server setting -> Operational Policies -> Project Workspace Provisioning Settings -> Automatic Provisioning. We will have to change the option under this link.

Resolution

PWA -> Server setting -> Operational Policies -> Project Workspace Provisioning Settings -> Automatic Provisioning -> Allow users to manually create project workspaces in Project Server. Save the PWA.

]]> Access Denied - Error message when we access https://xxxxxxxx/PWA - Project Web Access https://docs.microsoft.com/archive/blogs/murthygs/access-denied-error-message-when-we-access-httpxxxxxxxxpwa-project-web-access Fri, 25 Dec 2009 01:19:00 GMT https://blogs.msdn.microsoft.com/murthygs/2009/12/25/access-denied-error-message-when-we-access-httpxxxxxxxxpwa-project-web-access/ Initially users on the client machines were seeing "Access denied" message when they try to browse to https://xxxxxxxx/PWA.

When we try to access the PWA on the Project server 2007 server, we saw the same behavior.
No matter what account we use to access the PWA, we see access denied, we also tried the SharePoint service account " System Account" but no luck.

When we get the access denied message, simultaneously we saw that the following event being logged in the application logs on the project server.

Apparently we saw this Event ID getting logged frequently


Event Type: Error
Event Source: Office SharePoint Server
Event Category: Project Server
General
Event ID: 6058
Date:  xxxxxxxxxxx
Time:  xxxxxxxxxxx
User:  N/A
Computer: (computer name)Description:


Failed to get language information for Project Server (http address)

We implemented KB article - https://support.microsoft.com/kb/934838, ALL the command in this KB completed successfully.We did a re boot of both the SharePoint servers in farm. Still the problem was occurring.We also restarted the 2 PRJ services, SQL service, still no luck.  Eventually  we saw that the SSP links like - the search settings, search administration , user profile properties links were also not working.


ERROR- An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.

We implemented the steps in - https://support.microsoft.com/?id=962928. "You cannot browse to an SSL-secured Office SharePoint Server 2007 site or to the Search Settings page for a Shared Services Provider".

Installed- KB- 959209, Re booted the server, All the links started working in SSP and the PWA site also was accessible.

]]> 401 - You are nto authorized to view this page - Refresh or f5 will help. https://docs.microsoft.com/archive/blogs/murthygs/401-you-are-nto-authorized-to-view-this-page-refresh-or-f5-will-help Tue, 29 Sep 2009 22:40:00 GMT https://blogs.msdn.microsoft.com/murthygs/2009/09/29/401-you-are-nto-authorized-to-view-this-page-refresh-or-f5-will-help/ ENVIRONMENT -

MOSS 2007 - Upgraded to Sp1 - 12.0.0.6219

OS - Windows Server 2003 ENT SP2 x64

SQL - SQL server 2005

 PROBLEM DESCRIPTION -

This problem occured after applying Sp1 - When we browse to a SharePoint site for the frist time after IIS RESET and also browse to the links with in this site for the first time- we are prompted for user authentication and when the users gives the credentials the site come up. But the point is that this web application is configured for anaonymous access. So the question is why is the site asking for credentials when it is for anonymous access.

CAUSE - 

In the web.config file <compilation batch="true" debug="true">  was the culprit. By default this tag should be <compilation batch="false" debug="false">.

Ideally in production environments the debug value should be false, if it is "true" then the web.config file will go into debug mode and look for permissions. It specifies whether to compile debug binaries rather than retail binaries.

RESOLUTION -

Change the debug value from "true" to "False".

What is Batch compilation?

 

In short, when debug=true, we don’t batch compile, when debug=false we do…

 

When an aspx, asax, or ascx page is first requested it gets compiled into an assembly. This assembly has a name like 3ks0rnwz.dll or similar (8 characters) and stores the class for the actual ascx, asax, or aspx page (not the code behind). The assembly goes into a folder in the C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files with the same name as the application.

 

Related Link - https://msdn.microsoft.com/en-us/library/s10awwz0.aspx


 

 

 

 

]]> MOSS 2007 - ERROR - Trial period for this product has expired. https://docs.microsoft.com/archive/blogs/murthygs/moss-2007-error-trial-period-for-this-product-has-expired Mon, 20 Apr 2009 00:08:00 GMT https://blogs.msdn.microsoft.com/murthygs/2009/04/20/moss-2007-error-trial-period-for-this-product-has-expired/

BEHAVIOR:

====================

When we perform certain tasks in SharePoint portal 2007 site, like, create a publishing or collaboration site or check out web parts or a custom VS2005-build

Workflow with a document library or while creating pages, you get an error message.

ERROR MESSAGE:

====================

The Trial period of this product has expired

ENVIRONMENT:

====================

Product - Office SharePoint server 2007 -12.0.4518.1016

OS - Windows server 2003 standard edition Sp2

CAUSE:

====================

This error still happens on the RTM release, not just the B2TR release as mentioned

in the forum post. Also caused by a server in a farm scenario (even a single-server

farm) whose application pools are using non-admin accounts.

RESOLUTION:

====================

- Customer as soon as getting this error message will try to check if he had the

trial version or the full version and tries to convert the license by "convert

license type" link in the central administration operations page.

-This step might fail with the following error -"your license conversion operation

failed. Check the error logs for details" this is an expected behavior as the

SharePoint license is already converted to a full version from a trial version.

-The actual problem will not be solved by the above 2 steps.

-We changed the application pool log on from network service account to a

SharePoint administration service account.

- Made this account the local administrator, by adding into the local administrator

group.

- Added the SharePoint administrator service account to the IIS_WPG and WSS_WPG

groups. Did an IIS reset.

- Logged into the system with the SharePoint administrator service account.

- These steps did not bring the trial expired error message.

- And the issue got resolved.

KEYWORDS:

====================

SharePoint MOSS 2007 license expired trial period

MORE INFORMATION:

====================

NOTE - This is a Non MS Link.

<https://weblogs.asp.net/avnerk/archive/2007/02/20/trial-expired-errors-in-unexpected-places.aspx>

]]>