IE9 Save As or Save Target As not working after applying update KB3008923 on Windows 7 SP1 64 Bit machine

Update : After applying the Latest Cumulative Security Update KB3032359 - MS15-018: Cumulative security update for Internet Explorer: March 10, 2015 Save As is working fine again. Also this resolves IE9 Freak Vulnerability as well. 

If you have applied the update KB3008923 , you may not be able to open any Microsoft office document (doc, docx, xls, xlsx, ppt, pptx) etc. Also If you try to download a software and try to use Save As option from the toolbar, it does not work. If you right click on a link and Select Save Target As that also does not work.

This issue is not mentioned on the Microsoft site http://support.microsoft.com/kb/3008923 

Though they recommend manually applying update KB3025945 (

http://support.microsoft.com/kb/3025945) to resolve IE9 Crash issue, it does not fix the issue.

To resolve the issue, I have to uninstall both KB3025945 and KB3008923 and once I did that everything started working normally. I would advise not to install this update till Microsoft come up with a replacement fix using windows update.

This will impact PeopleSoft Excel Query download functionality any word document download.

To uninstall the update, go to Control Panel and Search for “Installed updates” and Select View Installed Updates under Programs and Features

In the Search dialog at the top right type KB3025945 first and then KB3008923 and select uninstall  after right clicking on the selected update. You will need to restart the machine after each update is uninstalled.

(NET.334): Tuxedo cannot find the service RunAeAsync2. Make sure the application server advertising this service is booted.

If your users are calling and telling you that App engine processes are remaining in initiated status for longer time ( > 5 minute) and you observe the following message. (Assuming PSAESRV is configured)

in the $PS_CFG_HOME/appserv/prcs/<domain>/LOGS folder for SCHDLR_MMYY.LOG you will see the message

(NET.334): Tuxedo cannot find the service RunAeAsync2.  Make sure the application server advertising this service is booted.

To see all files that has this message

grep NET.334 SCHDLR*.LOG | cut -d : -f 1 | sort -u

Please note the number at the end of RunAeAsync. It could be 1 thru n depending on number of PSAESRV configured. What this message means that the PSAESRV and number at the RunAeSync is not running for e.g. in this case PSAESRV that provides service RunAeSync2 is not running.

You will also see in the same folder for TUXLOG.MMDDYY the following message

010135.abc.com!restartsrv.16887.414156544.-2: server AESRV/2: CMDTUX_CAT:1684: ERROR: Application initialization failure

010135.abc.com!restartsrv.16887.414156544.-2: server AESRV/2: CMDTUX_CAT:587: INFO: Cannot restart server, scheduling for cleanup

grep CMDTUX_CAT:1684 TUXLOG.*

Resolution

What this means is that for some reason PSAESRV has crashed and Tuxedo restart process is not able to restart PSAESRV process.

You have 2 option 2 fix the issue.

Option 1 : Shutdown and Restart the server

Option 2: Manually start the PSAERV process using command line without shutting down and restarting the server.

Option 2 is preferred, if you have other PSAESRV processes running in process monitor that will be killed if you try to stop the process scheduler.

Start PSADMIN (cd $PS_HOME/appserv; ./psadmin)

Select 2 for process Scheduler

Select 1 for Administer a domain

Select 1for appropriate Process Scheduler Domain

Select 5 for TUXEDO command line (tmadmin)

Type

boot -g AESRV -i 1

(Change -I 1 to appropriate number for PSAESRV process that crashed Determined from the number at the end of RunAeSync).

Observed this issue in PeopleTools : 8.53.12 and Linux : Red Hat 6.3 64 bit.

Unable to find a Routing Corresponding to the incoming Request Message (158,505)

When testing a WSDL or WADL you are getting the above message in the output Unable to find a Routing Corresponding to the incoming Request Message (158,505). for e.g. after publishing the WSDL for Soap or WADL for Rest, you try to view the WSDL or WADL and get the above message. 

1. Make sure that GETWADL and GETWSDL Service Operation which is part of IB_UTILITY Service is active and has any to local routing defined and active. Once you add the missing routing, Go to Routing Definition and Select Parameter Tab and make sure that External alias is exactly GetWADL for GETWADL and GetWSDL for GETWSDL. If it is anything other for e.g. GETWADL or GETWADL.V1 it will not work.

See following My Oracle Support Resolutions 1949257.1 and 1572531.1 for more information.

Sample URL to view WADL and WSDL are

WADL (REST)

http://piahostname.com/PSIGW/RESTListeningConnector/PSFT_PA/PTCS_SECURITY.1.wadl

WSDL (SOAP)
http://piahostname.com/PSIGW/PeopleSoftServiceListeningConnector/PSFT_PA/PTCS_SECURITY.1.wsdl

To find out which WSDL or WADL are published to  WSDL Repository, Do the following Select.

select * from PSIBWSDLDFN;

Note: This is tested in 8.53.09 and 8.53.12 but may be valid for other PeopleTools version as well.

Deleting Rows in ExcelToCI

Go to http://www.cedarhillsgroup.com/knowledge-base/kbarticles/deleting-rows-in-exceltoci to see How to modify delivered ExcelToCI template to delete rows which is not delivered by default. One of the use case is delete roles from user profiles in mass without using backend SQL . This uses delivered USER_PROFILE component interface. Tested in PT 8.53 and works fine. Make sure that you select Action as UPDATEDATA in Connect Information worksheet of ExcelToCI

In Summary, Go to Tools | Macros | Visual Basic Editor

Open StagingAndSubmission Module and Navigate to WriteCollectionHeader function do the following.

You will see a case statement “Select Case lScrollLevel”

Change the “Case 1” statement as PSROLEUSER is in level 1. If your target rows exist in other levels, you will need to modify that Case statement.

sXmlLine = sIndent & "<" & sXmlTag & ">"

To

sXmlLine = sIndent & “<” & sXmlTag & " CINodeAction=""DELETE"">"

Unable to Select or Edit a Field on a Page in Application Designer

On a very long page, we were not able to select the fields towards the bottom of this page. We found the following in PeopleBooks

Home -> PeopleSoft PeopleTools 8.53 -> PeopleSoft Application Designer Developer’s Guide -> Understanding Page Controls -> Data Entry Controls

Note: PeopleSoft Application Designer allows you add up to 405 fields on a page. When you reach this limit, typical system behavior includes being unable to select, move, or edit the page fields with an order number exceeding the 405-field limit. While this limit has no effect on the page at runtime, it has the potential to disrupt productivity during design time. If you find a page nearing the 405-field limit, you should use subpages to decrease the number of fields on a single page.

Below PeopleSoft resolution describes the same issue which is there since Version 8.2

E-AD Is there any limit on the number of fields on a Page Definition ( Doc ID 648823.1 )

Using Sub pages is the easiest way to resolve this issue. However this require changing the code.

The below query can be used to identify any such pages

select pnlname,count(*) from pspnlfield group by pnlname order by count(*) desc

Integration Network WorkCenter Incorrect Formatting after PeopleTools upgrade

After upgrading to PeopleTools 8.53 from 8.50, Integration Network Workcenter in Portal 9.1 application was not displaying properly. The culprit was missing classes from cloned stylesheet. Used the below sql to identify the missing sub style sheets and classes from the cloned stylesheet class and copy them manually.

Screenshot of incorrect formatting.

select * from PSSTYLECLASS a where a.stylesheetname = 'PSSTYLEDEF_SWAN'  and a.styleclassname not in (Select b.styleclassname from  PSSTYLECLASS b
where   b.stylesheetname = 'PREFIX_PSSTYLEDEF_SWAN_PT850')

minus
select * from PSSTYLECLASS a where a.stylesheetname = 'PSSTYLEDEF_SWAN'  and 'PREFIX_' || a.styleclassname || '_PT850'  in (Select  b.styleclassname   from  PSSTYLECLASS b
where   b.stylesheetname = 'PREFIX_PSSTYLEDEF_SWAN_PT850')

Replace the compared to stylesheetname with your custom stylesheet name and also do not overwrite your custom styleclass if any. In this particular instance adding the below class from delivered 'PSSTYLEDEF_SWAN resolved the issue.

STYLECLASSNAME

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

PSAVSCHART

PSCHARTGANTT

PSCHARTSTYLE_FREEFORM

PTAL_SUBSTYLE_REQ_SWAN

PTAL_SUBSTYLE_VL_SWAN

PTWC_SUBSTYLE_SWAN

PT_ACE_SS1_SWAN

Unified Navigation WorkCenter error

If you have upgraded the Portal 9.1 (Portal Interaction Hub or Enterprise Portal) from 8.50 to 8.53 and tried to use the Unified Navigation WorkCenter, You will get the following error.

Navigation : Portal Administration –> Unified Navigation WorkCenter

.arrowlistmenu{width:320px;} .arrowlistmenu .menuheader{font: 10px Arial;color: black;background-color: #FDFDFE;padding: 1px 0px 5px 5px;margin-bottom:2px;cursor: hand;cursor:

To fix this issue , Go to Portal Administration –> Pagelets –> Pagelet Wizard –> Pagelet Wizard

Open Pagelet ID : PAPP_EPPUN_UNPGLT

Navigate to Step 4 Select Display Format and Select Radio button Passthru. It is currently Custom

Click Next (Step 5 of 6) and Press Save.

Retest the Unified Navigation WorkCenter link. The issue should be resolved now.