The page cannot be displayed Siebel.
Symptom or Error MessageThe page cannot be displayed. Cannot find server or DNS Error Internet Explorer
Cause
1. Web server was running on an unsupported platform.
2. Microsoft Data Access Components (MDAC) and/or Microsoft Foundation Classes (MFC) not installed or incorrect version installed.
3. With introduction of MR 7.0.4.210, the new extension .swef is used and this extension was not added to the Application Mapping contained in the properties of the virtual directory during installation. This is only valid for virtual directories belonging to the Siebel Industry Product Line; others are configured correctly during installation.
4. When Windows 2000 resolves a name using DNS, it does not necessarily pick the first one in the list. If an external DNS server has been selected for name resolution, the error message appears.
Diagnostic Steps
1. Ensure the operating system is listed in the System Requirements and Supported Platforms guide.
2. Check the SESsetup.log log file in the dedicated client directory to ensure that the DLLs have all been registered successfully.
3. Check if the .swef extension is missing from the application Object Manager virtual directory properties in the Internet Services Manager.
Solution
1. Install the Web Server on a supported operating system.
2. If registration resulted in errors, install the following:
- Microsoft Data Access Components (MDAC)
- Microsoft Foundation Classes (MFC)
3. Add the missing mapping by editing the properties of the relevant Object Manager’s virtual directory in the Internet Services Manager. Add a line containing the .swef extension with the same mapping as the .swe extension. Restart the Web server.
4. Disable any DNS Server not being used by the Siebel Applications on the Client machine as a temporary workaround. For information on the Microsoft fix for this behavior, review the Microsoft Knowledge Base Q286834, ”The DNS Client Service Does Not Revert to Using the First Server in the List”. Microsoft suggests permanently re-configuring the DNS Servers and clients.
5. Carry out the following steps:
- Uninstall Siebel Web Server Extension (SWSE).
- Back up and clean the registry, then reboot.
- Install the supported Microsoft Service Pack and reboot.
- Verify that IIS is running and working, then install the relevant updates.
- Reinstall Siebel Web Server Extensions (SWSE).
Can’t load sscdo80.dll or Can’t load sscdo90.dll
Symptom or Error MessageCan’t load sscdo80.dll or
Can’t load sscdo90.dll
Cause
1. Oracle Client installation was corrupted.
2. Incorrect version of Oracle client installed.
Diagnostic Steps
1. Check the version of the Oracle Client installed in the Siebel Dedicated Client machine.
2. Check the version of the Oracle Client installed in the Siebel Server machine.
3. From the client machine, connect to the database server using SQL*Plus and run both a tnsping and a ping.
4. Ensure the tnsnames.ora file has the correct ConnectString.
5. Ensure the Oracle Client installation directory is in the Windows PATH environment variable and that the ORACLE_HOME environment variable is set correctly.
Solution
Install the correct Oracle Client version (refer to Siebel Systems Requirements and Supported Platforms guide).
Unable to start the web browser for your session
Symptom or Error Message
Unable to start the web browser for your session.
Cause1. Faulty installation of the Dedicated or Mobile Web Clients
2. Incorrect Internet Explorer settings
Diagnostic Steps
Not Applicable
Solution
Uninstall and re-Install the Client.
1. Return browser settings back to the default settings.
2. Re-install operating system or re-image machine.
Failed to install MDAC
Symptom or Error Message
Failed to install MDAC.
CauseThis error message is usually caused by either the presence of the wrong version of MDAC or the presence of software using a conflicting version of MDAC.
Diagnostic Steps
Confirm the installed version of MDAC and ensure that it matches the version listed in the Siebel System Requirements and Supported Platforms guide.
Solution
1. Reinstall the Siebel-supplied version of MDAC.
2. Back-up and delete the SQLSRV32.DLL file in the C:\WINNT\System32 directory. Re-run the Siebel installation. The installer should detect that no MDAC components are installed on the machine and successfully install MDAC.
3. If other solutions fail, re-image the system with the required MDAC version and updated system files.
Exited with error 5004
Symptom or Error Message
Completed Siebel Enterprise Configuration. Exited with error 5004.
Cause1. Error message usually produced during the installation on AIX because of incorrect permissions on the installation files.
2. Missing required AIX runtime libraries (X11.base.common and X11.base.lib).
Diagnostic Steps
1. Ensure that the permissions on the ”siebctl” file are at least ’rwx r-x —’ (750).
2. Confirm that file ””libXext.a”” exists on the server. This file is part of the fileset X11.base.lib and physically resides in /usr/lpp/X11/lib/R6/ with a symbolic link in /usr/lib. Ensure the file ”libXext.a” is in the correct directories with permissions set to ’rw- r– r–’ (644).
Solution
1. Set the correct permissions on the siebctl file. Prior to setting the server configuration during the install_server process, open a new shell and set the permissions on /bin/siebctl to ’rwx r-x r-x’ (755), then continue with the server configuration. Do not set the sticky bit.
Change Request # 12-4K12M7 addresses the problem with the sticky bit set.
2. Install the AIX runtime libraries (X11.base.common and X11.base.lib.
3. Use the Server Configuration Utility to reconfigure the Siebel server
4. Change following parameter :
setenv LDR_CNTRL=LOADPUBLIC@MAXDATA=0×60000000
Refer to Alert 471 on SupportWeb for more information.
Object expected
Symptom or Error Message
… Object Expected …
Cause
1. Mixed maintenance release versions on components
2. Incorrect permissions on the /home/siebel/SWSE/public directory, often for the Web server Administrator (IWAM__)
3. Missing JavaScript (.js) files from the \SWEApp\PUBLIC\SCRIPTS directory
Diagnostic Steps
1. Verify the maintenance release versions of each Siebel component in the enu.txt file in the root directory e.g. Siebel Server: \siebesrvr\enu.txt.
2. Refer to ”Alert 388: Additional permissions required with Siebel Web Server Extensions on Siebel 7 eBusiness applications”.
Solution
1. Install the same maintenance release version on each component.
2. Copy the JavaScript (.js) files in the \SWEApp\PUBLIC\SCRIPTS folder from another similar environment. Stop and re-start the Siebel Gateway, Server and Web Server Services.
HTTP 500 – Internal Server error
Symptom or Error Message
HTTP 500 – Internal Server error.
Cause1. Incorrect permissions on the /home/siebel/SWSE/public directory, often for the Web server Administrator (IWAM__)2. Cannot find the eapps.cfg file.
Diagnostic Steps and Solution
Refer to ”Alert 388 on SupportWeb: ’Additional permissions required with Siebel Web Server Extensions on Siebel 7 eBusiness applications’ ”.
No comments :