Wurzburg

Naia Tracker

Home - Naia Corporation

Security and WebServices

Google Search: PWA 2002 task time

Yes, this is true: Microsoft Project crashes with error message:
"Microsoft Project has encountered a problem and needs to close. We are sorry for the inconvenience." every time when I open Microsoft project with "team" account.

Here is related reference:
329665 - OAER: Project Stops Responding When You Copy Tasks from Inserted Project Plans

Can't create account when publishing project to Project Server

MS Project Server Spooler error

This error is caused by project authors (project managers) using local resources in project plans. By default, account creation is set to deny in Project Server, therefore, project managers can’t create accounts for new resources in the system. Project attempts to create accounts for local resources. A local resource is a resource that is not in the Enterprise Resource Pool. Local resources can have Project Server accounts if you want them to. Local resources are indicated in the system as "local" by its indicator icon in the indicators column of the Resource Sheet view. The indicator for this resource will be a single head with a piece of paper to the left of it.



Resolution

Open Microsoft Project and log into Project Server with an Administrator account
Click Tools - Enterprise Options - Open Enterprise Resource Pool selecting resources to update
Double click on a resource
On the General tab, set Workgroup value to none
Leave the email address blank
Alternately, setting the resource type to Generic will prevent the error.

Google Groups discussion
A non-enterprise project is any project that is not saved in the Project
Server database because you were not logged into Project Server when you
created it. To solve this problem, please do the following:

1. Open Microsoft Project 2002
2. Click Tools - Enterprise Options - Microsoft Project Server Accounts

In the dialog box, there is a "Current Account" setting just below the
Add... button. If the "Current Account" setting says "My Computer", then
you are NOT logged into Project Server. If this is the case, click the
Add... button, then create and test the new account, and then set the
account as the Default account.

3. In the lower left corner of the dialog box, click the "Manually control
connection state" option
4. Click the OK button
5. Close Microsoft Project 2002, then relaunch the software
6. When prompted, select your correct user account (not the My Computer
account) and then click the Connect button

Once you are logged in to the Project Server through Microsoft Project 2002,
you will now need to import your project to the Project Server database
using the Import Wizard. To do this, click Tools - Enterprise Options -
Import Project to Enterprise. Follow each of the steps in the wizard to
save the project in the Project Server database, then you can publish it.

See also: You are attempting to publish a non-enterprise project

File is already open.: " is already open."

# posted by Dennis Gorelik @ 11:35 AM 0 comments

If you have "Bad Data" error - remove "IsolateApps" attributes from machine.config file:
1) Open C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\CONFIG\machine.config
2) Find "<machineKey"
3) Remove two "IsolateApps" attributes from <machineKey> element.
Before:
<machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="SHA1"/>
After:
<machineKey validationKey="AutoGenerate" decryptionKey="AutoGenerate" validation="SHA1"/>
4) Restart IIS.

Removing of "IsolateApps" attributes from machine.config is necessary in order to provide smooth security integration between several web-applications.
More details:
microsoft.public.dotnet.framework.aspnet.security: FormsAuthentication.Decrypt causes System.Security.Cryptography.CryptographicException: Bad Data Error

Setup ASP.NET debugging

Remote Debugging Components Install
Frequently, users want to remotely debug an application running on a separate machine. Visual Studio .NET provides a smaller subset of components that, when installed on a remote machine, and once you give yourself sufficient privileges, allows you to remotely debug processes on that machine. This installation is extremely useful when you do not want to install the entire Visual Studio .NET onto a remote machine. The installation of these components is started with the Remote Components Setup link at the bottom of the Visual Studio .NET Setup page of the CD. Clicking this link allows you to install remote debugging components for all languages that use DCOM to communicate with the debugger, or just C++ only (if you prefer the Visual C++ 6.0 method of remote debugging over TCP/IP).

Facsys client installation files

"HTTP 1.1 500 Internal Server Error" ASP.NET solution by Stuart Campbell
Microsoft Development Environment
---------------------------
The Web server reported the following error when attempting to create or
open the Web project located at the following URL:
'http://localhost/WebApplication1'. 'HTTP/1.1 500 Internal Server Error'.
---------------------------
OK Help
---------------------------

I found LOADS of 'solutions' to this problem on the web and in the
newsgroups but nothing seemed to work.
Finally, The one that worked for me was the simplest of them all:
.......make sure that the default website in IIS has an application!!!!!!!