Exception: WUPD0248E: Fix pack update failure: The processing of fix pack WP_PTF_6104, component wp.ptf.config failed.

IBM says:

Completed processing extractor command line arguments. Performing extraction. Failed to perform extraction. Exception: WUPD0248E: Fix pack update failure: The processing of fix pack WP_PTF_6101, component wp.ptf.config failed.

Cause

The fixpack installation was performed utilizing a non-root user. Reviewing permissions on the directory structures for the /tmp file indicated the non-root user did not have write permissions on that directory. Therefore, the extraction of the updated .jar files to the /tmp directory failed.

Environment

Any supported UNIX® or Linux™ operating system may be affected. NOTE: Microsoft Windows operating systems should not be affected by this error message as the user ID used for Portal on Windows must be a member of the Administrators Group per the Portal 6.1 Information Center.

But, it happened to me on Windows.. the message in another log file was slightly different--it was making some changes of wkplc.properties which it said it couldn't write to. Odd, because I owned that directory, and am admin, and that's the only file I changed.. from a remote machine. Yes, it's usually more convenient to do something on a non-windows machine where you have real tools to work with. I am logged over the network as the same user, or should be, so why does writing over the next change it?

dir /Q will show owners..

C:\wps\WebSphere\wp_profile\ConfigEngine\properties>dir /q
Volume in drive C has no label.
Volume Serial Number is 3108-D2F9

Directory of C:\wps\WebSphere\wp_profile\ConfigEngine\properties

11/04/2009 11:32 AM 2,729 BUILTIN\Administrators db.config.properties
11/04/2009 11:32 AM 1,381 BUILTIN\Administrators empty.properties
06/14/2010 12:50 PM 87,670 ... test
06/14/2010 02:32 PM 87,670 BUILTIN\Administrators wkplc.properties
05/12/2010 11:48 AM 87,566 BUILTIN\Administrators wkplc.properties.standalone

Whatever '...' is, the administrator can't write to it.
Guess it's not surprising anymore when microsoft does things wrong.

Websphere Network Deployment, cluster creation: "Check the add node log for details"

[A search for "Check the add node log for details." returned very little, hence this entry..]

When adding the first node to a cluster,
all the configuration and applications are retrieved from it.
This may take a while. The output you see in the Node Deployment Manager console looks like this:

ADMU0001I: Begin federation of node node01 with Deployment Manager at mgrnode.company.org:8879.
ADMU0009I: Successfully connected to Deployment Manager Server: mgrnode.company.org:8879
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: server1
ADMU0506I: Server name: webserver01
ADMU0506I: Server name: WebSphere_Portal
ADMU2010I: Stopping all server processes for node node01
ADMU0510I: Server server1 is now STOPPED
ADMU0510I: Server WebSphere_Portal is now STOPPED
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: node01
ADMU0120I: isclite.ear will not be uploaded since it already exists in the target repository.
ADMU0120I: isclite.ear will not be uploaded since it already exists in the target repository.
ADMU0014I: Adding node node01 configuration to cell: mgrnodeCell01
The console has not received information on the add operation in a timely manner. The state of the operation is indeterminate. Check the add node log for details.

The addNode.log file is on the server you added to the cluster, in ...\WebSphere\wp_profile\logs\addNode.log.

If you were successful, you should see:

[4/19/10 7:41:10:166 EDT] 0000000b NodeSyncTask A ADMS0003I: The configuration synchronization completed successfully.
[4/19/10 7:41:10:368 EDT] 0000000a AdminTool A ADMU0018I: Launching Node Agent process for node: node01
[4/19/10 7:41:33:410 EDT] 0000000a AdminTool A ADMU0505I: Servers found in configuration:
[4/19/10 7:41:33:410 EDT] 0000000a AdminTool A ADMU0506I: Server name: nodeagent
[4/19/10 7:41:33:425 EDT] 0000000a AdminTool A ADMU0506I: Server name: server1
[4/19/10 7:41:33:441 EDT] 0000000a AdminTool A ADMU0506I: Server name: webserver01
[4/19/10 7:41:33:457 EDT] 0000000a AdminTool A ADMU0506I: Server name: WebSphere_Portal
[4/19/10 7:41:36:561 EDT] 0000000a AdminTool A ADMU9990I:
[4/19/10 7:41:36:655 EDT] 0000000a AdminTool A ADMU0308I: The node node01 and associated applications were successfully added to the mgrnodeCell01 cell.
[4/19/10 7:41:36:670 EDT] 0000000a AdminTool A ADMU9990I:
[4/19/10 7:41:36:686 EDT] 0000000a AdminTool A ADMU0306I: Note:
[4/19/10 7:41:36:701 EDT] 0000000a AdminTool A ADMU0302I: Any cell-level documents from the standalone mgrnodeCell01 configuration have not been migrated to the new cell\
.
[4/19/10 7:41:36:733 EDT] 0000000a AdminTool A ADMU0307I: You might want to:
[4/19/10 7:41:36:733 EDT] 0000000a AdminTool A ADMU0303I: Update the configuration on the mgrnodeCell01 Deployment Manager with values from the old cell-level documents.
[4/19/10 7:41:36:748 EDT] 0000000a AdminTool A ADMU9990I:
[4/19/10 7:41:36:764 EDT] 0000000a AdminTool A ADMU0003I: Node node01 has been successfully federated.

For me, with not a large amount of custom deployment, this occurred about 10 minutes after start.

The portal will not necessarily start up successfully after this, however... I got the error
com.ibm.wps.ac.DomainAdministratorNotFoundException: EJPSB0107E: Exception occurred while retrieving the identity of the domain admin ...
and only got 404 errors when trying to access the portal.
Problem: I missed a step.
[PDF] A Step-By-Step Guide to Configuring a WebSphere Portal v6.1.0.3 (WPv615ClusterGuide.pdf) -- wish I had found this document earlier.