EPMA Dimension server won't start using SSL enabled Database

Has anyone had any luck configuring EPMA 11.1.2.2 or 11.1.2.1 EPMA Dimension server with a JDBC SSL connection? I am using the following url to configure my SSL-enabled database:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=slc00qox)(PORT=1529))(CONNECT_DATA=(SERVICE_NAME=slc00qox.us.oracle.com)))
and the Dimension server won't start. Other Foundation, Essbase and Reporting repository connections work with same URL. Getting an error in Event Log:
Service cannot be started. Hyperion.DimensionServer.Interface.Exceptions.EPMAServiceException: Cannot initialize the Session Manager. ---> Hyperion.CommonServices.Exceptions.SessionManagerException: Session Manager could not start because database connectivity could not be established. ---> Oracle.DataAccess.Client.OracleException ORA-12537: TNS:connection closed at Hyperion.DimensionServer.SessionManager.SessionManager.InitializeSqlConnectionString()
--- End of inner exception stack trace ---
at Hyperion.DimensionServer.SessionManager.SessionManager.InitializeSqlConnectionString()
at Hyperion.DimensionServer.SessionManager.SessionManager.Initialize(String configFileName, Boolean restorePastInstanceSessions, Boolean enableCaching)
--- End of inner exception stack trace ---
at Hyperion.DimensionServer.Service.Main.InitializeSessionManager()
at Hyperion.DimensionServer.Service.Main.Start()
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
AND
[EPMA Server Startup] ERROR SVR_ERR_PROCESSMGR_CANT_INIT_SESSIONMGR:Cannot initialize the Session Manager.Hyperion.DimensionServer.Interface.Exceptions.EPMAServiceException: Cannot initialize the Session Manager. ---> Hyperion.CommonServices.Exceptions.SessionManagerException: Session Manager could not start because database connectivity could not be established. ---> Oracle.DataAccess.Client.OracleException ORA-12537: TNS:connection closed at Hyperion.DimensionServer.SessionManager.SessionManager.InitializeSqlConnectionString()
--- End of inner exception stack trace ---
at Hyperion.DimensionServer.SessionManager.SessionManager.InitializeSqlConnectionString()
at Hyperion.DimensionServer.SessionManager.SessionManager.Initialize(String configFileName, Boolean restorePastInstanceSessions, Boolean enableCaching)
--- End of inner exception stack trace ---
at Hyperion.DimensionServer.Service.Main.InitializeSessionManager()
at Hyperion.DimensionServer.Service.Main.Start()

As you have backup you can try this:
Restore your master database backup to another instance of SQL Server and in the "To
database:" section of the Restore Database dialog box, use an alternate database name such as "recover_master" to avoid conflict with the master database on this instance of SQL Server. This will cause the mdf/ldf to be named "recover_master.mdf"
and "recover_master_1.ldf". Then detach the
recover_master database, go into the file system, copy the recover_master.mdf and recover_master_1.ldf to the instance of SQL Server with the corrupt master database. Delete the corrupt master.mdf and mastlog.ldf files, rename recover_master.mdf to master.mdf,
and rename recover_master_1.ldf to mastlog.ldf. Now you're ready to try starting the SQL Server service again!
http://blogs.technet.com/b/fort_sql/archive/2011/02/01/the-easiest-way-to-rebuild-the-sql-server-master-database.aspx
Once master is online you can restore other database.

Similar Messages

I am upgrading to Calendar Server 4.0 on NT with more than 9 nodes (or I already have) and my server won't start

I am upgrading to Calendar Server 4.0 on NT with more than 9 nodes
(or I already have) and my server won't start.

The steps are the same whether you have already upgraded or are about to.

Calendar Server 4.0 on the Windows NT platform can only support up to nine
nodes on one server, while 3.51 supported up to 14. If you have a Calendar
Server 3.51 with more than 9 nodes that you want to upgrade to Calendar Server
4.0, Netscape recommends that you migrate the extra nodes to another Calendar
Server 3.51 on another Windows NT system. To accomplish this:
<OL>
<LI>Install Calendar Server on another Windows NT machine and configure it to
use the same directory server as your current Calendar Server.
<LI>Stop and backup your current Calendar Server.
<LI>Individually zip up the node directories you want to move to the new
server. (drive:\unsers\unison\db\Nx
where "x" is the number of the node you want to use.)
<LI>Stop the new Calendar Server.
<LI>Unzip the files into the new Calendar Server in the same place as they
were on the old server.
<LI>Edit the unison.ini
file on the new server to add the nodes you have just migrated.
<LI>Edit the unison.ini
file on the old server to remove the nodes you have moved to the new server.
<LI>Edit the nodes.ini
file on the old server to remove the nodes you just moved and then add them
with the new hostname. Keep in mind that you will only be able to modify the
node network from the old host.
<LI>Run unidbfix -export
on both servers for all nodes.
<LI>Edit the remotenodes.ini
file on both servers to reflect your node topology.
<LI>Run unidbfix -import
to import the changes into the node databases.
<LI>Run unidbfix -c,
then -f,
then -c
again on both servers for all the nodes.
<LI>If you don't get any errors, run uninode -test all
to test if your nodes connections are set properly. If they are not, do not
start either of the servers; instead, fix the errors and try again.
<LI>Start both servers.
<LI>Log in and check to see if you can see people on remote nodes.
<LI>Notify the users on the moved nodes of their new calendar host.
<LI>If you did this in preparation of an upgrade, you can now run the upgrade to
4.0 since both servers contain fewer than 9 nodes.
</OL>

Use Disk Utility whihc is in the Utilities Folder.
Select your Boot Disk on the left.
Select Verify Permissions
If any errors the do Reapir permissions.
You might have to repeat the process.
see this:
Steve

After Setting Up SSO Managed Server Won't Start

I am using the Oracle supplied white paper to set up SSO using Active Directory. Following those instructions everything was working and testing correctly until I added the NegotiateIdentityAsserter provider to the list of WLS providers. Now the managed server won't start. The admin server starts without any errors and goes to the RUNNING state. But the Start BI Services command window gets to the wls.alive: prompt and hangs. And hangs. Eventually the window goes away and it may throw an error but I've never seen it. You can login to the WLS console and EM without a problem. Remove the new provider and everything comes up normally. I have looked at the krb5.ini and krb5login.conf files and even rewritten them from scratch without any change in behavior.
While looking for answers I ran into the SPNEGOCheck webapp that Oracle makes available to diagnose problems. It says everything is OK until it parses the krb5login.conf and then complains that the Username associated with SPN in AD is blank and so doesn't match the SPN specified in the krblogin config. But I can't see anything wrong in the files themselves.
from the log:
In section 'libdefaults'
LSA: Found Ticket
LSA: Made NewWeakGlobalRef
LSA: Found PrincipalName
LSA: Made NewWeakGlobalRef
LSA: Found DerValue
LSA: Made NewWeakGlobalRef
LSA: Found EncryptionKey
LSA: Made NewWeakGlobalRef
LSA: Found TicketFlags
LSA: Made NewWeakGlobalRef
LSA: Found KerberosTime
LSA: Made NewWeakGlobalRef
LSA: Found String
LSA: Made NewWeakGlobalRef
LSA: Found DerValue constructor
LSA: Found Ticket constructor
LSA: Found PrincipalName constructor
LSA: Found EncryptionKey constructor
LSA: Found TicketFlags constructor
LSA: Found KerberosTime constructor
LSA: Finished OnLoad processing
Config name: C:\Windows\krb5.ini
KdcAccessibility: reset
KdcAccessibility: reset
Reachable? true
Connection seems to have succeeded.
Parsing section contents 'com.sun.security.jgss.krb5.accept { com.sun.security.auth.module.Krb5LoginModule required principal="[email protected]" keyTab=biwhse1a.keytab useKeyTab=true storeKey=true debug=true;};'
Section name: 'com.sun.security.jgss.krb5.accept'
Getting next NV pair beginning at 'principal="[email protected]" keyTab=biwhse1a.keytab useKeyTab=true storeKey=true debug=true'
NVPair name: 'principal' value: '[email protected]'
NVPair name: 'keyTab' value: 'biwhse1a.keytab'
NVPair name: 'useKeyTab' value: 'true'
NVPair name: 'storeKey' value: 'true'
Got back 4 name/value pairs.
section com.sun.security.jgss.krb5.accept should probably contain a setting for debug=true
Section com.sun.security.jgss.krb5.accept seems OK
The krb5.ini file:
[libdefaults]
default_realm = SRS1.COM
default_tkt_enctypes = des-cbc-crc
default_tgs_enctypes = des-cbc-crc
ticket_lifetime = 600
[realms]
SRS1.COM = {
kdc = 129.58.120.200
admin_server = adc01.srs1.com
default_domain = SRS1.COM
[domain_realm]
.srs1.com = SRS1.COM
[appdefaults]
autologin = true
forward = true
forwardable = true
encrypt = true
The krb5login.conf file:
com.sun.security.jgss.krb5.accept {
com.sun.security.auth.module.Krb5LoginModule required
principal="[email protected]"
keyTab=biwhse1a.keytab
useKeyTab=true
storeKey=true
debug=true;
[D:\] setspn -L bi_kerb_prin
Registered ServicePrincipalNames for CN=bi_kerb_prin,OU=Non-Person Users,OU=WRC Users,DC=srs1,DC=com:
HTTP/biwhse1a.srs1.com
HTTP/biwhse1a
[D:\]
OBIEE 11.1.1.6.2 BP2
Windows Server 2008 SP1

Did you try -Djava.security.krb5.conf=<path>/krb5.conf before the %EXTRA_JAVA_PROPERTIES%. in your C:\OBI\user_projects\domains\bifoundation_domain\bin\setDomainEnv.cmd .?
Also change your JAAS config file and try with
com.sun.security.jgss.krb5.initiate {
com.sun.security.auth.module.Krb5LoginModule required
principal="HTTP/[email protected]"
keyTab=biwhse1a.keytab
useKeyTab=true
storeKey=true
debug=true;
com.sun.security.jgss.krb5.accept {
com.sun.security.auth.module.Krb5LoginModule required
principal="HTTP/[email protected]"
keyTab=biwhse1a.keytab
useKeyTab=true
storeKey=true
debug=true;
Now restart and see.
Hope this helps. Pls mark if it does.
Thanks,
SVS
Edited by: SSVS on Mar 17, 2013 11:47 PM

Wrong JRE Runtime Lib Path on Win2K--Admin Server Won't Start

Running Sun One Web Server 6.0 SP6 on a Windows 2000 server, I inadvertently entered a typo in the iPlanet Administration Server's Global Settings, "Configure JRE/JDK Paths" link.
In the "JRE Runtime Lib Path" field I typed "jjk1.3.1_03" instead of "jdk1.3.1_03". Now the Sun One web server won't start, so I can't go into the Administrative Server to fix the Jre Runtime Lib Path. I havent' been able to find any file where I can change that erroneous setting either. Is it a Registry entry?
I also tried adding the correct JRE Runtime Lib Path at the end of the Windows PATH environment variable on the server, but that didn't help.

Yes we checked the Registry settings and fixed the typo in the path associated with the key NSES_JRE_RUNTIME_LIBPATH. That should have fixed the problem, but the Sun One web server still wouldn't start.
Moved to plan B and removed then reinstalled the Sun One web server. Now it starts and all is well.
Thanks for helping everyone. This also raised the issue for us of whether or not we are entitled to individual support from Sun since we paid for the Sun One web server. According to the web site, the answer is NO - unless we pay $3,000 for a support contract. Other vendors who recommended using Sun One with their products say YES. We're still tracking that down.

X server won't start after recent catalyst-test and kernel upgrade

Hi,
after recent upgrade of catalyst-test (13.2) and kernel (3.7.5), my x server won't start with this log (WW) and (EE) only:
[ 114.989] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 116.077] (WW) Falling back to old probe method for fglrx
[ 116.093] (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
[ 116.101] (EE) fglrx(0): DAL initialization failed!
[ 116.101] (EE) fglrx(0): Display Infrastructure Failed
[ 116.101] (EE) fglrx(0): PreInit failed
[ 116.212] (EE) Screen(s) found, but none have a usable configuration.
[ 116.212]
Fatal server error:
[ 116.212] no screens found
[ 116.212] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 116.212] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 116.212] (EE)
[ 116.515] Server terminated with error (1). Closing log file.
My card is mobility radeon hd 5700, I'm running on x86_64 system. I'm using aticonfig generated xorg.conf. I will provide any other information if needed.
I've tried:
- to downgrade to catalyst 12.8 and xorg 1.12 (screen just freezes after trying to get to X, only poweroff button works (system catches the signal and shuts down softly - no errors in Xorg.0.log))
- to use catalyst-total 13.1 / catalyst-generator 13.1 (Xorg.0.log says something about *not* compatible module - i can try it again and give you the whole log, it is probably another problem)
- to use open-source drivers (poor performance, overheating)
- to check nomodeset option (present at all kernel images in generated grub.cfg)
Unfortunately, I could not find any similar issue solved in past few days...

Downgrading kernel to 3.7.4 actually worked for catalyst 13.1. Anyone knows what could be wrong for linux 3.7.5?
Edit: catalyst-test 13.2 beta works with linux 3.7.4.
Last edited by sirkubador (2013-02-05 14:24:44)

Server won't start/Bad JVM?

Running CFMX7.02. After noticing that the Java version was
1.4 something (the version originally supplied with the product in
2006), and that I couldn't do things like use the "browse server"
controls in CFAdministrator without getting Java errors, I
repointed the CF engine to use the version supplied by Java on
their website today. Now the server won't start.
From the CF error log:
Error: no `server' JVM at `C:\Program
Files\Java\jre1.6.0_03\bin\server\jvm.dll'.
Windows event log is no help, reporting that is has received
"server-specific error code 2". Based on the advice of some earlier
topic, I tried to restart the service with "interact with the
Desktop" checked, but no DOS window there.
Any ideas? I'd be happy to point CF back to its own version
of Java, if I could do so without interacting with the
Administrator (which requires starting the server).

quote:
Originally posted by:
JR "Bob" Dobbs
1. CF 7 does not support JVMs higher than 1.4.x
Ah. That explains
that.
quote:
2. You should install the full JDK so you'll get the server
version of the JVM
3. You change change the JVM version by editing the
jvm.config file.
Got it--and thanks for the extremely quick reply.
However, what can I do to fix the Java errors that keep me
from using the GUI file-browsing components in the CFAdministrator,
since I can't upgrade the main Java engine?

Is server authentication mandatory for using SSL?

Is server authentication mandatory for using SSL sockets, or is there a way around it?
In other words, how can I take advantage of SSL sockets without dealing with any kind of certificates? Do I have any other options?

Ok folks, I found my answer.Here�s the deal.
Here are some helpful sites: I hope they will also help you understand this topic better and make your life little easier.
//====================================
http://www.onjava.com/pub/a/onjava/2001/05/03/java_security.html
http://www-105.ibm.com/developerworks/education.nsf/java-onlinecourse-bytitle/96B42A25DD270CA886256BAA006351B4?OpenDocument
http://www.ddj.com/documents/s=870/ddj0102a/rl1
//====================================
Neither Server nor Client authentication is mandatory. However, if you don�t use proper ciphersuite (that doesn�t require any authentication), the connection will die so to avoid this problem, you need to enable those ciphersuites manually. Read on.
In most modes, SSL encrypts data being sent between client and server and also provides (optional) peer authentication.
These kinds of protection are specified by a "cipher suite", which is a combination of cryptographic algorithms used by a given SSL connection. During the negotiation process, the two endpoints must agree on a ciphersuite that is available in both environments. If there is no such suite in common, no SSL connection can be established, and no data can be exchanged.
The cipher suite used is established by a negotiation process called "handshaking".
There are two groups of cipher suites which you will need to know about when managing cipher suites:
� Supported cipher suites: all the suites which are supported by the SSL implementation. This list is reported using getSupportedCipherSuites.
� Enabled cipher suites, which may be fewer than the full set of supported suites.
This group is set using the setEnabledCipherSuites method, and queried using the getEnabledCipherSuites method. Initially, a default set of cipher suites will be enabled on a new socket that represents the minimum suggested configuration.
Implementation defaults require that only cipher suites which authenticate servers and provide confidentiality be enabled by default. Only if both sides explicitly agree to unauthenticated and/or non-private (unencrypted) communications will such a ciphersuite be selected.
When SSLSockets are first created, no handshaking is done so that applications may first set their communication preferences: what cipher suites to use, whether the socket should be in client or server mode, etc. However, security is always provided by the time that application data is sent over the connection.
The suite is chosen based upon the credentials that each side possesses and suites that each side supports. For example, a server can�t support an RSA cipher suite unless it has an available RSA private key.
The client and server must support at least one common cipher suite in order to communicate; if they both support multiple ciphers, the strongest available suite will be chosen.
The strings are part of the SSL specification and are defined as:
SSL_<key exchange algorithm>with<encryption algorithm>_<hash algorithm>
When a number appears in the encryption algorithm, it refers to the key strength of the encryption: higher numbers are more secure.
setEnabledCipherSuites(String[] suites) method controls which particular cipher suites are enabled for use on this connection.
� The cipher suites must have been listed by getSupportedCipherSuites() as being supported.
� Even if a suite has been enabled, it might never be used if no peer supports it, or the requisite certificates (and private keys) are not available.
getSupportedProtocols(): Returns the names of the protocols which could be enabled for use on an SSL connection.
setEnabledCipherSuites(String[] suites): Controls which particular cipher suites are enabled for use on this connection.
Let me give you some code that will help you understand little better.
One is Client.java for the client and the other one is Server.java for the server.
Compile and run them in two separate consoles.
( By the way, I assume that you have properly installed JSSE on your system.)
//===== Client.java: ===================================================
import java.io.*;
import java.net.*;
import javax.net.ssl.*;
public class Client
 public static void main(String[] args)
 (new Client()).doIt();
 }//end main
 private void doIt()
 int port = 3333;
 String host = "localhost";
/* String[] enable = {"SSL_DH_anon_WITH_RC4_128_MD5",
 "SSL_DH_anon_WITH_DES_CBC_SHA",
 "SSL_DH_anon_WITH_3DES_EDE_CBC_SHA",
 "SSL_DH_anon_EXPORT_WITH_RC4_40_MD5",
 "SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA"};
*/ try
 SSLSocketFactory sslFact =
 (SSLSocketFactory)SSLSocketFactory.getDefault();
 SSLSocket s =
 (SSLSocket)sslFact.createSocket(host, port);
 //String[] suites;
 //Get all the default CipherSuites
 System.out.println("\n*** Default CipherSuites ***\n");
 String [] defaultSuites=sslFact.getDefaultCipherSuites();
 for(int i = 0; i<defaultSuites.length; i++)
 System.out.println("["+i+"] Default CipherSuite ="+defaultSuites);
 //Get all the supported CipherSuites
 System.out.println("*** ================= ***");
 System.out.println("\n*** CipherSuites Enabled by default ***\n");
 String [] enabledSuites=s.getEnabledCipherSuites();
 for(int i = 0; i<enabledSuites.length; i++)
 System.out.println("["+i+"] Enabled CipherSuite="+enabledSuites[i]);
 System.out.println("*** ================= ***\n");
 System.out.println("***\n Supported CipherSuites ***\n");
 String [] supportedSuites=sslFact.getSupportedCipherSuites();
 for(int i = 0; i<supportedSuites.length; i++)
 System.out.println("["+i+"]Enabled Supported CipherSuite ="+supportedSuites[i]);
 //Get all enabled CipherSuites
 System.out.println("*** ================= ***\n");
 System.out.println("\n*** Old and Newly enabled Anonymous CipherSuites ***\n");
 //s.setEnabledCipherSuites(enable);
 //Enable all supported CipherSuites
 s.setEnabledCipherSuites(supportedSuites);
 String [] suites=s.getEnabledCipherSuites();
 for(int i = 0; i<suites.length; i++)
 System.out.println("["+i+"] Newly enabled Anonymous CipherSuites="+suites[i]);
 System.out.println("*** ================= ***\n");
 System.out.println(" The strongest available CipherSuite is chosen by the System.");
 System.out.println(" But it has to be enabled first, otherwise it ignores it. ");
 System.out.println("Currently Selected CipherSuite = "+s.getSession().getCipherSuite()+"\n");
 System.out.println("*** ================= ***");
 // Send messages to the server through
 // the OutputStream
 // Receive messages from the server
 // through the InputStream
 OutputStream out = s.getOutputStream();
 InputStream in = s.getInputStream();
 PrintWriter p = new PrintWriter(out);
 p.println("Hi Buddy!");
 p.println("Wanna have a beer?");
 p.println("All right, let's have some.");
 p.flush();
 out.close();
 in.close();
 s.close();
 catch (IOException e)
 System.out.println(""+e);
}//end class
//===== Here's Server.java ==============================================
import java.io.*;
import java.net.*;
import javax.net.ssl.*;
public class Server
 public static void main(String[] args)
 (new Server()).doIt();
 }//end main
 private void doIt()
 int port = 3333;
 SSLServerSocket ss;
 String[] enable = {"SSL_DH_anon_WITH_RC4_128_MD5",
 "SSL_DH_anon_WITH_DES_CBC_SHA",
 "SSL_DH_anon_WITH_3DES_EDE_CBC_SHA",
 "SSL_DH_anon_EXPORT_WITH_RC4_40_MD5",
 "SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA"};
 try
 SSLServerSocketFactory sslSrvFact =
 (SSLServerSocketFactory)
 SSLServerSocketFactory.getDefault();
 //Get all the default CipherSuites
 String [] suites=sslSrvFact.getDefaultCipherSuites();
 for(int i = 0; i<suites.length; i++)
 System.out.println(""+i+". DEFAULT CIPHER SUITE="+suites[i]);
 suites=sslSrvFact.getSupportedCipherSuites();
 for(int i = 0; i<suites.length; i++)
 System.out.println(""+i+". SUPPORTED CIPHER SUITE="+suites[i]);
 System.out.println("*** ================= ***");
 ss =(SSLServerSocket)sslSrvFact.createServerSocket(port);
 suites=ss.getEnabledCipherSuites();
 for(int i = 0; i<suites.length; i++)
 System.out.println(""+i+". ENABLED CIPHER SUITE="+suites[i]);
 ss.setEnabledCipherSuites(enable);
 suites=ss.getEnabledCipherSuites();
 for(int i = 0; i<suites.length; i++)
 System.out.println(""+i+". NEW ENABLED CIPHER SUITE="+suites[i]);
 System.out.println("*** ================= ***");
 SSLSocket c = (SSLSocket)ss.accept();
// ServerSocket ss = new ServerSocket(port);
// Socket c = ss.accept();
 OutputStream out = c.getOutputStream();
 InputStream in = c.getInputStream();
 BufferedReader br = new BufferedReader(new InputStreamReader(in));
 // Send messages to the client through
 // the OutputStream
 // Receive messages from the client
 // through the InputStream
 while(true)
// int i = in.read();
 String inputString = br.readLine();
 if(inputString != null)
 System.out.println(inputString);
 else
 out.close();
 in.close();
 c.close();
 ss.close();
 catch (IOException e)
 System.out.println(""+e);
}//end class
//========= Good Luck! ===================

Report Application Server won't start. CCM always says Starting....

I am complete newbie to doing admin for Crystal Servers, forgive the question:
(Win Server 2003 r 2 / CR XI)
Report Application Server won't start which is preventing other servers from starting in CCM.
Reboot machine several times and still having the issue.
Get an error msg in Windows before login window appears stating that the crystalras.exe application requested a runtime to terminiate in an unusual way (.Net error).
I get the following error msg in my event viewer.
From Event Viewer:
Event Type: Error
Event Source: BusinessObjects_crystalras
Event Category: Startup
Event ID: 33000
Date: 7/27/2010
Time: 4:24:34 PM
User: N/A
Computer: CRYSTAL
Description:
Failed to start the Report Application Server.
From Logging:
Timestamp ProcessID ThreadID Message
Tue Jul 27 20:24:34 2010 2496 3176 assert failure: (.\sso_wrapper.cpp:94). (SFileSys::exists(ssPath) && SFileSys::isDir(ssPath) : Platform binaries directory not valid.).
We installed some Windows Server Updates about 3 months ago (at the time, over 70 Windows updates were installed) but, this problem hasn't shown up until 2 or 3 weeks ago. I think a .Net Service Pack might have been part of the updates at that time. When we did the updates, Windows was shutdown and updates installed per the preferred option of Windows. But now when rebooting since that time, the server continually reccomends the install updates and shutdown option. Do we need to rollback the server to date prior those updates if possible?
I have also uninstalled .Net Framework back to 2.0. Is 1.0 or 1.1 the max that will work with XI?
Should I also try to uninstall all other Windows updates?
Thanks in advance for any help, Ed

Post this query to the [Business Objects Enterprise Administration|BI Platform; forum.

X200S won't start using a battery

X200s works fine when connected to AC but won't start using the battery. The on button has no impact, no indicator lights , nothing. I have tried it with two different batteries, in both cases the battery condition shows good and fully charged in Lenovo Power Manager - any ideas?

The fuses are not considered replaceable. They are soldered to the motherboard and are not a job for a "radio shack" soldering iron. A quartz preheater and a temperature controlled rework station is the minimum equipment you would need. It requires a complete disassembly to determine whether the problem is a fuse or something else. I do not have an x200s motherboard to look at to be sure, but the charging fuse for the main battery is usually near the battery connector. I will add that the problem you describe more likely to be a power transistor than a fuse, unless there was some sort of event that happened at the time it stopped working.

Messaging Server won't start up, or acts strangely

One of the config files has disappeared, or the Messaging Server
is acting "strangely".

Because of bugs in the Berkeley DB code, it is possible for a configuration
file to become corrupted. The Messaging Server will remove a severly
corrupted config file, but there is a threshold of corruption that may
impact server operation and may not cause files to be deleted.

If you notice that one of the config files is gone (your server won't start),
or that your server is acting strangely, DO NOT REPLACE IT WITH A BACKUP COPY.
This will most likely re-introduce the corruption. Instead, make note of
all the configuration changes you've made with the Messaging Server admin gui.
The easiest way to do this is to print out each page. Then replace the
config file with a clean one from the install directory or from the media.

Before re-starting the server, check each admin gui page to make sure it
matches your printout, and make any necessary changes. Then start the server.

The installed configuration files are located in the message spool area,
by default: /var/spool/postoffice/config and they are: 

Account-Handler 
Account-Manager 
AutoReply-Handler 
Configuration-Manager 
Dispatch 
Error-Handler 
Finger-Server 
IMAP4-Server 
MTA-Accounts 
Mailbox-Deliver 
POP3-Server 
Program-Deliver 
SMTP-Accept 
SMTP-Deliver 
SMTP-Router 
UNIX-Deliver 

Un-configured copies of all these files may be found under the directory
you installed the server at:

/install/server/data 

The fresh files will all have a .install appended to them.

Shut the computer dow, remove the power cord and all peripherals, wait for 30 seconds, replace the power cod and press the start button at the same time.
If you do not have the iSight, try the steps in [this|http://docs.info.apple.com/article.html?artnum=300908] Apple article.

Logitech Media Server won't start

Hi,
Logitech Media Server won’t start after I clean installed 10.10.1 and migrated my user data from time machine. I tried tuned of firewall and clean install LMS many times and tried different version of LMS from 7.7.4 to 7.9 but none of them worked.
I builded a new user account for testing, LMS works well in this new user account.
Is there anything I can do to fix my old user account?
Thank you.

Thank you very much! I did not know about the nightly builds. LMS has pretty much worked throughout the years; it may have needed an update now and then but I never had to go looking for beta versions.
I held off upgrading my Mac Pro -- which acts as a server for iTunes and other things around the house -- to Yosemite until today. All was well except for getting LMS to start. I was pretty bummed at the prospect of not having my tunes on my Squeezebox radio. In any case, I'm glad I found my answer in 5 seconds here at the Apple forums. Rock on.

RADIUS Server Won't Start

After running Software Update and installing the Security Update 2008-005 and iTunes 7.7.1 on the server, I noticed none of my wireless clients would authenticate. I checked Server admin and the Radius server was not running. Upon trying to start the RADIUS service in Server Admin the Radius server wouldn't start. Could this software update be to blame? Any Ideas?

+The Logs keep repeating the following sequence:+
Sat Aug 2 10:51:33 2008 : Info: Using deprecated naslist file. Support for this will go away soon.
Sat Aug 2 10:51:33 2008 : Info: rlm_exec: Wait=yes but no output defined. Did you mean output=none?
Sat Aug 2 10:51:33 2008 : Info: rlmeaptls: Loading the certificate file as a chain
Sat Aug 2 10:51:33 2008 : Error: rlm_eap: SSL error error:0906A068:PEM routines:PEMdoheader:bad password read
Sat Aug 2 10:51:33 2008 : Error: rlmeaptls: Error reading private key file
Sat Aug 2 10:51:33 2008 : Error: rlm_eap: Failed to initialize type tls
Sat Aug 2 10:51:33 2008 : Error: radiusd.conf[10]: eap: Module instantiation failed.
Sat Aug 2 10:51:33 2008 : Error: radiusd.conf[1954] Unknown module "eap".
Sat Aug 2 10:51:33 2008 : Error: radiusd.conf[1897] Failed to parse authenticate section.

RMI Server exits early when using SSL

Hi,
Maybe someone else has encountered this one.
My RMI server works fine when I use standard sockets. I create an instance and bind it into the rmiregistry. It then waits indefinitely for connections.
When I use SSL, I can create the object instance. I can also bind it into the registry. However, it only waits a few seconds and then exits.
No exception or error is thrown (I have a catch Throwable block on my main method to be sure of this.)
As my code is adapted from the RMI SSL 'Hello World' examples found on this site) I decided to compile and run those examples. I get the same problem.
Any ideas?
This is the relevant part of my code:
public static void main(String[] args)
    HelloImpl obj = null;
    try
        // use -clear option to get standard sockets
        if (args.length > 0 && args[0].equals("-clear"))
            obj = new HelloImpl();
        else // otherwise default to SSL sockets
            RMIClientSocketFactory csf = new RMISSLClientSocketFactory();
            RMIServerSocketFactory ssf = new RMISSLServerSocketFactory();
            obj = new HelloImpl(csf,ssf);
        Naming.rebind("HelloServer", obj);
        System.out.println("HelloServer listening for requests\n";
    catch (RemoteException ex)
        ex.printStackTrace();
    catch (MalformedURLException ex)
        ex.printStackTrace();
    catch (Throwable ex)
        ex.printStackTrace();

Thanks for taking an interest.
I just use:
c:\j2sdk1.4.1_02\bin\rmiregistry
to start the registry.
I think the problem is with my SSL sockets. I'm guessing the reason a UnicastRemoteObject is normally kept alive (not garbage collected) in the registry is because it has a ServerSocket which is waiting for connections.
In this case, I don't think the SSLServerSocket is getting created and so my UnicastRemoteObject gets garbage collected.
However, I'm not sure why exactly.

Solaris 10 Console Server won't start

Pardon this slightly off-topic query, but I don't believe there is a more proper place for it.
Been a while since I've upgraded anything, but I finally installed Solaris 10 on my Ultra 30 (a clean install, replacing Solaris 9). The installation went well, except that when I started up the SMC, it wouldn't connect to the console server. I have stopped and started the console server, but it will never show that it's running. The status is always "Solaris Management Console server not running on port 898". I have seen numerous other folks having the same difficulty, not no solutions so far. Any ideas? I'd hate to roll back to Solaris 9, but without a solution I can't even add any users to the system...at least using the GUI.
Jake Brodersen
Jacob K. Brodersen III
Deputy Director, Test and Operations
Jacobs/Sverdrup

I assume you haven't enabled RBAC and turned root into a role at this point.
Take a look at the useradd man page for a command line level example of adding users.
I just started using Sol10 x86 myself. I haven't tried installing SMC just yet but I'm pretty sure the wbem is a legacy boot script. I looked on my newly installed Sol10 install and port 898 isn't up on my server either. A "svcs -a" command didn't show up services that appear to be SMC console related.
Stupid question - Did you go through the SMC install process on that server ?

Server does not start using Sun Java SE 1.5.0_07

The application server launched with startserv using Sun Java SE 1.5.0_07 , seems to hang (uyner SuSE Linx 10.1), it does not start, and stays forever in startserv. performing a kill -3 for the precess we have:
"process reaper" daemon prio=1 tid=0x08459ab8 nid=0x1bc8 runnable [0xa8c01000..0xa8c01e50]
at java.lang.UNIXProcess.waitForProcessExit(Native Method)
at java.lang.UNIXProcess.access$900(UNIXProcess.java:20)
at java.lang.UNIXProcess$1$1.run(UNIXProcess.java:132)
"Low Memory Detector" daemon prio=1 tid=0x080c7720 nid=0x1bc6 runnable [0x00000000..0x00000000]
"CompilerThread0" daemon prio=1 tid=0x080c6178 nid=0x1bc5 waiting on condition [0x00000000..0xaa2c09b8]
"Signal Dispatcher" daemon prio=1 tid=0x080c5100 nid=0x1bc4 runnable [0x00000000..0x00000000]
"Finalizer" daemon prio=1 tid=0x080b9b88 nid=0x1bc3 in Object.wait() [0xaa3fc000..0xaa3fd0d0]
at java.lang.Object.wait(Native Method)
- waiting on <0xaaa77568> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0xaaa77568> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=1 tid=0x080b8e38 nid=0x1bc2 in Object.wait() [0xaa47e000..0xaa47e150]
at java.lang.Object.wait(Native Method)
- waiting on <0xaaa775e8> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0xaaa775e8> (a java.lang.ref.Reference$Lock)
"main" prio=1 tid=0x0805d5f8 nid=0x1bc0 runnable [0xbfb3a000..0xbfb3b2d8]
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:194)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:254)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
- locked <0xaaa79d20> (a java.io.BufferedInputStream)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
- locked <0xaa591480> (a java.io.InputStreamReader)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
- locked <0xaa591480> (a java.io.InputStreamReader)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at com.sun.enterprise.tools.launcher.ProcessLauncher.sendInputToProcessInput(ProcessLauncher.java:410)
at com.sun.enterprise.tools.launcher.ProcessLauncher.executeBackgroundCommand(ProcessLauncher.java:352)
at com.sun.enterprise.tools.launcher.ProcessLauncher.executeCommand(ProcessLauncher.java:327)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:238)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:158)
"VM Thread" prio=1 tid=0x080b61b0 nid=0x1bc1 runnable
"VM Periodic Task Thread" prio=1 tid=0x080c8bd8 nid=0x1bc7 waiting on condition

The recommended way of starting the application server is to use asadmin command, for ex. <application-server-install-root>/bin/asadmin start-domain. The reason startserv hangs is because it is expecting some input which is automatically provided by the asadmin command.
- sreeni

EPMA Dimension server won't start using SSL enabled Database

Similar Messages

Maybe you are looking for