cmd: manageprofiles -validateAndUpdateRegistry
response: [PROFILENAME]
Verify with:
cmd: manageprofiles -deleteAll or manageprofiles -delete -profileName
response: INSTCONFSUCCESS: All profiles are deleted
cmd: manageprofiles -validateAndUpdateRegistry
response: [PROFILENAME]
Verify with:
cmd: manageprofiles -deleteAll or manageprofiles -delete -profileName
response: INSTCONFSUCCESS: All profiles are deleted
In a command shell:
Go to your Websphere install.
Go to the bin directory.
wasprofile -unaugment -profileName <profile_name>
wasprofile -delete -profileName <profile_name>
Problem: During a logon process to SQL server the following error may appear: “Login failed for user ‘username’. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)”.
Cause (for me anyway): The SQL server has been configured to operate inĀ “Windows Authentication Mode (Windows Authentication)” and doesn’t allow the use of SQL accounts.
Solution: Change the Authentication Mode of the SQL server from “Windows Authentication Mode (Windows Authentication)”
to “Mixed Mode (Windows Authentication and SQL Server Authentication)“.
How: