After upgrading Adobe 9.x to a later version of 9.x, the client crashes on startup.
Fix details: SPR# BJGY83MPB6 This issue is fixed in 8.5.2.
Author: <span>kenio.carvalho</span>
Go to File -> Preferences -> General -> Web Browser
Click in New and fill the form.
Repeat the process for Google Crome and restart the Designer
At the server console type sh stat server. There is a server statistic called “Server.Version.Architecture” that indicates if Domino is 64-bit or not.
The server console will display Server name: Lotus Domino Server (64-bit) at the top of its window
Support for Firefox 4 is introduced in Interim Fix 401.8HF6 for iNotes 8.5.2 Fix Pack 2, which is now available for download from Fix Central. iNotes 8.5.2 Fix Pack 3 will also provide Firefox 4 support. This interim fix can be applied on a Domino server running 8.5.2 Fix Pack 2 or a Domino server running 8.5.2 Fix Pack 2 with a Domino hotfix. If you are running 8.5.2 Fix Pack 2 with an iNotes hotfix, please contact IBM Support to request a new iNotes hotfix that combines iNotes IF 401.8HF6 with your existing iNotes hotfix.
The information above is fron TN 147006
Yesterday the users complaim about this and conclude that it’s a domino fault and my fault.
For several years I received this type of complaint. Every time I researched the problem I found problems with DNS. Lack of PTR record, MX record in error and ultimately a lack of SPF record. . It’s not Domino fault! It’s not my fault!
The fault is always (or almost 99%) the network administrators or DNS administrators.
I use the following in my own DNS to avoid problems:
1 – Use the A record pointing to your Domino Server
2 – Create a PTR record for your Domino Server
3- Create a MX record and setup it pointing to the A record of your Domino Server.
4 – Create a SPF record
Test tool: Mool BXTox
This TN show how to setup password checking and prompt users to change the passwords
Today I solved a problem with my wireless home network. My kid have a PS3 and wants to play online.
The signal strength was not too bad (52%) but the PS3 got some network errors and the kid loses the game.
My solution was to buy another router TP-Link WR941 and link the Linksys WRT54G using WDS.
The problem was that WRT54G doesn’t have support to WDS. To solve this problem go and change the bios of the WRT54G from the LinkSys to
DD-WRT http://www.dd-wrt.com/site/index. Look up for your WRT54G version and follow the instructions.
The WDS setup was easy, just setup the WR941 as usual (basic setup), like next, next and finish. The WR941 was the primary router (gateway to internet), connected to my ADSL and
as a DHCP server for my network, the IP is 192.168.10.1. SSID Springfield2 and WRT54G IP is 192.168.10.2 SSID Springfield1
The two routers need to operate on the same channel and use the same security settings.
To connect the two routers:
Setup WRT54G as a secondary router.
Put the MAC address of the Wireless on the WDS setup
Setup WDS on the TP-Link put the MAC address of the WRT54g here.
How To Speed Up WebSphere Portal Server 7 After the Initial Installation
When any version of WebSphere Portal is first installed, there is always a significant load time for each JSP page. The poor load time is attributed to the fact that each JSP page must be compiled the first time it is accessed. To avoid the delay, execute the precompile-jsp command.
1. Open a command line and navigate to the following directory:
C:IBMWebSpherewp_profilebin
2. Execute the following command (all on one line)
ConfigEngine.bat precompile-jsp –DwasUser=wasadmin –DWasPassword=wasadmin
When you have a portal for a long time (My case since 6.0.0.1) you apply a list of Fix during the life of your portal.
The directory version grows and you need to clean up to free disk space,
I open a PMR and the answer was:
“It is critical that the client does not remove the jar files from the
backup folder. This folder is very important if you decide to uninstall
a fix/fixpack or upgrade to a new fixpack. If you install a fix, say
PM0001 and it affects the portal.jar file. What happens is that the
original portal.jar file is stored in the backup folder and the new
portal.jar is deployed.
So if we have a scenario where the client wants to upgrade to the latest
fixpack and their current Portal has several fixes applied.. when you go
to upgrade, part of the install process is to uninstall those fixes
(thus those jar files that each fix affects are removed and replaced
with the associated backed-up jar files in the backup folder). You will
break Portal and it will be very painful to recover.
The logs folder can be emptied.”