Jamie's Blog

PeopleSoft: Could not create shared cache (0,0)

Problem:

When trying to sign into PeopleSoft the error Could not create shared cache (0,0)

Resolution:

Verify there is enough free space on the  file systems
Common directories to look at: * /u01/app/ptools849/psoftXXX/appserv/XXXX%APPDOMAIN%/LOGS
You can also run “df -m|more” when inside of /u01/app/ptools849/psoftXXX to see which directories are using the most space

Change Assistant PSEMAgent clear peer ids and cleanup

Problem:

Having issues with PSEM Agent and environments not showing up. Browsing to the hub website “http://XXXXX.XX.com/PSEMHUB/hub” there are many items listed that do not exist anymore.

Solution:

The Following will cleanup the files and afterwards you should be able to start the agents and see the environments in change assistant without any problems

@ECHO OFF
REM *********
REM The File clears the contents of the EMF Hub and Agents and Change Assistant
REM *********
PIA ServicePeoplesoftStart

Rem THIS IS FOR THE PC RUNNING CHANGE ASSISTANT
move “C:\Program Files\PeopleSoft\Change Assistant\envmetadata\data\matchers.xml” c:\matchers.xml
del /q /s “C:\Program Files\PeopleSoft\Change Assistant\envmetadata\data\*.*”
move c:\matchers.xml “C:\Program Files\PeopleSoft\Change Assistant\envmetadata\data\matchers.xml”
rmdir /q /s “C:\Program Files\PeopleSoft\Change Assistant\envmetadata\PersistentStorage\”
rmdir /q /s “C:\Program Files\PeopleSoft\Change Assistant\envmetadata\scratchpad\”
rmdir /q /s “C:\Program Files\PeopleSoft\Change Assistant\envmetadata\transactions\”

REM THIS IS FOR THE AGENTS
move %1\PSEMAgent\envmetadata\data\matchers.xml c:\matchers.xml
del /q /s %1\PSEMAgent\envmetadata\data\*.*
move c:\matchers.xml %1\PSEMAgent\envmetadata\data\matchers.xml
rmdir /q /s %1\PSEMAgent\envmetadata\PersistentStorage\
rmdir /q /s %1\PSEMAgent\envmetadata\scratchpad\
rmdir /q /s %1\PSEMAgent\envmetadata\transactions\

REM THIS IS FOR THE HUB
Stop Peoplesoft PIA Service
rmdir /q /s %1\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data\environment\
rmdir /q /s %1\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data\proxies
del /q /s %1\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data\*.*
rmdir /q /s %1\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\PersistentStorage\
rmdir /q /s %1\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\scratchpad\
rmdir /q /s %1\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\transactions\

HP dv7t Select Edition Series (dv7tse)

HP released their new DV7T series labeled DVT7SE. It has some pretty good specs and I will be purchasing very soon.

Office 2010 Deployment Kit for APPV-V Error: The product key you entered cannot be used on this machine. This is most likely due to previous version Office 2010 trails being installed. (System error: -1073418219)

Problem:

When installing the Microsoft Office 2010 Deployment Kit for APP-V on the Sequencer machine to begin the installs you receive the error: “The product key you entered cannot be used on this machine. This is most likely due to previous version Office 2010 trails being installed. (System error: -1073418219)” .

Resolution:

Verify that the correct key is being used. I was having issues because the key that was given to me was a KMS key when I was supposed to get the MAK key. After providing the PIDKEY= parameter the correct MAK key the Deployment kit installed without any problems.

PeopleSoft Invalid Access ID and password for signon — see your security administrator.

Problem:

When trying to connect to Data mover or Application designer the following error (“PeopleSoft Invalid Access ID and password for signon — see your security administrator.” ) comes up even though you are inputting the correct user/pass combination.

Resolution:

Verify that the connect ID and Connect password is correct in the Configuration Manager. This ID allows PeopleSoft to connect to the database to verify that the user/pass is correct.

HP DV7t disassembly guide

I recently bought a new laptop and needed the guide to get into the heart of the computer. This guide will show you all part numbers and the possibly how to replace it.

Files
HP DV7T Disassembly guide

SharePoint Report Error: Cannot create a connection to data source ‘dataSource1’.

Problem:
You recieve the following error when running a report from report builder.

Report Execution error the report might not be vaild or the server could not process the data.
for more information about this error navigate to the report server on the local server machine, or enable remote errors
—-
Cannot create a connection to data source ‘dataSource1’.
—
An error has occurred during report processing.

Resolution
In my case the problem was the login that was used when running the report did not have access to the catalog and the sql server. I granted the correct access to the databases in sql manager and the user was able to run the report.

PeopleSoft Error Crystal Reports Print Engine error text: Error in File e:\XX\XX.rpt: Access to report file denied. Another program

Problem:

PeopleSoft Crystal Report was not processing and error out. Looking at the message log I noticed the following messages:
Crystal Reports Print Engine error text: Error in File e:\ptools849\psofthcm\crw\eng\pbc_0004.rpt:
Access to report file denied. Another program

looking at the crystal trace file to view more detailed information I noticed:
4     328    37007      05/07/10 10:04:02   Using report: E:\PTOOLS849\PSOFTHCM\CRW\ENG\PBC_0004.RPT
5     328    37007      05/07/10 10:04:02   About to RunReport()
6     328    37007      05/07/10 10:04:02   About to open print engine
7     328    37007      05/07/10 10:04:02   Print engine opened. About to open job
8     328    37007      05/07/10 10:04:03   Job opened
9     328    37007      05/07/10 10:04:03   Logon info set
10    328    37007      05/07/10 10:04:03   Parameters: -CTORACLE -CDHCMPRD -COHHARVEY -CPUnavailable -I37007 -RP”PBC_0004″ -OT6  -OP\\server\files\Departments\Finance\Payroll\xxx\xx\x\file-20100507 -LGENG.txt -OF14 -ORIENTL

Resolution:

The report file did exist and access was granted to the report file. However, the output path of the crystal report was on the network share. I had to grant access to the process scheduler service account to write the output file.

PeopleSoft Java Exception: Error while wr ite to file:java.lang.Security Exception: Directory Creation Failed (63,49)

After running a process the Distribution Status goes to Error and the reports/logs do not post. This was occurring for some reason after domain controllers were restarted.

Problem:
4:17:08PM Java Exception: Error while write to file:java.lang.Security Exception: Directory Creation Failed  (63,49)
4:17:08PM SchedulerTransfer Servlet error.

Resolution:

make sure the correct smb file share name is in the correct web profile configuration. We changed the domain name netbios name and it caused our PeopleSoft report repository node that is connected to the DFS to error out.

19D0810A-10000004 error in sftlog.txt log file

Problem:

The following error appears in the sftlog.txt file when trying to refresh or connect to app-v server with app-v client

[05/06/2010 11:12:06:531 MIME ERR] {tid=1154:usr=Jamie}
Failure on Desktop Configuration Server request to URL {rtsp://192.168.29.105:554/} with header {Host: 192.168.29.105
Content-Type: text/xml
AppV-Op: Refresh
} (rc 19D0810A-10000004).

Resolution:

SQL 2008 R2 and APP-V Server are located on the same machine. When we rebooted the server APP-V started before the SQL service causing APP-V service to error out. Configure APP-V service with delayed start or dependency on SQL.

Also seen this error because the firewall was turned on the server and the client PC could not connect to the correct 554 port. Verify the client has some form of communication to the servers ports by telneting into the port and see if you get a TCP connection.