sql server: "User, group, or role XXXX already exists in the current database." even after deleting user and recreating

A database user existed without an associated sql server login.
WebSphere wants login to match the schema name (up to now it seems okay...)

• tried to create a user with this login -- failed because 'user or role' already exists. or principal, I forget the error.
• delete that login. fail because its the owner of a schema.
• edit that schema, assign ownership to another user
• create login. failed because of user mapping, with a message similar to above.
  
• but it was actually created! I saw it later after trying to see if I could find any reference to the user.
• try to modify the user mapping again. okay for the default schema/database, and I could login okay, but trying to assign the user mapping for database 'master' failed, and I think those SqlJDBCXAUser role settings are necessary.
  

So I searched google for "User, group, or role" "already exists in the current database." "user mapping" master, and found the following:

SQL Server Tip - Fixing Orphaned Users and ran the following as sa:

sp_change_users_login 'auto_fix', 'UserName'

where UserName is the name of your user.

The row for user 'customizationusr' will be fixed by updating its login link to a login already in existence.
The number of orphaned users fixed by updating users was 1.
The number of orphaned users fixed by adding new logins and then updating users was 0.

checked the login to see if I could make the master mapping... It was already there!
Success. am i certified ms sqlserver dba now?

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.

Awareness works sometimes in Sametime, or for certain people, or I don't see myself as online

Probably a case issue...
see

Upper/Lower case discrepancies in DN cause problems with Awareness in Common PIM and Domino portlets

Question You are using one or more of the Lotus® Domino® and Extended Products Portlets or Common PIM Portlets with IBM® WebSphere® Portal. You initially have trouble with Awareness working in the portlet(s), but after you follow the troubleshooting script, "Troubleshooting Sametime Awareness in WebSphere Portal" (#1163790), the STLinks applet loads correctly in your browser.
However, you then notice that either no Awareness functionality ever appears in your browser, or if your name appears multiple times on a page, some will show Awareness (for example, green icon to symbolize a person is logged into Sametime and available, etc.) while others do not.
...

.. though in addition to the stlink.js change listed there, the one I was sent also has this:

1748,1756d1747
<
< //fix for PMR 73450,SGC,724 -- stcl portlet fails to load mixed case awareness.
<
< if(!STlinksCaseSensitive) {
< linkId = linkId.toLowerCase();
< }
<

now why didn't they put that there?

Generally their support is okay (at least after you get off the web and get someone on the phone).. is this to require maintenance ?

.... okay, I thought that fixed it.
I swear I saw it work.
But I am still seeing issues.

Will update later....

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.

Citrix Web Interface fails after Websphere migration v6.0 -> v6.1

If you can actually get migration to work,
and you have this portlet, you might see this in your logs:

[3/17/10 11:35:55:867 EDT] 0000003c AdminLinkInfo W com.ibm.workplace.searchmenu.portal.taglib.AdminLinkInfoExtTag doStartTag The search menu tag is not supported in this version of WebSphere Portal. Please refer to the Information Center for details.
[3/17/10 11:35:55:960 EDT] 0000003c WebApp E [Servlet Error]-[/WEB-INF/jsp/View.jsp]: com.ibm.ws.jsp.translator.JspTranslationException: JSPG0227E: Exception caught while translating /WEB-INF/jsp/View.jsp:
/WEB-INF/jsp/View.jsp(14,1) --> JSPG0009E: Unable to load tag handler class org.apache.pluto.tags.DefineObjectsTag

Enterprise app name: PA_Citrix_WI
locally, my file was called NewCli3.war.

Solution:
unzip the file, edit View.jsp, jar it back up, update the app in websphere portal server, and the error should go away.

How to change JSP? see Changing JSP source
1. Change the tag library to use the standard tag library.
in some goddamned IBM documentation.

This PTF WP_PTF_6102 can not be installed/uninstalled because PortalAdminPwd, W asPassword have not been entered in wkplc.properties.

Full message:

E:\IBM\WebSphere\PortalServer\update>UpdatePortal -fixpack -installDir "E:\

IBM\WebSphere\PortalServer" -fixpackDir "E:\IBM\WebSphere\PortalServer\updat

e\fixpacks" -install -fixpackID WP_PTF_6102 -fixpackDetails

Start of [ UpdatePortal ]

Build 20090714_0130

Verifying installer jar:

[ PortalUpdateInstaller.jar ]

Setting permissions on E:\IBM\WEBSPH~1\PORTAL~1\version

Set encoding: console

Fix pack update specified

Fix pack directory: E:\IBM\WebSphere\PortalServer\update\fixpacks

Installation specified

Fix pack: WP_PTF_6102

Target product directory: E:\IBM\WebSphere\PortalServer

Copyright IBM Corporation 2002, 2008; All rights reserved.

WebSphere Portal Version 6.1

Update Installer Version 1.6.1, Dated 5/1/08

UpdateInstallerArgs.isThisUninstall 0

UpdateInstallerArgs.isThisUninstallforFixpack 1

UpdateInstallerArgs.thisIsFixpackID WP_PTF_6102

WPConfig:findWkplcProperties

what is profileDirectory? e:/IBM/WebSphere/wp_profile

wp_install_root is e:/IBM/WebSphere

WP_PTF_6102Checking for Passwords ...

PortalAdminPwd has not been entered

WasPassword has not been entered

This PTF WP_PTF_6102 can not be installed/uninstalled because PortalAdminPwd, W

asPassword have not been entered in wkplc.properties.

UpdateInstaller.puiReturnCode is 8

End of [ UpdatePortal ]

----------------------------------------

Well, I set the passwords... got a little farther:

UpdateInstallerArgs.isThisUninstall 0

UpdateInstallerArgs.isThisUninstallforFixpack 1

UpdateInstallerArgs.thisIsFixpackID WP_PTF_6102

WPConfig:findWkplcProperties

what is profileDirectory? e:/IBM/WebSphere/wp_profile

wp_install_root is e:/IBM/WebSphere

WP_PTF_6102Checking for Passwords ...

log file in configtrace checking e:/IBM/WebSphere/wp_profile\ConfigEngine\log\Co

nfigTrace.log

Checking the status of all Application Servers

Checking status of server server1

Checking status of server WebSphere_Portal

Checking product features:

[No fix pack detail]

The specified fix pack does not exist

WP_PTF_6102

UpdateInstaller.puiReturnCode is 9

End of [ UpdatePortal ]

.............................................................

okay, maybe i didn't have the file(s) in fixpacks, but a subdirectory

There seemed to be a problem before, so I moved them..

start at 8:50pm ...