SQL Server not Starting Up - Could not open error log file system error = 5(Access is denied.)

Hi guys,
I am working on issue with SQL Server 2008 R2 .. we rebooted the server and after that all SQL services is not coming up. below is the error from eventlog...
SQL Server running under NetworkService account and has full control on this files..
from Config Manager ....
The request failed or the service did not respond in a timely fashion....
From Event log..
initerrlog: Could not open error log file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'. Operating system error = 5(Access is denied.).
Any idea or workaround..?
Thanks..
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

Finally I found solution and was able to bring back online the SQL Services...
I had a very similar issue with the following error (event log):
Description:
The SQL Server (MSSQLSERVER) service terminated with service-specific error 17058 (0x42A2).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17058
Date: 19/05/2012
Time: 10:20:14
User: N/A
Computer: NSQLXX
Description:
initerrlog: Could not open error log file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
Operating system error = 5(error not found).
In this case the ERRORLOG file had been marked as read only. This was following a scheduled automated boot. -This
was culprit
MSSQL wouldn't not start until this file had been changed.
http://www.experts-exchange.com/Database/MS-SQL-Server/Q_23951723.html
Thanks everyone for your kind replies and time...
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

Similar Messages

TF255186: The following SQL Server Reporting Services Instance could not be found

Hi,
I'm trying to install TFS 2013 on a remote SQL RS instance.
Using the TFS 2103 U4 installation
SQL 2012 RS, name instance, Server: SQLProdA, Instance Name COMRS
When I enabled tracing using debugView I see the following output:
[4160] [Error @11:07:10.978] Exception Message: TF255186: The following SQL Server Reporting Services Instance could not be found: COMRS. The server name is: SQLProdA. (type TfsAdminException)
Any ideas what the issue is?
Thanks,
reuvy

Hi Charles,
Thanks for the help. I already saw those links, and am already trying with the format. As I wrote above:
Server: SQLProdA, Instance Name COMRS
So I wrote in the box "SQLProdA\COMRS" (without quotes of course) and I still keep getting that error.
I don't know if it matters, but although this is indeed a named instance, nonetheless, the path to the report server uses the default url (ie.
http://servername/reports) as opposed to the name instance version (ie.
http://servername_instance/reports) as mentioned by your link and this post:
https://msdn.microsoft.com/en-us/library/bb552341.aspx
But, I checked with Fiddler on the server and didn't see it trying to even access the link so I don't think it is related. I saw with Process Monitor that it is indeed trying to access via the network resources on SQLProdA, so I know it's trying.
I have noticed something in the past, and wondered if this could be the issue, that for example if I have Management Studio 2014 installed, I cannot connect to a Reporting Services instance which is 2012. Only when Management Studio 2012 is installed
and being used can I connect. I wondered if this possibly could be related, that maybe the API or something else which the installer is using is missing some component to connect to the RS instance.
Just in case, I already installed both the SQL 2012 and 2014 Client Tools Connectivity (although I first installed 2014, and then 2012).
Do you think this could be the issue? If not, do you possibly have any other leads?
Thanks,
Reuvy

SQL Server 2012 Reorg Index Job Blew up the Log File

We have a maintenance plan that nightly (1) runs dbcc checkdb on all databases, (2) reorgs indexes on all databases, compacting large objects, (3) updates statistics, etc. There are three user databases, one large, one medium, one small. Usually it uses
a little more than 80% of the medium database's log, set to 6,700 MB. Last night the reorg index step caused the log to increase to almost 14,000 MB and then blew up because the maximum file size was set to 14,000 MB, one of the alter index commands failed
because it ran out of log space. (Dbcc checkdb step ran successfully.) Anyone have any idea what might cause this? There is one update process on this database, it runs at 3 AM. The maintenance plan runs at 9 PM and completes by 1 AM. The medium database has
a 21,000 MB data file, reserved space is at about 10 GB. This is a SQL 2012 Standard SP 2 running on Windows 2012 Server Standard.

I personally like to shrink the log files once the indexes have been rebuilt and before switching back to full recovery, because as I'm going to take a full backup afterwards, having a small log file reduces the size of the backup.
Do you grow them afterwards, or do you let the application waste time on that during peak hours?
I have not checked, but I see no reason why the backup size would depend on the size of the log file - it's the data in the data file you back up, not the log file.
I would say this is highly dubious.
Erland Sommarskog, SQL Server MVP, [email protected]
Yeah I let the application allegedly "waste" a few milisseconds a day autogrowing the log file. Common, how long do you think it takes for a log file to grow a few GB on most storage systems nowadays? As long as you set an appropriate autogrow
interval so your log file doesn't get too fragmented (full of VLFs), you'll be perfectly fine in most situations.
Lets say you have a logical disk dedicated to log file storage, but it is shared across multiple databases within the instance. Having allocated space for the log files means there will be not much free space left in the disk in case ANY database needs more
space than the others due to a peak in transactional workload, even though other databases have unused space that could have been used.
What if this same disk, for some reason, is also used to store the tempdb log file? Then all applications will become unstable.
These are the main reasons I don't recommend people blindly crucify keeping log files small when possible. I know there are many people who disagree and I'm aware of their reasons. Maybe we just had different experiences about this subject. Maybe people
just haven't been through the nightmare of having a corrupted system database or a crashed instance because of insuficient log space in the middle of the day.
And you are right about the size of the backup, I didn't put it correctly. It isn't the size of the backup that gets smaller (although the backup operation will run faster, having tested this myself), but the benefit from backing up a database with a small
log file is that you won't need the extra space to restore it in a different environment such as a BI or DEV server, where recuperability doesn't matter and the database will be on simple recovery mode.
Restoring the database will also be faster.
Just because there are clouds in the sky it doesn't mean it isn't blue. But someone will come and argue that in addition to clouds, birds, airplanes, pollution, sunsets, daltonism and nuclear bombs, all adding different colours to the sky, this
is an undocumented behavior and should not be relied upon.

Failure when connecting MS SQL SERVER from ODI ! could not load JDBS driver

i have some trouble with connecting MS SQL SERVER from ODI.
I have already downland jdbs driver 3.0 (and 2.0 ) and copy the sqljdbc4.jar to D:\oracle\product\11.1.1\Oracle_ODI_1\oracledi\agent\drivers( where the oracle jdbs driver is already exitst )....but i have this error :
could not load JDBS driver class..
thanks

After more investigation and even more chocolate, we've identified the problem and it's now working. For anyone else who strikes this problem in future, here's something to check/consider/try:
Even though Squirrel SQL Client was connecting and working ok using the MS JDBC driver (v 3.0), it recorded this in its logs:
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the INTERSECT operation.
We've found that the open source jTDS driver does not have the same issue as the Microsoft one.
We've installed the current jTDS driver, recorded the driver name (net.sourceforge.jtds.jdbc.Driver) and the JDBC URL (jdbc:jtds:sqlserver://<hostname>:1433/<database>) and the connection is now working fine.
Hope this helps other people...
Thanks to those of you who offered suggestions and things to check...much appreciated.
Robyn

SQL Server Installation failing saying 'Could not write values to registry key \SOFTWARE. Verify you have sufficient access or contact support personnel'

Hi,
I am trying to install SQL server 2012/SQL Server 2014 and I constantly keep getting this error and the Management Tools fails to install.
'Could not write values to registry key \SOFTWARE. Verify you have sufficient access or contact support personnel'
Tried installing even SQL Server 2008 and still get the same error.
Below is the log i get from C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140705_151943\sql_ssms_Cpu64_1.log
MSI (s) (FC:D8) [15:22:55:746]: Executing op: RegAddValue(Name=SQLPath,Value=C:\Program Files (x86)\Microsoft SQL Server\110\Tools,)
MSI (s) (FC:D8) [15:22:55:746]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE,,BinaryType=0,,)
MSI (s) (FC:D8) [15:22:55:746]: Executing op: RegAddValue(,,)
MSI (s) (FC:D8) [15:22:55:746]: Note: 1: 1406 2: 3: SOFTWARE 4: 5
MSI (s) (FC:D8) [15:22:59:434]: Product: SQL Server 2012 Management Studio -- Error 1406. Could not write value to key \SOFTWARE. System error . Verify that you have sufficient access to that key, or contact your support personnel.
Error 1406. Could not write value to key \SOFTWARE. System error . Verify that you have sufficient access to that key, or contact your support personnel.
MSI (s) (FC:D8) [15:23:03:435]: User policy value 'DisableRollback' is 0
MSI (s) (FC:D8) [15:23:03:435]: Machine policy value 'DisableRollback' is 0
Action ended 15:23:03: InstallFinalize. Return value 3.
Just not able to figure out what the problem is, can someone help?
Thanks

Hi,
Thanks for providing log
Following is in the log.
01) 2014-07-09 11:08:53 Slp: Could not write value to key \SOFTWARE. Verify that you have sufficient access to that key, or contact your support personnel.
(01) 2014-07-09 11:08:58 Slp: Watson bucket for generic failure has been created
(01) 2014-07-09 11:08:58 Slp: Error: Action "Install_sql_ssms_Cpu64_Action" failed during execution.
(01) 2014-07-09 11:08:58 Slp: Completed Action: Install_sql_ssms_Cpu64_Action, returned False
(01) 2014-07-09 11:08:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-09 11:08:59 Slp: Running Action: Install_sql_tools_Cpu64_Action
(01) 2014-07-09 11:08:59 Slp: Sco: File 'D:\Softwares\SQL2012\DeveloperEdition\x64\setup\x64\sql_tools.msi' does not exist
(01) 2014-07-09 11:07:00 Slp: Sco: File 'D:\Softwares\SQL2012\DeveloperEdition\x64\setup\x64\sql_ssms.msi' does not exist
(01) 2014-07-09 11:07:00 Slp: Checkpoint: PREINSTALL_SQL_SSMS_CPU64_ACTION
(01) 2014-07-09 11:07:00 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
(01) 2014-07-09 11:07:00 Slp: Sco: Attempting to open SC Manager
(01) 2014-07-09 11:07:00 Slp: Sco: Attempting to open service handle for service msiserver
(01) 2014-07-09 11:07:00 Slp: Invoking QueryServiceStatus Win32 API
(01) 2014-07-09 11:07:00 Slp: Sco: Attempting to close service handle for service msiserver
(01) 2014-07-09 11:07:00 Slp: Sco: Attempting to close SC Manager
(01) 2014-07-09 11:07:00 Slp: Target package: "D:\Softwares\SQL2012\DeveloperEdition\x64\setup\sql_ssms.msi"
(01) 2014-07-09 11:07:57 Slp: MSI Error: 1406 Could not write value to key \SOFTWARE. Verify that you have sufficient access to that key, or contact your support personnel.
(01) 2014-07-09 11:08:38 Slp: InstallPackage: MsiInstallProduct returned the result code 1603.
(01) 2014-07-09 11:08:38 Slp: Using MSI error code to detect the retry option: 1406
(01) 2014-07-09 11:08:38 Slp: No retry-able MSI return code detected.
(01) 2014-07-09 11:08:38 Slp: Watson Bucket 2
Original Parameter Values
From above it seems client tools component is missing from Installation or may be problem with Windows installer but I guess this is not issue with windows installer . Can you re download SQL Server package and run again.
Edit: For further analysis can you also post log from below location on skydrive
C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140709_104804\sql_ssms_Cpu64_1.log
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Weblogic 9.2 server not starting up : Could not create the Java virtual mac

Hi
I have created Weblogic domain.
Now I am trying to bring my server up by using the startWeblogic.cmd present in domain\bin.
I get the following error -
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode)
Unrecognized option: -
Could not create the Java virtual machine.
The output when i run the start script is as follows -
JAVA Memory arguments: -Xms1024m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=256m -XX:MaxPermSize=256m
WLS Start Mode=Development
CLASSPATH=S:local;;D:\bea\patch_weblogic923\profiles\default\sys_manifest_classpath\weblogic_patch.jar;P:\JDK150~1\lib\tools.jar;D:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;D:\bea\WEBLOG~1\server\lib\weblogic.jar;D:\bea\WEBLOG~1\server\lib\webservices.jar;;D:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient51.jar;D:\bea\WEBLOG~1\server\lib\xqrl.jar;;Q:\VODAFO~1\lib\WSDLProxy.jar;
PATH=D:\bea\patch_weblogic923\profiles\default\native;D:\bea\WEBLOG~1\server\native\win\32;D:\bea\WEBLOG~1\server\bin;P:\JDK150~1\jre\bin;P:\JDK150~1\bin;D:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Intel\DMIX;C:\Program Files\TortoiseSVN\bin;D:\ProgramFiles\Rational\common;C:\Program Files\CVSNT\;D:\bea\WEBLOG~1\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
Starting WLS with line:
P:\JDK150~1\bin\java -client -Xms1024m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=256m -XX:MaxPermSize=256m -Xverify:none -da -Dplatform.home=D:\bea\WEBLOG~1 -Dwls.home=D:\bea\WEBLOG~1\server -Dwli.home=D:\bea\WEBLOG~1\integration -Dweblogic.management.discover=true -Dweblogic.http.descriptor.merge=true -Dejbruntime.database=pointbase44 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\bea\patch_weblogic923\profiles\default\sysext_manifest_classpath -Djava.protocol.handler.pkgs=com.vodafone.vgsg.wsdlproxy -Dcom.vodafone.vgsg.wsdlproxy.protocol=http -Dcom.vodafone.vgsg.wsdlproxy.host=localhost -Dcom.vodafone.vgsg.wsdlproxy.port=7001 -Dweblogic.Name=portalServer -Djava.security.policy=D:\bea\WEBLOG~1\server\lib\weblogic.policy - weblogic.Server
I checked all configurations. All seem fine but I am surely missing something.
I recreated the domain thinking I messed up something but that did not help.
I tried using jrockit instead of sun jdk. It still could not create JVM.
I really appreciate any help!
Regards,
Smita

Extra dash in the java start line ( before the weblogic.Server ):
-Dweblogic.Name=portalServer -Djava.security.policy=D:\bea\WEBLOG~1\server\lib\weblogic.policy - weblogic.Server
might be why you get the message:
Unrecognized option: -
I can get the same error with this example:
/bin> java -
Unrecognized option: -
Could not create the Java virtual machine.

Windows explorer does not start and could not open control panel.

HP Touchsmart 610-1280
When trying to open window explorer, it says window explorer is stopped working and trying to restart. But it does not open. Cannot go to control panel.

Hello GLPP:
Can you srst up the computer in safe mode. Turn off computer and turn it back on press F-8 and hold as the computer starts up. Ounce in safe mode open up recovery manger select microsoft recovery and do a back restore recovery choose a date as close as you can before this problem occurred and do the recovery. This will fix your issue.

File System error while restoring a backup from analysis server to another

Hi
I have restored an analysis database backup to from server 1 (sql server 2008) to server 2(sql 2008) and its working fine
and now am trying to restore another database from analysis server server 3 (sql 2005) to server 2 (sql 2008 )but its giving error that
File System error occured while opening the file G:\ProgramFiles\MSAS10.MSSQLSERVER\OLAP\Backup\Workordermodule.0.db\WomDW1.7.00 ..etc

Hi Maverick,
According to your description, you are experiencing the error when restoring the SSAS 2005 database on SSAS 2008 server, right?
In your scenario, how do you backup your SSAS 2005 database? Please ensure that you backup and restore steps are correct. Here is a blog which describe how to migrate a cube in SQL Server Analysis Services 2005 to SQL Server Analysis Services 2008 step by
step, please refer to the link below.
http://blogs.technet.com/b/mdegre/archive/2010/03/31/migrating-a-cube-in-sql-server-analysis-services-2005-to-sql-server-analysis-services-2008.aspx
Besides, you can import SQL 2005 AS database in SQL 2008 BIDS Project. Then fix AMO warnings and deploy that database on SQL 2008 Server.
http://technet.microsoft.com/en-in/library/ms365361(v=sql.100).aspx
Regards,
Charlie Liao
TechNet Community Support

Help for OSX Server 3.2.2 could not open after upgarded Mac OSX Yosemite!

Dear All,
Please for solving my osx server 3.2.2 could not open and show failure after upgarded Mac OSX Yosemite.

Version 3.2.2 does not work with Yosemite you'll need to upgrade to version 4.0 to get Server functionality.
Cheers HD

Could not open error log file ''. Operating system error = 5(failed to retrieve text for this error. Reason: 15105).

Hello
When I try to start the SQl server service i get the following error:
Event id 17058
Could not open error log file ''. Operating system error = 5(failed to retrieve text for this error. Reason: 15105).
As a test I have made sure the errorlog file ,and the entire drive it is, has everyone full control permissions, but to no avail. Does anyone have any ideas to resolve this issue?
Thank you

Hi,
Try running:
SELECT SERVERPROPERTY('ErrorLogFileName')
Then verify that the account being used to run the SQL Server service account has access to the path output above. If possible, you could try logging onto the server with the same account used to run SQL Server then navigate to the errorlog folder.
Thanks,
Andrew Bainbridge
SQL Server DBA
Please click "Propose As Answer" if a post solves your problem, or "Vote As Helpful" if a post has been useful to you

SQL Server Configuration Manager snap in not getting created by Microsoft Manager Console

I just installed SQL Server 2008 Express with Advanced Services. I want to enable FILESTREAM so I can install the AdventureWorks sample database. The instructions at this page: http://msdn.microsoft.com/en-us/library/cc645923.aspx say:
On the Start menu, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Configuration Manager.
When I open SQL Server Configuration Manager I get an error message: "MMC could not create the snap in, the snap in might not have been installed correctly. Name: SQL Server Configuration Manager." Then it gives me a CLSID.
On this page: http://msdn.microsoft.com/en-us/library/ms174212.aspx it says: "Microsoft Management Console (mmc.exe) uses the SQLServerManager10.msc file in the Windows System32 folder to open SQL Server Configuration Manager."
I looked in the System32 folder and, sure enough, the file SQLServerManager10.msc is in there. It's XML inside the file.
Please help. I really need to get this SQL Server Configuration Manager working so I can enable FILESTREAM data and install the database. I appreciate any help you can give.
--goldenthroat

I'd try this first;
Go to the Run from the Start menu and type mmc and press enter to open an empty console. Under the File menu select "Add/Remove Snap-in". Click "Add" under Console Root and select the "Microsoft SQL Enterprise Manager" snap-in. Close windows until you are back to the mmc, and you can rename the "console1.msc" to default name which is "SQL Server Enterprise Manager.MSC" and save it under C:\Program Files\Microsoft SQL Server\80\Tools\Binn (Default location of SQL Server 2000) - Obviously you want your 2008 installation folder and unfortunately I don't have it so I couldn't point you to it... http://weblogs.sqlteam.com/

Windows could not start the FLEXnet Licensing Service service on Local Computer Error 1068: The dependency service or group failed to start.

Today I installed Adobe Director 11.5. I received a couple of errors in the FLEXnet Licensing Service. It looks It could not start. I tried to download the Licence fix what I found on Google but that doesn't work, so I checked the 'Service' at service (windows).
It's status is empty. When I double click on the FLEXnet Licensing Service, clicked on start at the opened window and an error is coming:
Windows could not start the FLEXnet Licensing Service service on Local Computer
Error 1068: The dependency service or group failed to start.
I don't understand what it says with this message, only that it is impossible to start. However, that is not what I am trying of course, I want to start the FLEXnet Licensing Service, service.
Re-installing of the software, doesn't make any change. How can I start it so Director is also working?

Hi Don1233,
Please consider seek help at the software vendor side.
For the services didn't start, follow the suggestions posted by Elton in the thread below:
https://social.technet.microsoft.com/Forums/en-US/e35da253-f0df-41d1-8df2-b73fa54742a0/windows-could-not-start-the-flexnet-licensing-service-service-on-local-computer-error-1068-the?forum=w7itproinstall
Best regards
Michael Shao
TechNet Community Support

IPhoto9: "library could not be opened because the file system of the library's volume is unsupported."

Can please anyone help me with this issue.
After upgrading from iPhoto8 to iPhoto9 my library won't open anymore. I have stored all my pictures on a NAS (Buffalo Link Station Duo). It all worked fine but since upgrading to iPhoto9 I do have the following problem:
When opening iPhoto I receive a message that the library needs to be updated. I assume that iPhoto should just do this sort of automatically in order to upgrade to iPhoto9.However, next message I receive then is
"The library could not be opened because the file system of the library's volume is unsupported."
Apple support so far does not seem to be able to solve my issue. Anyone else having had the same issue and having a solution to this?
Thanks a lot for your help.

There is no solution.
IPhoto needs to have the Library sitting on disk formatted Mac OS Extended (Journaled). Users with the Library sitting on disks otherwise formatted regularly report issues including, but not limited to, importing, saving edits and sharing the photos.While you have been lucky to date, many folks with a library on a NAS found that it worked for a while and then the problems started.
Workaround: Put the Library on a Disk Image formatted Mac OS Extended (Journaled) and store that on the NAS. But the real solution is to use a properly formatted disk for the Library.
Regards
TD

The specified domain either does not exist or could not be contacted when logging in through RDP. Server 2012/SBS 2007

I have a server 2012 machine running RDP and a PDC running SBS 2007. Every once a while all my users get an error saying "The specified domain either does not exist or could not be contacted". After waiting ~5-10 minutes the issue resolves itself.
I believe it has something to do with the syncing between the two but am not 100% sure. Anyone know a fix or what I should look at?
Jerry T

Hi Jerry,
Thank you for posting in Windows Server Forum.
After referring to your error, it seems to have DNS issue in your case which can’t locate the DC. Please check the setting related to DNS issue as following. (Below quoted from
this thread)
If this is the case, I would recommend proceeding like that:
1. Make sure that each DC has only one IP address in use and ONLY one NIC card enabled (Other NICs should be disabled)
2. Make sure that public DNS servers are configured as DNS forwarders and not in IP settings of DCs
3. Choose a healthy DC / DNS server and make each DC point to it as primary DNS server
4. Make each DC / DNS server point to its private IP address as secondary DNS server
5. Make sure that needed ports for AD replication are opened: http://technet.microsoft.com/en-us/library/bb727063.aspx
6. Check your DNS zones and remove manually all obsolete / unused DNS records for DCs
Once done, run ipconfig /registerdns and restart netlogon on each DC you have.
On the client computer, run ipconfig /flushdns and check again.
Hope it helps!
Thanks.
Dharmesh Solanki

Apachectl start: httpd could not be started

Hi everyone
Can any helpme with this error when a try to start the apache server on Sun Solaris?
apachectl start: httpd could not be started
I could start the apache server in W2K perfect, and use iSQL*Plus very well, but when a try to do the same in solaris, i've this problem.
Thanks!
Ariel

Hi everyone
I'mself respond to my question.
I try to start the Apache server in a x-terminal and its all ok.
The problem was I try first in a simple terminal.
Good bye
Ariel

SQL Server not Starting Up - Could not open error log file system error = 5(Access is denied.)

Similar Messages

Maybe you are looking for