Domain does not exist or could not be contacted...
Hello all,
Recently attempted to add another Windows 2008R2 server to our existing DSFW domain and am receiving the following error:
The specified domain either does not exist or could not be contacted
Looking at the windows debug log the following sticks out:
NetpDoDomainJoin: status: 0x54b
Everything else appears normal with the domain, authentication etc. I've run every check from Novell TID 7001884 (Verify a Domain) and all return proper information. I've done SRV record checks using the check-dns.pl "Cool Tool" it says all of the SRV records are fine.
When attempting to join the domain the /var/opt/novell/xad/log/kdc.log presents one weird result:
krb5kdc[1054](info): no valid preauth type found: Unknown code 0
That error immediately appears upon inputting credentials in the Windows server and pressing enter
If I unzip one of the previous logs where a server was joined I do not see that 'unknown code 0' error, rather I see the normal message logs.
The server is:
SLES
VERSION = 11
CO-BRANDS = SLE openSUSE
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 1
patches as of that service pack are in place, I havn't yet updated to OES11 SP2 that's on the agenda.
Any ideas, I've been beating my head against the wall most of last night / this fine weekend AM.
Thanks,
Hi amginenigma,
Please ensure the following
1. Ensure the time of the workstation is in sync with that of DSfW DC.
2. Validate the Domain services using "xadcntrl validate" command.
Hope you are trying with a valid domain administrator user.
3. Perform a kinit on DC for the same user for which the join is failing and if kinit goes fine, then perform a ldapsearch over GSSAPI (pt. "a" below) and see if the ldapsearch is failing with any GSSAPI related errors. If so, we would want to get more information for that failure (pt. "b" below).
a. Run the command
SASL_PATH=/opt/novell/xad/lib64/sasl2/ ldapsearch -Y GSSAPI -s base -b "".
During the execution capture the ndstrace.log with TIME, TAGS, MISC and NMAS set.
b. Check the output of the following command :
LDAPCONF=/etc/opt/novell/xad/openldap/ldap.conf ldapsearch -Y EXTERNAL -s base -b "cn=<DC-name>,ou=Domain controllers,<mapped-partition>" -Z serviceprincipalname
Here, <DC-name> is the domain controller's host name. And the <mapped-partition> is the partititon which is mapped while creating the domain.
This would give the list of service principal names in created for domain controller.
4. If still no luck, please reach to NTS for help.
-Kamalesh
Similar Messages
-
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 THi 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 -
"the specified domain either does not exist or could not be contacted"
Dear Experts,
I made an installation of BPC 7.0 MS SP04 in a multiserver environment. Installation process terminated correctly. My installation user is a domain user, and he's also local Administrator on my Web/Application Server.
I simply want to add a domain user to my ApShell: so I log on to ApShell with my installation user, then I click to "add a new user".
When I try to click on "Available domain [domain name]" to see domain resources, popup appears with the following message: "the specified domain either does not exists or could not be contacted".
I cannot browse in to the domain!
Additional information:
1.The domain has been added from BPC server manager ->define system user group->domain
2.The BPC server are in the same domain to which this domain user belongs .
3. I can browse the domain resources with installation user from Appl/Web server using start->control panel-> Administrative tools-> Component Services->Active directory.
4. It's possible also add another domain user on the security of any folder.
5. I restarted COM+ application "OSoftUserManage"
6. We have another multi server installation in the same domain, the installation user is the same, there is no problem about AD browsing.
Any help would be appreciated.
Regards,
Dario
Edited by: DARIO CUPPARI on Nov 3, 2009 3:23 PMI opened a case with Microsoft and this problem has been fixed!
The issue was that I had both a Preferred DNS server (my local DNS server) and an Alternate DNS server (8.8.8.8, which I added for "good measure" in my ignorance) listed on the server. Removing the Alternate DNS server fixed the problem.
(Control panel/Network and Sharing Center/Change Adapter settings
Right click on your connection, choose properties.
Click on TCP/IPv4 (unless you are using IPv6...) and choose properties
Make sure there is only a Preferred DNS server listed.)
Why redundancy is not a good idea is a mystery to me, but in this case it isn't.
Peggy Thrasher -
The 'c' XUSER key for the DBM user does not exist or could not be identified
Hello members,
I am getting this message 'The 'c' XUSER key for the DBM user does not exist or could not be identified' in SUM preparation phase while upgrading SOLMAN from 7.01 to 7.1
Does anyone has any idea on this. What steps need to be followed for this.
My DB is MaxDB.
Thanks,
SrikanthHello,
Figured out the problem. Actually SAP System was moved from actual server to Virtual machine on the server. In this process some of the DB configuration got corrupted. And this activity was done by one of our previous employee.
Since this was a standalone system, I took backup of all current configuration and uninstalled SAP and installed new Solman 7.1 SPS12. Issue is resolved now.
Best Regards,
Srikanth
Solman Upgrade from 7.01 to 7.1 stuck in Extraction-PREP_EXTRACT/BEGIN_PRE phase -
Domain either does not exist or could not be contacted
Ok where to start!
Existing 2003 domain (2x DC)
New 2012 server - i have followed https://www.youtube.com/watch?v=OG5K6B7hgRU as i hadn't done a migration to 2012
Everything was generally ok, Active Directory appeared in sync as i had the users/computers etc before seizing the roles and these where confirmed by using 'netdom query fsmo'
Now there was FRS errors in the event log;
File Replication Service is scanning the data in the system volume. Computer SERVER-AD cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
and
The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer SERVER-AD. The File Replication Service might not recover when power to the drive is interrupted and critical
updates are lost.
The 2003 SBS log was suggesting it was in a RNL_WRAP_ERROR so i looked at one of the log and said to set the value one '1' for 'Enable Journal Wrap Automatic Restore' and this is where i think it went pear shaped!!!!!!
Entry was ' Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.' --- this is still set to value '1' do i need to change
to '0'????
So running through the FRS log entries i have ' Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.'
'The File Replication Service moved the preexisting files in c:\windows\sysvol\domain to c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
The File Replication Service may delete the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time. Files can be saved from deletion by copying them out of c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying the files
into c:\windows\sysvol\domain may lead to name conflicts if the files already exist on some other replicating partner.
In some cases, the File Replication Service may copy a file from c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into c:\windows\sysvol\domain instead of replicating the file from some other replicating partner. '
'The File Replication Service successfully added this computer to the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Information related to this event is shown below:
Computer DNS name is "rookesbs.Rooke.local"
Replica set member name is "ROOKESBS"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"'
'The File Replication Service successfully added the connections shown below to the replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
"rooketerm.Rooke.local"
"SERVER-AD.Rooke.local"
"rooketerm.Rooke.local"
"SERVER-AD.Rooke.local" '
SERVER-AD is the NEW server (master) and rooketerm is another 2003 member server
'The File Replication Service is having trouble enabling replication from ROOKETERM to ROOKESBS for c:\windows\sysvol\domain using the DNS name rooketerm.Rooke.local.' --- and getting the same for SERVER-AD
Now the SYSVOL folder SHARE had gone but looking there is a backup in that folder?
NOW i have 'NtFrs_PreExisting___See_EventLog' in the 2003 SBS SYSVOL folder -- can i use this?
I DONT HAVE A BACKUP OF SYSVOL -- i can maybe able to get an old backup of Backup exec SRS but NAS has been down :(
Now naturally how things are i can't access Active Directory on any server as it says not available/found etc
IS this going to stop users logging on in the morning??
REALLY need some urgent help!I also ran a NSLOOKUP to make sure DNS was ok - as i changed the order of DNS on SERVER-AD as the 2003 SBS server was first however those appear to be in sync anyhow - results of the lookup
> _ldap._tcp.dc._msdcs.rooke.local
Server: UnKnown
Address: ::1
_ldap._tcp.dc._msdcs.rooke.local SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = server-ad.rooke.local
_ldap._tcp.dc._msdcs.rooke.local SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = rooketerm.rooke.local
_ldap._tcp.dc._msdcs.rooke.local SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = rookesbs.rooke.local
server-ad.rooke.local internet address = 192.168.1.21
server-ad.rooke.local AAAA IPv6 address = 2001:0:9d38:6ab8:20b5:74ee:2bfd:eff5
rooketerm.rooke.local internet address = 192.168.1.5
rookesbs.rooke.local internet address = 192.168.1.3
This all appears OK to me :)
Also SHOWREPL results
Repadmin: running command /showrepl against full DC localhost
Default-First-Site-Name\SERVER-AD
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 66f0b91a-f210-4a53-a1a9-4f585114c181
DSA invocationID: 15db3e56-e573-4c7e-a487-4a9259e7b6bd
==== INBOUND NEIGHBORS ======================================
DC=Rooke,DC=local
Default-First-Site-Name\ROOKETERM via RPC
DSA object GUID: bad19e19-a045-410f-8854-5d06d7cb5bb1
Last attempt @ 2014-03-12 18:26:07 was successful.
Default-First-Site-Name\ROOKESBS via RPC
DSA object GUID: 11aecea4-d53e-48b8-9c68-f996cca7e72e
Last attempt @ 2014-03-12 18:28:44 was successful.
CN=Configuration,DC=Rooke,DC=local
Default-First-Site-Name\ROOKESBS via RPC
DSA object GUID: 11aecea4-d53e-48b8-9c68-f996cca7e72e
Last attempt @ 2014-03-12 18:08:39 was successful.
Default-First-Site-Name\ROOKETERM via RPC
DSA object GUID: bad19e19-a045-410f-8854-5d06d7cb5bb1
Last attempt @ 2014-03-12 18:08:52 was successful.
CN=Schema,CN=Configuration,DC=Rooke,DC=local
Default-First-Site-Name\ROOKESBS via RPC
DSA object GUID: 11aecea4-d53e-48b8-9c68-f996cca7e72e
Last attempt @ 2014-03-12 18:08:28 was successful.
Default-First-Site-Name\ROOKETERM via RPC
DSA object GUID: bad19e19-a045-410f-8854-5d06d7cb5bb1
Last attempt @ 2014-03-12 18:08:32 was successful.
DC=ForestDnsZones,DC=Rooke,DC=local
Default-First-Site-Name\ROOKESBS via RPC
DSA object GUID: 11aecea4-d53e-48b8-9c68-f996cca7e72e
Last attempt @ 2014-03-12 18:08:28 was successful.
DC=DomainDnsZones,DC=Rooke,DC=local
Default-First-Site-Name\ROOKESBS via RPC
DSA object GUID: 11aecea4-d53e-48b8-9c68-f996cca7e72e
Last attempt @ 2014-03-12 18:08:28 was successful.
DCDIAG
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
* Verifying that the local machine SERVER-AD, is a Directory Server.
Home Server = SERVER-AD
* Connecting to directory service on server SERVER-AD.
* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=Rooke,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
The previous call succeeded
Iterating through the sites
Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
Getting ISTG and options for the site
* Identifying all servers.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=Rooke,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
The previous call succeeded....
The previous call succeeded
Iterating through the list of servers
Getting information for the server CN=NTDS Settings,CN=ROOKESBS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
Getting information for the server CN=NTDS Settings,CN=ROOKETERM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
Getting information for the server CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.
* Found 3 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SERVER-AD
Starting test: Connectivity
* Active Directory LDAP Services Check
Determining IP4 connectivity
* Active Directory RPC Services Check
......................... SERVER-AD passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SERVER-AD
Starting test: Advertising
Warning: DsGetDcName returned information for \\rookesbs.Rooke.local,
when we were trying to reach SERVER-AD.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
......................... SERVER-AD failed test Advertising
Test omitted by user request: CheckSecurityError
Test omitted by user request: CutoffServers
Starting test: FrsEvent
* The File Replication Service Event log test
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
A warning event occurred. EventID: 0x800034FD
Time Generated: 03/12/2014 16:42:38
Event String:
File Replication Service is initializing the system volume with data from another domain controller. Computer SERVER-AD cannot become a domain controller until this process is complete. The
system volume will then be shared as SYSVOL.
To check for the SYSVOL share, at the command prompt, type:
net share
When File Replication Service completes the initialization process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication
interval between domain controllers.
A warning event occurred. EventID: 0x800034C8
Time Generated: 03/12/2014 16:42:39
Event String:
The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer SERVER-AD. The File Replication Service might
not recover when power to the drive is interrupted and critical updates are lost.
A warning event occurred. EventID: 0x800034C4
Time Generated: 03/12/2014 16:44:19
Event String:
The File Replication Service is having trouble enabling replication from rookesbs.Rooke.local to SERVER-AD for c:\windows\sysvol\domain using the DNS name rookesbs.Rooke.local. FRS will keep
retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name rookesbs.Rooke.local from this computer.
[2] FRS is not running on rookesbs.Rooke.local.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
A warning event occurred. EventID: 0x800034C4
Time Generated: 03/12/2014 16:52:19
Event String:
The File Replication Service is having trouble enabling replication from ROOKETERM to SERVER-AD for c:\windows\sysvol\domain using the DNS name rooketerm.Rooke.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name rooketerm.Rooke.local from this computer.
[2] FRS is not running on rooketerm.Rooke.local.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
A warning event occurred. EventID: 0x800034C4
Time Generated: 03/12/2014 16:52:20
Event String:
The File Replication Service is having trouble enabling replication from ROOKESBS to SERVER-AD for c:\windows\sysvol\domain using the DNS name rookesbs.Rooke.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name rookesbs.Rooke.local from this computer.
[2] FRS is not running on rookesbs.Rooke.local.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
A warning event occurred. EventID: 0x800034FE
Time Generated: 03/12/2014 17:42:51
Event String:
File Replication Service is scanning the data in the system volume. Computer SERVER-AD cannot become a domain controller until this process is complete. The system volume will then be shared
as SYSVOL.
To check for the SYSVOL share, at the command prompt, type:
net share
When File Replication Service completes the scanning process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.
A warning event occurred. EventID: 0x800034C8
Time Generated: 03/12/2014 17:42:51
Event String:
The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer SERVER-AD. The File Replication Service might
not recover when power to the drive is interrupted and critical updates are lost.
A warning event occurred. EventID: 0x800034C4
Time Generated: 03/12/2014 17:44:32
Event String:
The File Replication Service is having trouble enabling replication from rookesbs.Rooke.local to SERVER-AD for c:\windows\sysvol\domain using the DNS name rookesbs.Rooke.local. FRS will keep
retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name rookesbs.Rooke.local from this computer.
[2] FRS is not running on rookesbs.Rooke.local.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
......................... SERVER-AD passed test FrsEvent
Starting test: DFSREvent
The DFS Replication Event Log.
Skip the test because the server is running FRS.
......................... SERVER-AD passed test DFSREvent
Starting test: SysVolCheck
* The File Replication Service SYSVOL ready test
The registry lookup failed to determine the state of the SYSVOL. The
error returned was 0x0 "The operation completed successfully.".
Check the FRS event log to see if the SYSVOL has successfully been
shared.
......................... SERVER-AD passed test SysVolCheck
Starting test: KccEvent
* The KCC Event log test
Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
......................... SERVER-AD passed test KccEvent
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
Role Domain Owner = CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
Role PDC Owner = CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
Role Rid Owner = CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
Role Infrastructure Update Owner = CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
......................... SERVER-AD passed test KnowsOfRoleHolders
Starting test: MachineAccount
Checking machine account for DC SERVER-AD on DC SERVER-AD.
* SPN found :LDAP/SERVER-AD.Rooke.local/Rooke.local
* SPN found :LDAP/SERVER-AD.Rooke.local
* SPN found :LDAP/SERVER-AD
* SPN found :LDAP/SERVER-AD.Rooke.local/ROOKE
* SPN found :LDAP/66f0b91a-f210-4a53-a1a9-4f585114c181._msdcs.Rooke.local
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/66f0b91a-f210-4a53-a1a9-4f585114c181/Rooke.local
* SPN found :HOST/SERVER-AD.Rooke.local/Rooke.local
* SPN found :HOST/SERVER-AD.Rooke.local
* SPN found :HOST/SERVER-AD
* SPN found :HOST/SERVER-AD.Rooke.local/ROOKE
* SPN found :GC/SERVER-AD.Rooke.local/Rooke.local
......................... SERVER-AD passed test MachineAccount
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC SERVER-AD.
The forest is not ready for RODC. Will skip checking ERODC ACEs.
* Security Permissions Check for
DC=DomainDnsZones,DC=Rooke,DC=local
(NDNC,Version 3)
* Security Permissions Check for
DC=ForestDnsZones,DC=Rooke,DC=local
(NDNC,Version 3)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=Rooke,DC=local
(Schema,Version 3)
* Security Permissions Check for
CN=Configuration,DC=Rooke,DC=local
(Configuration,Version 3)
* Security Permissions Check for
DC=Rooke,DC=local
(Domain,Version 3)
......................... SERVER-AD passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Unable to connect to the NETLOGON share! (\\SERVER-AD\netlogon)
[SERVER-AD] An net use or LsaPolicy operation failed with error 67,
The network name cannot be found..
......................... SERVER-AD failed test NetLogons
Starting test: ObjectsReplicated
SERVER-AD is in domain DC=Rooke,DC=local
Checking for CN=SERVER-AD,OU=Domain Controllers,DC=Rooke,DC=local in domain DC=Rooke,DC=local on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local in domain CN=Configuration,DC=Rooke,DC=local on 1 servers
Object is up-to-date on all servers.
......................... SERVER-AD passed test ObjectsReplicated
Test omitted by user request: OutboundSecureChannels
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=DomainDnsZones,DC=Rooke,DC=local
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency
information (Win2K DC).
DC=ForestDnsZones,DC=Rooke,DC=local
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency
information (Win2K DC).
CN=Schema,CN=Configuration,DC=Rooke,DC=local
Latency information for 5 entries in the vector were ignored.
5 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency
information (Win2K DC).
CN=Configuration,DC=Rooke,DC=local
Latency information for 5 entries in the vector were ignored.
5 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency
information (Win2K DC).
DC=Rooke,DC=local
Latency information for 5 entries in the vector were ignored.
5 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency
information (Win2K DC).
......................... SERVER-AD passed test Replications
Starting test: RidManager
* Available RID Pool for the Domain is 5607 to 1073741823
* SERVER-AD.Rooke.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 5107 to 5606
* rIDPreviousAllocationPool is 5107 to 5606
* rIDNextRID: 5107
......................... SERVER-AD passed test RidManager
Starting test: Services
* Checking Service: EventSystem
* Checking Service: RpcSs
* Checking Service: NTDS
* Checking Service: DnsCache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: w32time
* Checking Service: NETLOGON
......................... SERVER-AD passed test Services
Starting test: SystemLog
* The System Event log test
Found no errors in "System" Event log in the last 60 minutes.
......................... SERVER-AD passed test SystemLog
Test omitted by user request: Topology
Test omitted by user request: VerifyEnterpriseReferences
Starting test: VerifyReferences
The system object reference (serverReference)
CN=SERVER-AD,OU=Domain Controllers,DC=Rooke,DC=local and backlink on
CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
are correct.
The system object reference (serverReferenceBL)
CN=SERVER-AD,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=Rooke,DC=local
and backlink on
CN=NTDS Settings,CN=SERVER-AD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Rooke,DC=local
are correct.
The system object reference (frsComputerReferenceBL)
CN=SERVER-AD,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=Rooke,DC=local
and backlink on CN=SERVER-AD,OU=Domain Controllers,DC=Rooke,DC=local
are correct.
......................... SERVER-AD passed test VerifyReferences
Test omitted by user request: VerifyReplicas
Test omitted by user request: DNS
Test omitted by user request: DNS
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : Rooke
Starting test: CheckSDRefDom
......................... Rooke passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Rooke passed test CrossRefValidation
Running enterprise tests on : Rooke.local
Test omitted by user request: DNS
Test omitted by user request: DNS
Starting test: LocatorCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
PDC Name: \\SERVER-AD.Rooke.local
Locator Flags: 0xe00071fd
Time Server Name: \\rookesbs.Rooke.local
Locator Flags: 0xe00001f8
Preferred Time Server Name: \\rookesbs.Rooke.local
Locator Flags: 0xe00001f8
KDC Name: \\rookesbs.Rooke.local
Locator Flags: 0xe00001f8
......................... Rooke.local failed test LocatorCheck
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... Rooke.local passed test Intersite -
Namespace Errors System Error 1355 - Specified domain does not exist or could not be contacted
Ok, lets start with my environment:
dc1 - windows server 2003 r2
dc2 - windows server 2012 r2
fs1- windows server 2003 r2
fs2 - windows server 2012 r2
Namespace - \\<fqdn>\data (the fqdn would be like contoso.microsoft.com)
I am in the process of migrating everything from server1 to server2 (dc and fs listed above). I am done with mostly everything except DFS. I have migrated the data, setup permissions, shares, etc. and replicated the data between fs1 and fs2.
I have verified that all data is currently replicated and up to date, so no backlogs. I am trying to add dc2 and fs2 as namespace servers. This is so that I can point all of the referrals to FS2 that way when I remove FS1 no one gets an error
about not being able to find the files. The problem is that from all 4 servers, I receive an error message when loading the namespace via DFS Management tool. I then thought because of the drastic differences between the versions, the next best
thing would be to export the namespace and then import it into the new server, but even attempting the export command (dfsutil) gives me the same error. My suspect is that the original namespace server was removed sometime ago without the previous IT
person properly migrating everything (but I am at a loss cuz here I am). I then thought if I go through ADSIedit, I can change the namespace server to the new one for all of my shares, and then possibly be able to load the namespace within the MMC tool
(again just a guess); however, I cannot find anything listed for namespace or remoteservers under the properties of the share.
Note: the namespace does work when I navigate to it from a PC. \\contoso.microsoft.com\data does bring up folders and files. (changed the name for obvious reasons)
At this point, I just want to have my new namespace server, so that I can change the referrals, and decommission my other servers. (And yes there are many other steps I need to perform for the decommissioning, but that's not the point of this). I
have read numerous articles on this and haven't found a way to accomplish what I want. Even though I walked through the steps listed for those issues and unfortunately they either did not apply or did not work. I prefer to not use ADSIedit if at
all possible, simply because it's not the "clean" way of doing things, but if I have no other option then I have no other option.
Edit 1: In event viewer on dc1, under File Replication Service on the left hand side, I see the following error appear numerous times (not every day, but still a lot). I have not performed any of the steps listed simply because
I do not know if this pertains to my problem and I don't want to start troubleshooting a server I plan on decommissioning unless I need to (say for the above issue):
Event ID: 13568
Source: NtFrs
Description:
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication
Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Edit 2: I have verified that firewalls are off and I can communicate to all 4 servers from each other.
Edit 3: Attempted to try and fix error reported in 'Edit 1'; however the registry key mentioned does not exist (looked at all 4 servers to verify).I think in your situation it would be worth trying the things listed under the event. It does have to do with FRS and it's easy to do. I've used it to fix journal errors after a server unexpectedly restarts and sysvol stops replicating. I
could see where it could fix your issue, and if it doesn't, you're out 5 minutes. :)
The listed registry key does not exist
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
-
DAC, ETL failed due to Post-Etl Script not exist and table not exist.
When execute the ETL in DAC, it failed when execute the "Change Capture For Siebel OLTP"
encounterred the following two type errors.
how to fix these errors?
The first is the table not exist:
======================================================================
MESSAGE:::Could not truncate table 'S_ETL_I_IMG_38' because this table does not exist in database 'OLTP_SIA'.
EXCEPTION CLASS::: com.microsoft.sqlserver.jdbc.SQLServerException
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
======================================================================
The second is the Post-Etl not exist.
I have copied the Copy Source Files and Lookup Files. What else should I do? What script it not find? have no idea.
======================================================================
Jan 20, 2009 4:11:06 PM com.siebel.etl.etlmanager.EtlExecutionManager finishEtl
SEVERE: Incorrectly specified Post-Etl Script/Executable. The file either does n
ot exist, or is not readable
UNREGISTERING: com.siebel.etl.engine.bore.FixedFailedNodesFacility
686 SEVERE Tue Jan 20 16:11:06 CST 2009
END OF ETL
687 SEVERE Tue Jan 20 16:11:06 CST 2009 Incorrectly specified Post-Etl Script
/Executable. The file either does not exist, or is not readable
UNREGISTERING: com.siebel.etl.engine.core.SessionHandler
UNREGISTERING: com.siebel.etl.engine.bore.ServerTokenPool
UNREGISTERING: com.siebel.etl.engine.core.TableIndexHandler
UNREGISTERING: com.siebel.etl.engine.bore.NewDispatcher
Stopping EtlParameters 9550256
UNREGISTERING: com.siebel.etl.engine.bore.EtlParameters
UNREGISTERING: com.siebel.etl.engine.bore.ExternalTaskTokenPool
UNREGISTERING: com.siebel.analytics.etl.execution.RefreshDateHandlerHi tigger,
ad scripts:
http://download.oracle.com/docs/cd/E12102_01/books/AnyInstAdm784/AnyInstAdmFunctionalRef9.html#wp1005877
http://download.oracle.com/docs/cd/E12102_01/books/AnyInstAdm784/AnyInstAdmFunctionalRef8.html
ad tables:
Without data change capture tables nothing will work. Have you looked at the actual documentaiotn? It contains everythign step by step.
http://www.oracle.com/technology/documentation/bi_apps.html
--> Oracle Business Intelligence Applications Fusion Edition Installation and Configuration Guide -> 4.15.3 How to Update Siebel Transactional Database Schema Definitions -
Error when opening indd-file: Either the file does not exist, you do not have permission, or the...
Hi! I'm having trouble opening a indd-file. It was sent to me as a zip-fil along with the used fonts and links. When I try to open the file, I'm getting this error: "Either the file does not exist, you do not have permission, or the file may be in use by another application". I've tried to look up this error both here in these forums and through google, but can't find a similar case. Hope someone can help me with this. Please let me know if you need more information/details, and I'll provide. Thanks!
function(){return A.apply(null,[this].concat($A(arguments)))}
I'm suspecting it to come from a mac user, if that could influence the case...
It does come from a Mac, as is proven by the fonts, which are of no use on my Windows machine, but that doesn't prevent my CS4 to open it without any problem. It seems to me it's a perfectly regular CS2 file.
Just for cheers I set the file to Read-only, but my InDesign opens it regardless (again as a copy, because it's a "converted" file).
Could it be something in your environment? No network read/write privileges, insufficient free hard disk space, stuff like that? -
The user does not exist or is not unique - workflow problem
I am using Solution Starters Dynamic Management workflow on my Project Server 2010. I was working fine for a year now, but today all workflows were broken when someone tried to submit them to a next stage. "Workflow terminated. An error has occurred
in the workflow."
I tried debbuging the workflow and it seems to be OK, but the problem appears when it needs to assign tasks to the approvers (they are in the Approvers group). When I remove users from the group that represents approvers (and leave that group empty), it
works fine, so I am guessing that users (who need to approve the stage) are the problem. My administrators are saying that there were no updates or changes on AD machine.
I don't have problem with users in any of people picker fields or anywhere else on the site. I am using claims auth.
What could be the reason for this behavior??
These are main errors from the log:
Failed to persist workflow instance: 7dc2e035-cd02-4284-b851-a829e372a809 with error code: 5, instance data size: 29578, internal state: Running, processing id: 1e2211d2-ef7b-4416-90ef-ac041396c200 2f83db27-34da-4275-a42e-0625240af921
The user does not exist or is not unique.
WinWF Internal Error, terminating workflow Id# 7dc2e035-cd02-4284-b851-a829e372a809
System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. Parameter name: additionalNodes at Microsoft.Office.Workflow.Actions.OfficeTask.ProcessTaskError(Object sender, EventArgs e)
at System.Workflow.ComponentModel.ActivityExecutorDelegateInfo`1.ActivityExecutorDelegateOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime) at System.Workflow.Runtime.Scheduler.Run()It appears that this isn't the problem with users, but it is a problem with Office Tasks. This is the main error in ULS logs (same as in the previous post):
"Specified argument was out of the range of valid values. Parameter name: additionalNodes"
I noticed that all content types are gone from my pwa site. Is it possible that my workflow is causing problems when adding tasks because somebody deleted all content types?? -
ORA-15001: diskgroup "FRA" does not exist or is not mounted
Dear Experts,
We noticed the error "ORA-15001: diskgroup "FRA" does not exist or is not mounted" on the 2nd node of our 4 nodes RAC database system.
During this weekend, we moved our system to a new data center. After the move was done, we were able to bring up the 4 instances around 3:00 AM. However, 4 hours later (7:00 AM), OEM Grid control alerted us with "archival error" on the 2nd instance. From our investigating, we saw the FRA was dismounted. Below is the oracle alert log file (For secuirty reson, the SID is modified):
Sat Feb 7 03:46:03 2009
Completed: ALTER DATABASE OPEN
Sat Feb 7 03:50:18 2009
Sat Feb 7 07:01:36 2009
Thread 2 advanced to log sequence 8534
Current log# 3 seq# 8534 mem# 0: +REDOGRPA/xyz/onlinelog/redo_03.log
Current log# 3 seq# 8534 mem# 1: +REDOGRPB/xyz/onlinelog/redo_03b.log
Sat Feb 7 07:01:39 2009
ARCH: Archival stopped, error occurred. Will continue retrying
Sat Feb 7 07:01:39 2009
ORACLE Instance XYZ2 - Archival Error
Sat Feb 7 07:01:39 2009
ORA-16038: log 11 sequence# 8533 cannot be archived
ORA-00254: error in archive control string ''
ORA-00312: online log 11 thread 2: '+REDOGRPA/xyz/onlinelog/redo_11.log'
ORA-00312: online log 11 thread 2: '+REDOGRPB/xyz/onlinelog/redo_11b.log'
ORA-15001: diskgroup "FRA" does not exist or is not mounted
ORA-15001: diskgroup "FRA" does not exist or is not mounted It is my understanding, that Oracle will automatically mount the diskgroups on the ASM when the instances are started. In our case, all other diskgroups are started OK but not the FRA diskgroup. Is this a bug with FRA where FRA can not be automatically started up after recycling the instance? Did anyone experience the same situation? Can someone advice?
Thanks!Hello,
We are running oracle 10.2.0.2.
Which section of the alert log file for +ASM2 we need here? I will paste it here the ones when "alter diskgroup all mounted" started at 3:00 AM all the way upto 4:00 AM on Saturday, Feb 7:
SQL> ALTER DISKGROUP ALL MOUNT
Sat Feb 7 03:44:15 2009
NOTE: cache registered group FRA' number=1 incarn=0x1e5bf0d2
NOTE: cache registered group DATAX number=2 incarn=0xbcabf0d1
NOTE: cache registered group REDO2 number=4 incarn=0x1e5bf0d3
NOTE: cache registered group REDOGRPA number=5 incarn=0xbcbbf0d4
NOTE: cache registered group REDOGRPB number=6 incarn=0xbcbbf0d5
NOTE: cache registered group TEMPX number=7 incarn=0xbcbbf0d6
NOTE: cache registered group TEMP number=8 incarn=0x1e6bf0d7
NOTE: cache registered group TIBDATA number=9 incarn=0xbcbbf0d8
NOTE: cache registered group TIBREDO number=10 incarn=0xbcbbf0d9
NOTE: cache registered group TIBTEMP number=11 incarn=0x1ebbf0da
Sat Feb 7 03:44:15 2009
ERROR: no PST quorum in group 1: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 1/0x1E5BF0D2 (FRA')
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup FRA' was not mounted
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 2)
ERROR: no PST quorum in group 4: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 4/0x1E5BF0D3 (REDO2)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup REDO2 was not mounted
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 5)
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 6)
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 7)
ERROR: no PST quorum in group 8: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 8/0x1E6BF0D7 (TEMP)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup TEMP was not mounted
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 9)
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 10)
ERROR: no PST quorum in group 11: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 11/0x1EBBF0DA (TIBTEMP)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup TIBTEMP was not mounted
NOTE: cache opening disk 0 of grp 2: DATAX_0000 path:/dev/raw/raw61
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 2/0xBCABF0D1 (DATAX)
Sat Feb 7 03:44:16 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:16 2009
NOTE: attached to recovery domain 2
Sat Feb 7 03:44:16 2009
NOTE: opening chunk 4 at fcn 0.1158090 ABA
NOTE: seq=54 blk=4821
Sat Feb 7 03:44:16 2009
NOTE: cache mounting group 2/0xBCABF0D1 (DATAX) succeeded
SUCCESS: diskgroup DATAX was mounted
NOTE: cache opening disk 0 of grp 5: REDOGRPA_0000 path:/dev/raw/raw20
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 5/0xBCBBF0D4 (REDOGRPA)
Sat Feb 7 03:44:16 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:16 2009
NOTE: recovering COD for group 2/0xbcabf0d1 (DATAX)
SUCCESS: completed COD recovery for group 2/0xbcabf0d1 (DATAX)
Sat Feb 7 03:44:16 2009
NOTE: attached to recovery domain 5
Sat Feb 7 03:44:16 2009
NOTE: opening chunk 4 at fcn 0.103802 ABA
NOTE: seq=43 blk=2123
Sat Feb 7 03:44:16 2009
NOTE: cache mounting group 5/0xBCBBF0D4 (REDOGRPA) succeeded
SUCCESS: diskgroup REDOGRPA was mounted
NOTE: cache opening disk 0 of grp 6: REDOGRPB_0000 path:/dev/raw/raw12
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 6/0xBCBBF0D5 (REDOGRPB)
Sat Feb 7 03:44:16 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:17 2009
NOTE: attached to recovery domain 6
Sat Feb 7 03:44:17 2009
NOTE: opening chunk 4 at fcn 0.75866 ABA
NOTE: seq=20 blk=1704
Sat Feb 7 03:44:17 2009
NOTE: cache mounting group 6/0xBCBBF0D5 (REDOGRPB) succeeded
SUCCESS: diskgroup REDOGRPB was mounted
NOTE: cache opening disk 0 of grp 7: TEMPX_0000 path:/dev/raw/raw71
NOTE: F1X0 found on disk 0 fcn 0.25328
NOTE: cache opening disk 1 of grp 7: TEMPX_0001 path:/dev/raw/raw7
NOTE: cache mounting (not first) group 7/0xBCBBF0D6 (TEMPX)
Sat Feb 7 03:44:17 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:17 2009
NOTE: attached to recovery domain 7
Sat Feb 7 03:44:17 2009
NOTE: opening chunk 4 at fcn 0.69473 ABA
NOTE: seq=42 blk=432
Sat Feb 7 03:44:17 2009
NOTE: cache mounting group 7/0xBCBBF0D6 (TEMPX) succeeded
SUCCESS: diskgroup TEMPX was mounted
NOTE: cache opening disk 0 of grp 9: TIBDATA path:/dev/raw/raw86
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 9/0xBCBBF0D8 (TIBDATA)
Sat Feb 7 03:44:17 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:17 2009
NOTE: attached to recovery domain 9
Sat Feb 7 03:44:17 2009
NOTE: opening chunk 4 at fcn 0.102912 ABA
NOTE: seq=12 blk=2050
Sat Feb 7 03:44:17 2009
NOTE: cache mounting group 9/0xBCBBF0D8 (TIBDATA) succeeded
SUCCESS: diskgroup TIBDATA was mounted
NOTE: cache opening disk 0 of grp 10: TIBREDO path:/dev/raw/raw87
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 10/0xBCBBF0D9 (TIBREDO)
Sat Feb 7 03:44:18 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:18 2009
NOTE: attached to recovery domain 10
Sat Feb 7 03:44:18 2009
NOTE: opening chunk 4 at fcn 0.18970 ABA
NOTE: seq=12 blk=6577
Sat Feb 7 03:44:18 2009
NOTE: cache mounting group 10/0xBCBBF0D9 (TIBREDO) succeeded
SUCCESS: diskgroup TIBREDO was mounted
Sat Feb 7 03:44:19 2009
NOTE: recovering COD for group 5/0xbcbbf0d4 (REDOGRPA)
SUCCESS: completed COD recovery for group 5/0xbcbbf0d4 (REDOGRPA)
NOTE: recovering COD for group 6/0xbcbbf0d5 (REDOGRPB)
SUCCESS: completed COD recovery for group 6/0xbcbbf0d5 (REDOGRPB)
NOTE: recovering COD for group 7/0xbcbbf0d6 (TEMPX)
SUCCESS: completed COD recovery for group 7/0xbcbbf0d6 (TEMPX)
NOTE: recovering COD for group 9/0xbcbbf0d8 (TIBDATA)
SUCCESS: completed COD recovery for group 9/0xbcbbf0d8 (TIBDATA)
NOTE: recovering COD for group 10/0xbcbbf0d9 (TIBREDO)
SUCCESS: completed COD recovery for group 10/0xbcbbf0d9 (TIBREDO)
Sat Feb 7 03:45:18 2009
Starting background process ASMB
ASMB started with pid=17, OS id=16122
Sat Feb 7 03:49:35 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Starting background process ASMB
ASMB started with pid=18, OS id=25963
Sat Feb 7 03:54:34 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Sat Feb 7 03:54:50 2009
Starting background process ASMB
ASMB started with pid=18, OS id=913
Sat Feb 7 03:57:55 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Sat Feb 7 04:07:26 2009
Starting background process ASMB
ASMB started with pid=21, OS id=23012
Sat Feb 7 04:13:59 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Starting background process ASMB
ASMB started with pid=22, OS id=31320
Sat Feb 7 04:36:43 2009
NOTE: ASMB process exiting due to lack of ASM file activity -
ORA-15001: diskgroup "DATA" does not exist or is not mounted in 11gR2
Dear all,
the system is HP-UX 11.31
the new RAC infrastructure is 11gR2 11.2.0.2 (2nodes using ASM)
i am restoring the 10G 10.2.0.4 database to this infrastructure
copy binary files over to new oracle home,
relink all binaries with option rac_off
--startup nomount
--restore controlfile
--mount database
--catalog the restore files
then run restore
run {
restore database ;
recover database;
i always get this error, i did not see this error in 11gR1( restore few times to 11gR1)
verified the diskgroup DATA and i was mounted
ORA-19504: failed to create file "+DATA/OCP/data1.dbf"
ORA-17502: ksfdcre:3 Failed to create file +DATA/OCP/data1.dbf
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
Please give me an advice.
Thanks,found this note in Metalink and it had solved my issue.
Unable To Create 10.1 or 10.2 or 11.1(< 11gR2) ASM RAC Databases (ORA-29702) Using Brand New 11gR2 Grid Infrastructure Installation . [ID 946332.1] -
I'm running ColdFusion 8 Enterprise on linux. I'm able to
create collections and index them through cfadmin as well as in cfm
application pages, but when trying to search I get the error
"The collection you specified does not exist or is not
registered with the ColdFusion Search Service."
I'm using the collection name in cfsearch and not the full
path.Would I have been better off posting this in the General
Discussion section? Could the moderators move it if so,
please? -
Sintax error in COPA- Table T2580 does not exist or is not active
hi to all
i am doing configuration for T.C KES1 in CO-PA
while doing this i am getting SINTAX ERROR saying that T2580 DOES NOT EXIST OR IS NOT ACTIVE.
I checked with standard program this table is used by standard SAP PROGRAM
programe name SAPL0KEA
but this table contain no data
could please some help on this
v v urgentHi Hari,
This is a know issue in CO-PA. You need to apply three notes and the issue will be resolved.
Please run report RKEAGENV as described in the attached 64490.
If running report RKEAGENV will cause another error concerning operating concern E_B1 please copy the report ZJBREOFC from the correction in-
structions in the attached note 872175, activate and execute it.
If after applying note 872175 you receive a new short dump, please
execute report RKEAGENF to eliminate the error so that the program
RKEAGENV could then be executed without error and thus the characteris-
tic maintenance should work again.
Please also implement note 942785 into your system.
Regards,
Abhisek. -
Adding to a task list - User does not exist or is not unique
We have SharePoint 2010 with a single web server front end and another server as the SQL server. When trying to add a task to a list or an announcement to a page, users are getting the error, "The user does not exist or is not unique."
I have searched diligently for an answer, but cannot find anything about this with regards to users getting the error.
Thank you in advance for your assistance.hello,
i have faced your problem few minutes ago. when i was trying to solve another problem
--->> (Object Cache: The super user account utilized by the cache is not configured) --> my current problem
i have found at search results the below PS command to configure super user and super reader.
$w = Get-SPWebApplication http://webapplicationlink
$w.Properties["portalsuperuseraccount"] = "domain account"
$w.Properties["portalsuperreaderaccount"] = "domain account"
$w.Update()
but it caused me another problem which you are facing right now.
---> ( Error: The user does not exist or is not unique)
while adding any item to any list specially lists
then i have tried to rollback by doing the below PS command and it worked and solved it.
$w = Get-SPWebApplication http://webapplicationlink
$w.Properties["portalsuperuseraccount"] = ""
$w.Properties["portalsuperreaderaccount"] = ""
$w.Update()
after that check for the super user and super reader by
Get-SPWebApplication | %{Write-Host "Web Application: " $_.url "`nSuper user: " $_.properties["portalsuperuseraccount"] "`nSuper reader: " $_.properties["portalsuperreaderaccount"] "`n"}
This is the output for the above command should be like this.
Web Application: http://webapplicationlink
Super user:
Super reader:
hope that it helps :)
Karim El Zarka,Senior IT Specialist Commercial International Bank, MCTS Sharepoint -
"The company code does not exist or has not been fully maintained" in mm01
Hi all,
I am creating a material, it needs me to provide company code. when I gave out my company code, it reports:
"The company code ZXXX does not exist or has not been fully maintained".
what should the problem be?
thanks and regards,
Smaosn ZhuHi Raja,
Checked all you specified.
I have done these assignments:
1. assign comp - > comp code
2. assign plant- > comp code
3. assign purch. org - > comp code
4. assign purch. org - > plant
but the problem is still there.
let me try to re-do it.
thanks,
samson
Maybe you are looking for
-
I have two monitors. I have an application that I run all day, displayed on my secondary monitor. Whenever a popup windows is launched form that application, it always opens on the primary monitor. Very annoying. Any way to get the popup to launch in
-
at the time of refreshment, while creating the control file i got the following error ora 01503 cannot create controlfile, ora-01100 database already mounted
-
Ipad won't turn on after 4.2.1 upgrade
After I upgraded my Ipad to the new os 4.2.1 it won't turn on. Before upgrading we all know that you turn it on by clicking the on and off switch or pushing the belly button in the middle, but now nothing happens at all. I have found that if I hold b
-
Trouble installing CS4 in Windows 7 64-bit
Has anybody else had trouble installing CS4 into Windows 7 Pro 64-bit? I had this suite installed in XP (32-bit) and it worked just fine, but it will not install on my new computer. The first time I tried, it got partway in (past the serial number)
-
My iPad phone number is hide in facetime
my iPad phone number is hide in facetime why? how i do show the number in facetime? i upgrade to iO7. please tell me how? why?