WC not getting publish...

Cause
A previous failed application update has corrupted the applications configuration information.
 Resolving the problem
Perform the following steps to resolve this issue:

1. Stop the server

2. Backup and remove the following directories:
- WCDE_installdir/wasprofile/config/cells/localhost/cus
- WCDE_installdir/wasprofile/config/cells/localhost/blas
- WCDE_installdir/wasprofile/wstemp
- WCDE_installdir/wasprofile/temp
- WCDE_installdir/wasprofile/config/temp
3. Start the server

4. Publish the WebSphere Commerce application.

The above steps clears corrupted server configurations and allows for the publish action to run properly.

Important Note

It is important that you keep a backup of the directories listed above since you may run into issues like few applications such as WAS Admin Console may not be accessible. If you face the same issue, please refer to the steps provided in my post - RESOLVED : Unable to access WAS Admin Console

Alternatively , try just removing the module which is causing problem during publishing - WC

Determining Application Server you are on in Firefox

Determining Application Server you are on in Firefox

1.       Tools -> Options

2.       Click Privacy

3.       Click Show Cookies

4.       Find Nashbar or Performance. (If you type in N or P, it will narrow it so that you can find them)

5.       Find the JSESSIONID Cookie

6.       Select it.

7.       The JSESSIONID should end with :13rdkhjun or : 143c5mheu or :13rdirq71

a.       143c5mheu - .25 (Server3)

b.      13rdirq71 - .13(Server1)

c.       13rdkhjun - .15(Server2)

8.       Based on the ID you know which server you are on.

Changing which Appserver you are on

1.       First start by going into Firefox and going to the following URL to get Add-on for editing the cookie. (https://addons.mozilla.org/en-US/firefox/addon/4510/)

2.       Follow all directions for installing the addon.

3.       Once the addon is installed go to site you want to work with.

4.       Click Tools -> Cookie Editor

5.       You can filter the cookies by typing in Performance or Nashbar

6.       Select Cookie Name JSESSIONID

7.       Click Edit

8.       Change what is after the : to match the application server you want to try.

9.       Click Close refresh the page.

10.   You are now working on that server.