Fail to ping to Solaris 10 system.

I install Solaris 10 but sometime I could not ping to system but sometime it is ok to ping. Is there any problem with network configuration in Solaris 10 or it is a network environment because I rent my server in the share rack (Data Center) and I dont know other factor that make my server fail to ping for sometime ?
Thanks

1) How's the uptime on the box?
2) is 'svcs -xv' clean?
3) Perhaps smokeping might be able to help you: http://oss.oetiker.ch/smokeping/

Similar Messages

OK to use fdisk/100% "SOLARIS System" partition for RAID6 Virtual Drive?

Solaris newb, here - I am configuring an x4270 with 16 135 GB drives. Basic approach is
D0, D1: RAID 1 (Boot volume, Solaris, Oracle Software)
D2-D13: RAID 6 (Oracle dB files)
D14, D15: global spares
After configuring the RAID's w/WebBIOS Utility, I am now trying to format/partition the RAID 6 Virtual Drive, which shows up as 1.327 TB 'Optimal' in the MegaRAID Storage Manager. After hunting around the ether for advice on how to do this, I came across http://docs.oracle.com/cd/E23824_01/html/821-1459/disksxadd-50.html#disksxadd-54639
"Creating a Solaris fdisk Partition That Spans the Entire Drive"
which is painfully simple: after 'format', just do an 'fdisk' and accept the default 100% "SOLARIS System" partition. After doing this, partition>print and prtvtoc show this:
partition> print
Current partition table (original):
Total disk cylinders available: 59125 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 0 0 (0/0/0) 0
1 unassigned wm 0 0 (0/0/0) 0
2 backup wu 0 - 59124 1.33TB (59125/0/0) 2849529375
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 - 0 23.53MB (1/0/0) 48195
9 unassigned wm 0 0 (0/0/0) 0
# prtvtoc /dev/dsk/c0t1d0s2
* /dev/dsk/c0t1d0s2 partition map
* Dimensions:
* 512 bytes/sector
* 189 sectors/track
* 255 tracks/cylinder
* 48195 sectors/cylinder
* 59127 cylinders
* 59125 accessible cylinders
* Flags:
* 1: unmountable
* 10: read-only
* Unallocated space:
* First Sector Last
* Sector Count Sector
* 48195 2849481180 2849529374
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
2 5 01 0 2849529375 2849529374
8 1 01 0 48195 48194
My question: is there anything inherently wrong with this default partitioning? Database is for OLTP & fairly small (<200 GB), with about 140 GB being LOB images.
Thanks,
Barry

First off, RAID-5 or RAID-6 is fine for database performance unless you have some REALLY strict and REALLY astronomical performance requirements. Requirements that someone with lots of money is willing to pay to meet.
You're running a single small x86 box with only onboard storage.
So no, you're not operating in that type of environment.
Here's what I'd do, based upon a whole lot of experience with Solaris 10 and not so much with Solaris 11, and also assuming this box is going to be around for a good long time as an Oracle DB server:
1. Don't use SVM for your boot drives. Use the onboard RAID controller to make TWO 2-disk RAID-1 mirrors. Use these for TWO ZFS root pools. Why two? Because if you use live upgrade to patch the OS, you want to create a new boot environment in a separate ZFS pool. If you use live upgrade to create new boot environments in the same ZFS pool, you wind up with a ZFS clone/snapshot hell. If you use two separate root pools, each new boot environment is a pool-to-pool actual copy that gets patched, so there are no ZFS snapshot/clone dependencies between the boot environments. Those snapshot/clone dependencies can cause a lot of problems with full disk drives if you wind up with a string of boot environments, and at best they can be a complete pain in the buttocks to clean up - assuming live upgrade doesn't mess up the clones/snapshots so badly you CAN'T clean them up (yeah, it has been known to do just that...). You do your first install with a ZFS rpool, then create rpool2 on the other mirror. Each time you do an lucreate to create a new boot environment from the current boot environment, create the new boot environment in the rpool that ISN'T the one the current boot environment is located in. That makes for ZERO ZFS dependencies between boot environments (at least in Solaris 10. Although with separate rpools, I don't see how that could change....), and there's no software written that can screw up a dependency that doesn't exist.
2. Create a third RAID-1 mirror either with the onboard RAID controller or ZFS, Use those two drives for home directories. You do NOT want home directories located on an rpool within a live upgrade boot environment. If you put home directories inside a live upgrade boot environment, 1) that can be a LOT of data that gets copied, 2) if you have to revert back to an old boot environment because the latest OS patches broke something, you'll also revert every user's home directory back.
3. That leaves you 10 drives for a RAID-6 array for DB data. 8 data and two parity. Perfect. I'd use the onboard RAID controller if it supports RAID-6, otherwise I'd use ZFS and not bother with SVM.
This also assumes you'd be pretty prompt in replacing any failed disks as there are no global spares. If there would be significant time before you'd even know you had a failed disk (days or weeks), let alone getting them replaced, I'd rethink that. In that case, if there were space I'd probably put home directories in the 10-disk RAID-6 drive, using ZFS to limit how big that ZFS file system could get. Then use the two drives freed up for spares.
But if you're prompt in recognizing failed drives and getting them replaced, you probably don't need to do that. Although you might want to just for peace of mind if you do have the space in the RAID-6 pool.
And yes, using four total disks for two OS root ZFS pools seems like overkill. But you'll be happy when four years from now you've had no problems doing OS upgrades when necessary, with minimal downtime needed for patching, and with the ability to revert to a previous OS patch level with a simple "luactivate BENAME; init 6" command.
If you have two or more of these machines set up like that in a cluster with Oracle data on shared storage you could then do OS patching and upgrades with zero database downtime. Use lucreate to make new boot envs on each cluster member, update each new boot env, then do rolling "luactivate BENAME; init 6" reboots on each server, moving on to the next server after the previous one is back and fully operational after its reboot to a new boot environment.

Root password fails on auth to Solaris Management Console Server

I've setup Solaris 10 x86 on a VA linux 1220 server, all is good so far except when I try to create additional users. I am logged in as root, and the root password logs in to the CDE, but fails on authentication to Solaris Management Console Server when I try to use any of the management apps like computers and networks or Users. So I'm stalled at the point where I should be configuring the system. I have been very careful about typing in the password exactly as I use it in the login screen, but it never works in the System Management tools for This Computer. The password I'm using is 26 characters long, is it too long? Or is there a step I'm missing?
Thanks,
Brian

One of my famous guesses, but unless you changed the default password algorithm the maximum length of your password is 8 characters, when logging in on the console or desktop, anything typed after those eight characters will be ignored (unless this behaviour changed very recently).
Its possibly that SMC, and its server component WBEM does not ignore the extra characters, which could cause this behavior.
What happens if you try and login to SMC with the root user and only the first eight characters of your password?
Btw, if this was the problem i think there is a way to change the default crypto algorithm to something that supports more characters.
.7/M.

Fail to ping standby . error = 3113 in trace files (oracle 9i)

Hi there. One of my standby databases is not working properly, I mean is not synchronized with primary. Both database are 9i Release 2 running on Compaq Tru64 servers
I look for the primary trace files and I found this trace file:
$ vi umercado_arc1_141731.trc
"umercado_arc1_141731.trc" 28 lines, 1164 characters
/oracle/app/oracle/admin/umercado/bdump/umercado_arc1_141731.trc
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
ORACLE_HOME = /oracle/app/oracle/product/9.2.0
System name: OSF1
Node name: utora01.emsut.com.sv
Release: V5.1
Version: 2650
Machine: alpha
Instance name: umercado
Redo thread mounted by this instance: 1
Oracle process number: 13
Unix process pid: 141731, image: [email protected] (ARC1)
*** SESSION ID:(10.1) 2008-09-02 16:03:38.240
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
*** 2008-09-03 11:22:29.405
RFS network connection lost at host 'umercado3'
Fail to ping standby 'umercado3', error = 3113
Error 3113 when pinging standby umercado3.
*** 2008-09-03 11:22:29.411
kcrrfail: dest:3 err:3113 force:0
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
The error I want to highlight is "FAIL TO PING STANDBY UMERCADO3, ERROR 3113"
I did this testings on the primary server:
- Unix ping to standby node , ok
- tnsping to standby database (tnsping umercado3), ok
Therefore I do not find the reason for this error. By this time I have defeered the transfer from the primary to standby.
Any advice is welcome.
Thanks!

Suggestion: would attempt to make a sqlplus connection from the primary to the standby using the tns entry that you have configured for the log_archive_dest parameter. you need to connect to the standby as sys.
What happened:
I did a sqlplus connection ON THE PRIMARY DATABASE using the tns entry that is exactly the same used in log_archive_dest_2 parameter. Here is it:
SQL> conn sys/*********@UMERCADO3 as sysdba
Connected.
Therefore I do not think it is a problem in the standby password file.
Any suggestions?

Failed to ping JCo destination 'WD_RSDAS_RFC_METADATA_DEST'.

Hello SDNers,
I have Netweaver ABAP trial SPS12 and Netweaver Java Trial SPS14 installed in my laptop. I have also configured SLD and successfully run transaction RZ70. I'm stucked at configuring JCo.
From Web Dynpro Content Administrator, when I ping, it gives me:
Failed to ping JCo destination 'WD_RSDAS_RFC_METADATA_DEST'.
From Web Dynpro Content Administrator, when I test, it gives me:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=hapizorr GROUP=NETWEAVER R3NAME=NSP MSSERV=sapmsNSP PCS=1 ERROR Group NETWEAVER not found TIME Thu Oct 16 23:59:36 2008 RELEASE 700 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 4299 DETAIL LgIGroupX COUNTER 1
I have created group NETWEAVER via transaction SMLG at the backend system. I have entered sapmsNSP 3600/tcp in the service file. I have also successfully pinged to the hostname. I have also successfully telnetted to hostname 3600.
What's wrong with my config? Help, pls!
Rgds,
Hapizorr Rozi Alias

Hi,
Just to test, try to connect using SPACE LOGON GROUP
Another tip, verify the property rdisp/autoabaptime on profile of your ABAP Installation.
Try to change it from 0 to 300.
Best regards

Installation of iCS 2.x on a Solaris system in which X or Open Windows software in not installed

When I try to run the install wizard for iPlanet Calendar Server 2.x on a
Solaris system that does not have X-Windows or Open Windows graphical user
interface, I get the following error:<BR>
<P>
Starting install wizard in graphical mode
ld.so.1: instsupp/bin/java: fatal: libX11.so.4: open failed: No such file or
directory
Killed
setup: The installation failed with errors.
<P>
To work around this problem, place a copy of libX11.so.4
into the /usr/lib
directory. This will allow
you to run the Calendar Server 2.x installer in the -nodisplay
mode. You can find the
libjava.so in the
instsupp/lib/sparc/native_threads
directory under the installation
program tree.

I thought that might be the case, so I preemptively expanded the mac partition to fill the entire disk, and retried -- it did not work. I think, at this point, my best bet might be to reinstall OSX from scratch, enable file-vault, and then repartition and install the other OS's.

Report to show all failed login attempts in B1 system

Hi,
Please advise is there anyway to view all failed login attempts in B1 system.
Regards,
Priscilla

Hi Priscilla,
Unfortunately, all failed login attempts are stored on each clients' local drive. There is no table to hold them.
Thanks,
Gordon

Sql Server 2012 Login Failed for user "NT Authority\System"

I have installed SQL Server on a new server. I have been getting the following error on each of the database in it.
Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ABC'. [CLIENT: xxx.xxx.xxx.xxx]
Here is some information on the instance:
1) Default instance
2) SQL Server, Sql Server Agent, Sql Server Reporting services are running / log on using a domain service account.
3) Sql Server Browser is disabled.
4) SQL Server VSS Writer is running / log on as Local Service.
5) NT AUTHORITY\SYSTEM does exists in Login with just public server roles.
I ran a trace on login failed and I get:
ApplicationName: Microsoft Windows Script Host
and it runs every 15 minutes.
Help please?

Hi,
The error was thrown when the SCOM components connected to the backend SCOM databases.
You can specify a domain account, grant it the sysadmin role and the error should be gone.
Also, see the replies in your previous thread:
http://social.technet.microsoft.com/Forums/en-US/23f6b6cb-ec41-4117-8613-26d24c948827/login-failed-for-user-username-reason-failed-to-open-the-explicitly-specified-database
Thanks.
Tracy Cai
TechNet Community Support

System call failed. Error 2 (The system cannot find the file specified. ) in execution of system call 'CreateProcessAsUser' with parameter ( , NULL, Program Files/sapinst_instdir/BS2011/ERP606/AS-ABAP/SYB/HA/DB, &StartupInfo, &ProcessInfo),

Dear All,
I am getting a below error while doing ehp6 installation on sybase (high availbility )
can any one help me on this..?
An error occurred while processing option SAP Business Suite 7i 2011 > Enhancement Package 6 for SAP ERP 6.0 > SAP Application Server ABAP > SAP ASE > High-Availability System > Database Instance( Last error reported by the step: System call failed. Error 2 (The system cannot find the file specified. ) in execution of system call 'CreateProcessAsUser' with parameter ( , NULL, Program Files/sapinst_instdir/BS2011/ERP606/AS-ABAP/SYB/HA/DB, &StartupInfo, &ProcessInfo), line (646) in file (d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxcchapp.cpp), stack trace: d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\ejs\ejscontroller.cpp: 181: EJSControllerImpl::executeScript() d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\ejs\jsextension.hpp: 1059: CallFunctionBase::call() d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\osmod\iaxxbprocess.cpp: 423: CIaOsProcess::start_impl() d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxcchapp.cpp: 238: CSyChildApplicationImpl::start(false) d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxcchapp.cpp: 262: CSyChildApplicationImpl::doStart() .). You can no
Regards,
Letz..

Hello Mauricio.
Thanks
Two Thinks:
1.- This error appears precisely in the process of creating SAP users including you mention sidadm:
      A.- Execute sapinst
      B.- Installation option is chosen
            SAP NetWeaver CE Production Edition
                    Installation Options
                        High-Availability System
                              Central Service Instance (SCS)
       c.- System ID, Next and appear message error
2.- However, the user manually create sidadm, I gave the permissions you indicate, and the error message is the same
Thanks

Ping all the servers into SP farm using powershell script and send email only if any of them failed to ping.

Hi,
i am trying to have such kind of functionality, so that if any servers in sharepoint farm failed then it will send notification email to specific user that server is not able to ping or failed. Right now following script is working but it sending mail either
servers are all running or dead. But i would like to send email only if any of the server failed to ping. what i need to modify following code to work.
Thanks in advanced
#### Provide the computer name in $computername variable
$ServerName = "localhost","Dc-XX"
$smtp = "ExchChange"
$to = "[email protected]"
$from = "[email protected]"
$sub = " Server Status"
$body = @"
##### Script Starts Here ######
foreach ($Server in $ServerName) {
                    if (test-Connection -ComputerName $Server -Count 2 -Quiet ) {
                        $body += write-output "$Server is alive and Pinging `n"
                            } else { $body += Write-output "$Server seems dead not pinging `n"
$body
send-MailMessage -SmtpServer $smtp -To $to -Subject $sub -Body $body  -From $from

you need to put a check on the send-mailmessage if no ping fails then exit else send the email with message.
also try this script, performing the the same thing but more granular way
http://gallery.technet.microsoft.com/scriptcenter/d0670079-6158-4dc5-a9da-b261c70e4b7d#content
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Anyone know when the 'Patch' or 'service pack' will be released for UDS 5? It doesn't work correctly on Solaris systems.

When trying to export code from older versions of forte and import the code into UDS 5, the imports don't work correctly on Sun server, Solaris system. Errors in the Windows. Seems to be a common problem, but haven't heard of any patch yet.

The SP1 for UDS 5 or 5.0.3 will be out in 2-3 weeks. I already have a beta copy of SP1 so I am sure you can request this if you open a case on your problem. I have never ran into the problem you are describing.
ka

Wireless Client PING-Based monitor system question

Hi:
I joined this forums because i need to recopilate info about a monitor system.
So, i have a relative big wireless network and due to legal instances I MUST use a ping-based monitor system to see the status of my network devices and the final clients on wireless station.
We developed a php linux-based system to make pings every 5 minutes to see if there is a host UP or DOWN. Everything works fine, the server is making the pings to the clients and MRTG generates graphic statistics.
Reference image -> http://img103.imageshack.us/img103/9125/pingred0xq.jpg
The problem is now I have received a notification to make a change on this system to send the pings FROM the clients TO the server and generate statistics.
Is there any difference between making pings from the Client side to the server and viceversa? Does round-trip time is different maybe?
What are the technicals issues on this system?
I accept every critic, advice, suggestion, information, etc.
PS: Sorry my poor english

That's interesting. It sounds as if you may have a good reason for implementing this, but it would also seem to be an inefficient monitoring scheme. A polling interval of 5 minutes does not give that much granularity for statistics even if you are able to make it work from the client side. Also, you would need to centrally collect the statistics in some way. If it were me I would stick to a centrally based monitoring system. I make heavy use of the syslog capabiliy on Cisco access points since they log just about everything. You can even have a syslog monitoring system page you for something as small as dropped wireless connection if you want to go that far.
Sorry if that's not much help, but I would definately have some people look at the big picture before implementing the proposed solution.
Good luck with it.
R Duke

11 -- 11,1 Upgrade: pkg://solaris/system/library signature problems?

Hi all,
I have a vanilla 11 11/11 lab system (x64, in VirtualBox) that I've tried to upgrade to 11.1:
# uname -a
SunOS alpha 5.11 11.0 i86pc i386 i86pc
# pkg list entire
NAME (PUBLISHER) VERSION IFO
entire 0.5.11-0.175.0.0.0.2.0 i--
# pkg publisher
PUBLISHER TYPE STATUS URI
solaris origin online http://pkg.oracle.com/solaris/release/
It has full connectivity to the Internet, and I've tried pointing it to the public release repo, a local 11.1 repo that has had the update ISO injected into it, and with a single loopback repo pointing to only the upgrade ISO (sol-11_1-upgrade-repo.iso, md5 verified). In all 3 cases I get this at the first stage of the upgrade:
# pkg update
Creating Plan |
pkg update: A signature in pkg://solaris/system/[email protected],5.11-0.175.0.10.1.0.0:20120918T164707Z could not be verified for this reason:
The signature value did not match the expected value. Res: 0
The signature's hash is 235c7674d821032ae3eeda280c7837d1f1f4fdb5
I must be missing something simple, because I can't imagine a bad signature in the public or upgrade-ISO repos. Any ideas?
Thanks!

If possible, please file a support request for this issue through the My Oracle Support portal so that the details of the issue can be captured.
With that said, executing the following commands may provide a viable workaround:
pkg set-property signature-policy=ignore
pkg set-publisher --set-property signature-policy=ignore solaris
Once the above commands have been executed, attempt the pkg update again. If successful, then after rebooting to the new boot environment, reset the properties as follows:
pkg unset-property signature-policy
pkg set-publisher --unset-property signature-policy

Ping in solaris 10

Hi , i am havign a problem with ping in solaris 10 . i need the ping to return the actual canonical name not the alias . ( like in solaris 8 )
but in solaris 10 wheni use ping it just returns the alias
e.g. in sol 10 ..
ping active-1
active-1 is alive
but it solaris 8 it used to return the actual hostname
is there anyway around this ? because i have many scripts that rely on the return to be the actual hostname before it kicks off a program or makes a connection . I really dont want to be going through hundreds of scripts amending that
thanks

are you familiar with ipf? it comes with solaris. check man ipf for some starter background if you are unfamiliar with it.

Critical SMS_Executive SQL Login failed for user 'NT AUTHORITY\SYSTEM'.

I am getting sql login errors on my sms executive log that i believe is stopping me from pxe booting. I have tried finding where to enter the credentials but i cannot find it.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
Starting SMS_EXECUTIVE... SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Microsoft System Center 2012 Configuration Manager v5.00 (Build 7958)
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
Copyright (C) 2011 Microsoft Corp. SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Running as a Win32 service. SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Process ID: 2368 SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Worker thread ID: 2412 SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Certificate (0x610450) is Exportable SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Initialize COM Security. SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
InitializeCOMSecurity: RegOpenKeyEx for appid key Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: RegQueryInfoKey for appid key Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: RegQueryValueEx for AccessPermission Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: IsValidSecurityDescriptor() Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: MakeAbsoluteSD() Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: CoInitializeEx() Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity() Succeeded. SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Installation directory: E:\Program Files\Microsoft Configuration Manager
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
This server: E076SCCM SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Site server: sccmserver.org SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Site code: 076 SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Site type: 1 SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
CSMSExecService::RegisterDBConnection: Register a DB connection...
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
Initializing the status message reporting system...
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
The path to the "Status Manager" inbox is "E:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs".
SMS_EXECUTIVE 4/10/2014 3:13:13 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Registered this process as a source of "SMS Server" events.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Registered this process as a source of "SMS Client" events.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Registered this process as a source of "SMS Provider" events.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Status message reporting system initialized successfully.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
STATMSG: ID=500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_EXECUTIVE" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:47.950 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Certificate maintenance interval is every 1800 seconds
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AD_FOREST_DISCOVERY_MANAGER initialized, DLL = "\bin\x64\ADForestDisc.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Sun Apr 13 00:00:00 2014 Eastern
Daylight Time". SMS_EXECUTIVE
4/10/2014 3:13:48 PM 2412 (0x096C)
STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_FOREST_DISCOVERY_MANAGER" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.119 2014 ISTR0="2014 04 0 13 04 00 00 000" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT initialized, DLL = "\bin\x64\adsgdis.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Thu Apr 10 15:15:00 2014 Eastern
Daylight Time". SMS_EXECUTIVE
4/10/2014 3:13:48 PM 2412 (0x096C)
STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.120 2014 ISTR0="2014 04 4 10 19 15 00 000" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AD_SYSTEM_DISCOVERY_AGENT initialized, DLL = "\bin\x64\adsysdis.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Thu Apr 10 15:15:00 2014 Eastern Daylight
Time". SMS_EXECUTIVE
4/10/2014 3:13:48 PM 2412 (0x096C)
STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_SYSTEM_DISCOVERY_AGENT" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.157 2014 ISTR0="2014 04 4 10 19 15 00 000" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AD_USER_DISCOVERY_AGENT initialized, DLL = "\bin\x64\adusrdis.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Thu Apr 10 15:15:00 2014 Eastern Daylight
Time". SMS_EXECUTIVE
4/10/2014 3:13:48 PM 2412 (0x096C)
STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_USER_DISCOVERY_AGENT" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.158 2014 ISTR0="2014 04 4 10 19 15 00 000" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AI_KB_MANAGER initialized, DLL = "\bin\x64\aikbmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_ALERT_NOTIFICATION initialized, DLL = "\bin\x64\NotiCtrl.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AMT_PROXY_COMPONENT initialized, DLL = "\bin\x64\amtproxymgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_CERTIFICATE_MANAGER initialized, DLL = "\bin\x64\CertMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_CLIENT_CONFIG_MANAGER initialized, DLL = "\bin\x64\ccm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_CLIENT_HEALTH initialized, DLL = "\bin\x64\chmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_CLOUD_SERVICES_MANAGER initialized, DLL = "\bin\x64\CloudMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_COLLECTION_EVALUATOR initialized, DLL = "\bin\x64\colleval.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_COMPONENT_MONITOR initialized, DLL = "\bin\x64\compmon.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_COMPONENT_STATUS_SUMMARIZER initialized, DLL = "\bin\x64\compsumm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_DATABASE_NOTIFICATION_MONITOR initialized, DLL = "\bin\x64\smsdbmon.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_DESPOOLER initialized, DLL = "\bin\x64\despool.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_DISCOVERY_DATA_MANAGER initialized, DLL = "\bin\x64\ddm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_DISTRIBUTION_MANAGER initialized, DLL = "\bin\x64\distmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_ENDPOINT_PROTECTION_CONTROL_MANAGER initialized, DLL = "\bin\x64\EPCtrlMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_ENDPOINT_PROTECTION_MANAGER initialized, DLL = "\bin\x64\EPMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_EN_ADSERVICE_MONITOR initialized, DLL = "\bin\x64\adctrl.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_FALLBACK_STATUS_POINT initialized, DLL = "\bin\x64\fspmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_HIERARCHY_MANAGER initialized, DLL = "\bin\x64\hman.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_INBOX_MANAGER initialized, DLL = "\bin\x64\inboxmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_INBOX_MONITOR initialized, DLL = "\bin\x64\inboxmon.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_INVENTORY_DATA_LOADER initialized, DLL = "\bin\x64\dataldr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_INVENTORY_PROCESSOR initialized, DLL = "\bin\x64\invproc.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_LAN_SENDER initialized, DLL = "\bin\x64\sender.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_LICENSE_MANAGER initialized, DLL = "\bin\x64\licensemgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_MIGRATION_MANAGER initialized, DLL = "\bin\x64\migmctrl.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_MP_CONTROL_MANAGER initialized, DLL = "\bin\x64\mpcontrol.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_MP_FILE_DISPATCH_MANAGER initialized, DLL = "\bin\x64\mpfdm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_NETWORK_DISCOVERY initialized, DLL = "\bin\x64\netdisc.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", not scheduled to start again.
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
STATMSG: ID=1106 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_NETWORK_DISCOVERY" SYS=sccmserver.org SITE=076 P

First, if your site server is having problems logging into the DB, which it clearly is, you've got bigger issues than just PXE.
Have you verified the permissions in your SQL Server instance for the local System account (I'm assuming at this point that it is local to the site server)?
Jason | http://blog.configmgrftw.com

Fail to ping to Solaris 10 system.

Similar Messages

Maybe you are looking for