FREQUENT FAILURES AND ERRORS:PLZ

can any one send some frequent failures and errors.with sol if possible.

Prasanth
Check these weblogs. Hope these helps.
Thnaks
Sat
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Re: dataloading problems from r/3 ?

Similar Messages

Windows 7 Starter, System Image Failure and Error 0x80070715 results in Command Prompt

Dear all
Hi. My laptop CPU is 1.8 GHz, RAM 1 GB, Windows 7 Starter 32-Bit, hard drive: 30 GB for System, antivirus: Microsoft Security Essentials. Creating system image in Windows 7 does not progress in my laptop so I typed regsvr32
/i swprv.dll in
administrator command prompt, the result was error: 0x80070715.
Stop/ Start VSC in Services menu, typing command SFC in adm. Command Prompt, and Clean Boot all were unsuccessful.
Would you do me a favour about this issue, please?
Kind regards

I have the same issue.
I am following a Microsoft procedure to re-register DLLs to resolve a VSS error. At this point, an error occurred. I did:
> net stop vss
> net stop swprv
> regsvr32 ole32.dll
> regsvr32 vss_ps.dll
> vssvc /register
> regsvr32 /I swprv.dll
Error:
The module "swprv.dll" was loaded but the call to DllRegisterServer failed with error code 0x80070715.
For more information about this problem, search online use error code as a search term."
Windows 7 pro 64-bit.

Process chain failures and errors therein

Hi all,
Can anyone please guide me as to why the process chain fails?
what are the various kind of errors most often encountered? and how we can recifty them.....???
Your kind suggestions are thankfully acknowledged,
thanks and regards,
shalini.

Hi Shalini,
Process Chain fails due to several reasons. if you come up with any questions our masters will guide you.
Process Chain fails mainly due to data problem.
Regards,
Nagesh.

WSUS service failure and uninstall error 0x80070643

Hello
I recently had a drive fail in a RAID 1 array on a Windows Server 2008 Standard SP2 domain controller. The drive was replaced and the array successfully rebuilt the drive. Our domain comprises a Win2k8 DC (which WSUS is installed on), a W2k3 DC, a W2k8 Storage
Server and various W2k, Win XP, Vista and W7 clients.
WSUS3 SP2 is installed on this computer and had been working fine. After the drive was rebuilt WSUS stopped working. WSUS is organised as follows:
The drive is divided into 3 partitions. C: contains the program files, D: contains the WSUS database and update files. E: is a system recovery partition.
After the drive was rebuilt I had a problem connecting to the WSUS console. I am logged on using the domain administrator account. I restarted the server last night in the hope that it would solve this issue. After restarting, the problem persists. When
I start Windows Server Update Services from Administrative Tools the centre pane shows a large red X and 'Error: Connection Error'. The option to 'Reset Server Node' results in the same error. The error, available from 'Copy Error to Clipboard' is:
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.
System.IO.IOException -- The handshake failed due to an unexpected packet format.
Source
System
Stack Trace:
 at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
 at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
 at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
 at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
 at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
 at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
 at System.Net.TlsStream.CallProcessAuthentication(Object state)
 at System.Threading.ExecutionContext.runTryCode(Object userData)
 at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
 at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
 at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
 at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
 at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
 at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
 at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **
System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.
Source
Microsoft.UpdateServices.Administration
Stack Trace:
 at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
 at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
 at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
 at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
 at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
 at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
 at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)
The event logs show that the Update Services service started 7mins after the server was restarted. This is immediately followed by an event stating the Windows Update service had started. If fails soon after and is restared automatically twice to try to
recover from the failure. 12 hours after the restart the Update Services service is still not running. It is set to Automatic (Delayed Start). The service is set to logon as 'Network Service'. The service can be manually started, but 'Resert Server Node' again
results in the same error. After 4mins the service will stop. Event 7034 is logged:
Log Name: System
Source: Service Control Manager
Date: 31/08/2011 09:05:50
Event ID: 7034
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Phobos.htlincs.local
Description:
The Update Services service terminated unexpectedly. It has done this 4 time(s).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name="Service Control Manager" Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}" EventSourceName="Service Control Manager" />
 <EventID Qualifiers="49152">7034</EventID>
 <Version>0</Version>
 <Level>2</Level>
 <Task>0</Task>
 <Opcode>0</Opcode>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2011-08-31T08:05:50.000Z" />
 <EventRecordID>230471</EventRecordID>
 <Correlation />
 <Execution ProcessID="0" ThreadID="0" />
 <Channel>System</Channel>
 <Computer>Phobos.htlincs.local</Computer>
 <Security />
</System>
<EventData>
 <Data Name="param1">Update Services</Data>
 <Data Name="param2">4</Data>
</EventData>
</Event>
IIS and SQL are running fine as far as I am aware. I also have Sophos Enterprise Console installed which uses SQL to store it's data and that is working fine.
After a bit of searching around the 'net I thought the easiest solution would be to uninstall WSUS, leave the database and update files in place and then re-install. I ran the uninstallation procedure from the Server Manager, but because the service is not
running, and even after starting the service, uninstallation fails:
Windows Server Update Services: Removal failed
 Error: Attempt to un-install Windows Server Update Services failed with error code 0x80070643. Fatal error during installation
I saw a reference to the online article located here:
http://blogs.technet.com/b/sus/archive/2008/11/05/how-to-manually-remove-all-of-wsus.aspx but the article states it is out of date and I did not want to make a bad situation worse by following the instructions.
Can anyone help me with this, please. Ideally, I would like to be able to keep the updates as downloading them again will consume a substantial amount of our monthly allowance. However, if the best thing is to remove the entire installation, then I will
ahppily go with that, too.
Thanks.

I'm experiencing this issue, but haven't been able to resolve it with the steps in Lawrence's post (and, another thanks from me for another detailed post from Lawrence!)
It's a 2008 box which had a relatively new WSUS install that just stopped working - not sure why. Unable to figure out why it had stopped, I tried to Remove the WSUS role, but that failed with the error above.
During the manual uninstall steps above...
(1) Using Windows Installer Cleanup Utility only showed the Windows Internal Database, not WSUS. I removed
that.
(2) Removed %ProgramFiles%\Update
Services - other resources not present
Reinstall has now failed with this error:
Windows Server Update Services 3.0 SP2 could not install Windows Internal Database. For more information, see the Setup log "C:\Users\NAME~1.ADM\AppData\Local\Temp\WSUSSetup.log".
2012-10-23 20:57:53 Success MWUSSetup Detected that setup was launched through Server Manager
2012-10-23 20:57:54 Success MWUSSetup Validating pre-requisites...
2012-10-23 20:57:54 Error MWUSSetup Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
2012-10-23 20:57:54 Error MWUSSetup WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
2012-10-23 20:57:57 Success MWUSSetup Incompatible version of ReportViewer installed. Required ReportViewer version: 9.
2012-10-23 20:57:57 Success MWUSSetup Incompatible version of ReportViewer installed. Required ReportViewer version: 9.
2012-10-23 20:58:25 Success MWUSSetup Initializing installation details
2012-10-23 20:58:25 Success MWUSSetup Skipping Asp.Net install since not running on win2k3...
2012-10-23 20:58:25 Success MWUSSetup Installing wYukon using ocsetup
2012-10-23 20:58:25 Success MWUSSetup Installing Windows Internal database using ocsetup with command line as "ocsetup "WSSEE" /quiet /norestart"
2012-10-23 20:58:49 Error MWUSSetup The process ocsetup "WSSEE" /quiet /norestart returned error: 0x643 (Error 0x80070643: Fatal error during installation.)
2012-10-23 20:58:49 Error MWUSSetup ExecCmd failed (Error 0x80070643: Fatal error during installation.)
2012-10-23 20:58:49 Error MWUSSetup Install Windows Internal database: Failed to execute "ocsetup "WSSEE" /quiet /norestart" (Error 0x80070643: Fatal error during installation.)
2012-10-23 20:58:49 Error MWUSSetup CInstallDriver::PerformSetup: Installation of wYukon failed (Error 0x80070643: Fatal error during installation.)
2012-10-23 20:58:49 Error MWUSSetup CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
Would anyone on the thread have suggestions for what I might be able to do, to wipe the slate clean with the Internal
Database on this box?
The WID is not used for anything else, but there is other production software installed, (using SQL - not relevant, just
mentioning) and reinstalling the OS is not an option.

Since the Version 20.0 update when starting firefox I have frequently got the error message "firefox is having trouble your windows and tabs" .

Since the version 20.0 update when starting firefox I have frequently got the error message "firefox is having trouble recovering your windows and tabs" This has not occurred with previous versions. If I click on the box "restore" and close firefox the problem reoccurs if I click close I lose the bookmark sidebar. I am so sick and tired of these frequent and buggy updates (every one since 17.0 have caused norton 360 to stop detecting tracking cookies for several weeks and or broken the norton toolbar) that I will uninstall firefox and switch to another browser if this does not change.

See:
*http://kb.mozillazine.org/Firefox_crashes
*https://support.mozilla.org/kb/Firefox+crashes
If you have submitted crash reports then please post the IDs of one or more crash reports that have this format:
*bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
You can find the IDs of the submitted crash reports on the about:crashes page.
*You can open the about:crashes page via the location bar, like you open a website.
See:
*http://kb.mozillazine.org/Mozilla_Crash_Reporter
*https://support.mozilla.org/kb/Mozilla+Crash+Reporter

Hi All, I'm using an Iphone 4. Last friday my iphone dead and not able to turn it on. I have tried to connect to itunes Home button power button it say's Iphone in DFU mode and asking to recover but when i click on restore it gives 1644 error. plz sugg

Hi All,
I'm using an iphone 4.Last friday my iphone dead and not able to turn it on. I have tried to connect to itunes +Home button + power button it say's Iphone in DFU mode and asking to recover but when i click on restore it gives 1644 error. plz sugguest.
my os version: 4.2
Firmware: 02.10.04

FORCE IPAD INTO RECOVERY MODE
1. Turn off iPad
2. Turn on computer and launch iTunes (make sure you have the latest version of iTune)
3. Plug USB cable into computer's USB port
4. Hold Home button down and plug the other end of cable into docking port.
DO NOT RELEASE BUTTON until you see picture of iTunes and plug
5. Release Home button.
ON COMPUTER
6. iTunes has detected iPad in recovery mode. You must restore this iPad before it can be used with iTunes.
7. Select "Restore iPad"...
Note:
1. Data will be lost if you do not have backup
2. You must follow step 1 to step 4 VERY CLOSELY.

My IPhone 5s is frequently reboot and show the "blue screen"

My IPhone 5s is frequently reboot and show the "blue screen"
Error code:
{"bug_type":"110","os_version":"iOS 7.1.1 (11D201)"}
Incident Identifier: 9E7D62CD-E1FA-443F-81D7-91C2C4257098
CrashReporter Key:   7290c27dd593ba841d0e97282cc3b97158891820
Hardware Model:      iPhone6,1
Date/Time:           2014-05-12 00:16:32.851 +0300
OS Version:          iOS 7.1.1 (11D201)
panic(cpu 0 caller 0xffffff80042cd540): "LSU err reported via serror: 0x8820000000000017\n"
Debugger message: panic
OS version: 11D201
Kernel version: Darwin Kernel Version 14.0.0: Fri Mar 28 21:22:21 PDT 2014; root:xnu-2423.10.70~1/RELEASE_ARM64_S5L8960X
Kernel slide:     0x0000000003400000
Kernel text base: 0xffffff8003602000
Boot    : 0x536f9564 0x00000000
Sleep   : 0x536fe714 0x00073b45
Wake    : 0x536fe7f4 0x00000107
Calendar: 0x536fe89d 0x0007b3d4
Panicked task 0xffffff8085024c60: 16873 pages, 14 threads: pid 16: SpringBoard
panicked thread: 0xffffff8085cc6000, backtrace: 0xffffff8002d94b10
          0xffffff8003764a10
          0xffffff8003627968
          0xffffff8003605ce0
          0xffffff80042cd540
          0xffffff80042cd7a0
          0xffffff8003621394
          0x000000018f1256b4
Task 0xffffff8085025ba0: 38507 pages, 149 threads: pid 0: kernel_task
Task 0xffffff80850257d0: 321 pages, 3 threads: pid 1: launchd
Task 0xffffff8085025030: 1712 pages, 11 threads: pid 15: UserEventAgent
Task 0xffffff8085024c60: 16873 pages, 14 threads: pid 16: SpringBoard
Task 0xffffff8085024890: 838 pages, 2 threads: pid 17: installd
Task 0xffffff80850240f0: 465 pages, 4 threads: pid 19: fseventsd
Task 0xffffff8085023d20: 2053 pages, 2 threads: pid 20: vmd
Task 0xffffff8085023950: 2434 pages, 2 threads: pid 21: sharingd
Task 0xffffff8085023580: 1839 pages, 4 threads: pid 22: aosnotifyd
Task 0xffffff80850231b0: 1054 pages, 4 threads: pid 23: imagent
Task 0xffffff8085022a10: 1025 pages, 2 threads: pid 25: lockdownd
Task 0xffffff8085021ea0: 526 pages, 2 threads: pid 28: softwarebehavior
Task 0xffffff8085021ad0: 4005 pages, 30 threads: pid 29: mediaserverd
Task 0xffffff8085021330: 5819 pages, 17 threads: pid 31: backboardd
Task 0xffffff8085020f60: 410 pages, 3 threads: pid 32: AppleIDAuthAgent
Task 0xffffff8085020b90: 1197 pages, 3 threads: pid 33: routined
Task 0xffffff80850203f0: 568 pages, 2 threads: pid 35: wirelessproxd
Task 0xffffff808501fc50: 649 pages, 3 threads: pid 37: timed
Task 0xffffff808501f880: 250 pages, 7 threads: pid 38: syslogd
Task 0xffffff808501f0e0: 1627 pages, 5 threads: pid 40: wifid
Task 0xffffff808501e940: 1331 pages, 11 threads: pid 42: configd
Task 0xffffff808501e1a0: 1562 pages, 2 threads: pid 44: fairplayd.H2
Task 0xffffff808501d260: 1507 pages, 4 threads: pid 48: BTServer
Task 0xffffff808501c6f0: 707 pages, 3 threads: pi

    Rmbrown,
We'll get your phone working quickly again! Plz go to Settings>General>About and let us know the Available GB.
SarahO_VZW
Follow us on Twitter @VZWSupport

How to monitor OSD TS failure and get alert or report?

How to monitor OSD TS failure and get some alert or generate an report?
We have SCCM 2012 R2 CU1 with MDT 2013.
I have checked the OSD reports in SCCM and everyone is emty, where do SCCM get data to the what to activate?
(I thinking of "Task Sequence - Deployment Status" reports)
I am not sure people read report manually or lock at the MDT monitor view. So best I think that generate an email or incident in Service Manager when an TS fails.
We do have SCOM, SCSM, SCO.
Is there anyone that can point what way or what option I have?
/SaiTech

Specifically you could use this Status Message Query syntax to monitor your Task Sequences for errors:
select stat.*, ins.*, att1.*, att1.AttributeTime from SMS_StatusMessage as stat left join SMS_StatMsgInsStrings as ins on stat.RecordID = ins.RecordID left join SMS_StatMsgAttributes as att1 on stat.RecordID = att1.RecordID inner join SMS_StatMsgAttributes
as att2 on stat.RecordID = att2.RecordID where att2.AttributeID = 401 and att2.AttributeValue = "DOJ200A1" and stat.SiteCode = "DOJ" and att2.AttributeTime >= ##PRM:SMS_StatMsgAttributes.AttributeTime## order by att1.AttributeTime desc
Just replace DOJ200A1 with the Deployment ID of your Task Sequence and DOJ with your SiteCode.
If you want to generate an alert if the TS fails then you could run a script that calls a utility (or similar) which sends a pre-configured email to a specified address (as an alternative to Torten's response). This could be placed in the built in error
logging section of the SCCM integrated MDT Task Sequence when it fails which I assume you are using (right at the bottom, called Gather Logs and StateStore on failure).
There are heaps of ways of generating an email from a TS and controlling error logging just do a search - as you have Service Manager you could even use your instance of Orchestrator and call a run book in your TS which does the email?
Cheers
Damon

Word couldn't send mail because of MAPI failure, Unspecified error.

This issue is crossposted in Microsoft Answers Word and OUTLOOK. I am posting here in hopes that someone at Mircrosoft may have a solution or at least elevate the issue to someone who does.
http://answers.microsoft.com/en-us/office/forum/officeversion_other-word/word-could-not-send-mail-because-of-mapi-failure/f62678fe-ef1d-42b5-8cfe-1e43d6a1d609
http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/word-couldnt-send-mail-due-to-mapi-failure/1f03cf74-9258-411b-9e2b-e41cb5006d71
I dabble with VBA and write and maintain several amateur Word Add-Ins. Accordingly, I have Word 2003, 2007, 2010 and 2013 installed on my PC. They get along fine. However, I am unable to "Share" or "Send" an open Word
document as an E-mail attachment in any version! In each case Word returns an error mesage "Word couldn't send mail because of a MAPI failure, Unspecified error (the same issue occurs with Excel and Powerpoint except the error dialog is a bit different.)
Using Word 2003, I (CAN) "Send to (Mail recipient for review)" in which case OUTLOOK is opened with the document as an attachment. I can also "Send to Mail Recipient" from Windows Explorer, in which case the Word file is attached to
an OUTLOOK message, and I can create an instance of OUTLOOK and send mail from Word using VBA.
I have repaired all Office versions. I have removed the registry keys for all office versions and repaired all versions again. I have run "fixmapi" until I am blue in the face. I have renamed the MAPI32.DLL files and ran sfc \scannow
to ensure that the MAPI32.DLL file is not corrupt. In view of these actions and in view of what I can do, something tells me that the MAPI files are fine.
So what is this "Unspecified error?" This problem is rife on the internet and most of the "canned" solutions have been marked "Answered" by some MS support engineer. These "canned" solutions might have
fixed the issue at one point, but they don't work now. At least not for me.
Thanks.
Greg Maxey Please visit my website at: http://gregmaxey.mvps.org/word_tips.htm

Hello Greg,
I noted that there are 2 knowledge articles that describe scenarios where you may encounter this error.
KB 291152 You receive a "Word couldn't send mail because of MAPI failure" error message when you try to send a Word document as an e-mail attachment in Word 2002
http://support.microsoft.com/kb/291152/EN-US
KB 929362 You cannot send a file by clicking Send in a different program when Outlook 2007 is running as administrator
http://support.microsoft.com/kb/929362/EN-US
Please let me know the following:
1. What version of Outlook are you using?
2. Do you have Outlook open when you attempt the File > Share > Email as attachment from Word? If not, does the error occur if you open Outlook, open Word and then try to send the email?
3. If you close/reopen Word and then try the send again, do you get the same error?
4. Are you running either Outlook or Word in an elevated mode?
5. What happens if you start both Outlook and Word as "Run As Administrator". You may have to right-click each applications' .exe file to be able to choose the "Run As Administrator" option.
6. Do you get the same error when using File > Share > Email as attachment using Excel?
7. In Internet Explorer, open the Internet Options. On the General tab within the browsing history, delete your temporary Internet files and website files
8. Does the issue occur in selective startup mode?
Steps to setup selective startup mode:
Click on the Windows Start button, in the Search box type msconfig and then hit enter. This should open up the System Configuration Utility. Make the following adjustments within each tab.
Services Tab:
- Check the option 'Hide All Microsoft Services'
- Click on button 'Disable All'
Startup Tab:
- Click the button 'Disable All'
- Go back through the list and enable any Microsoft items
Click Ok. It will say “You must restart your computer for some of the changes
made by System Configuration to take effect”. Hit the ‘Restart’ button.
When the PC reboots try to run your test again.
To return back to a normal boot launch msconfig again and choose 'normal startup' on the general tab, click Ok and then reboot the PC.
Regards,
Dennis

SQL Server 2012 installation failure An error occurred for a dependency of the feature causing the setup process for the feature to fail.

I am installing SQL Server 2012 Developer (from ISO image written on DVD), my machine has Windows 7 (Edit: Windows 7 with service pack 1) on it. This machine already has SQL Express and SQL 2008 R2 Express installed in it.
On running 2012 setup it goes fine from Setup Support Rules to Installation Progress. In Installation Progress after some progress installation fails.
Windows show the following components couldn't installed:
Managment Tools Complete Failed. Client Tools Connectivity Failed. Client Tools SDK Failed. Client Tools Backwards Compantibility Failed. Managment Tools Basic Failed. SQL Server Data Tools Failed. Reporting Services -Native Failed. Database Engine
Services Failed. Data Quality Services Failed. full-Text and Semantic Extractins for Search Failed. SQL Server Replication Failed. Integration Services Failed. Analysis Services Failed. SQL Client Connectivity SDK Failed.
In detail for failure of every component it provide these details:
Action required:
Use the following information to resolve the error, and then try the setup process again.
Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.
In summary log file it provide the following details:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068643839
Start time: 2012-07-31 16:23:37
End time: 2012-07-31 16:33:32
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for Conn: Use the following information to resolve the error, and then try the setup process again.
Next step for SDK: Use the following information to resolve the error, and then try the setup process again.
Next step for BC: Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for BIDS: Use the following information to resolve the error, and then try the setup process again.
Next step for RS: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for DQ: Use the following information to resolve the error, and then try the setup process again.
Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Next step for IS: Use the following information to resolve the error, and then try the setup process again.
Next step for AS: Use the following information to resolve the error, and then try the setup process again.
Next step for SNAC_SDK: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: Haansi-PC
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
SQL Server 2005 SQLEXPRESS MSSQL.1
Database Engine Services 1033 Express Edition
9.4.5000 No
SQL Server 2005 SQLEXPRESS MSSQL.1
SQL Server Replication 1033 Express Edition
9.4.5000 No
SQL Server 2005 SQLEXPRESS MSSQL.1
SharedTools 1033
Express Edition 9.4.5000 No
SQL Server 2005
Tools 1033
Express Edition 9.4.5000 No
SQL Server 2005
ToolsClient 1033
Express Edition 9.4.5000 No
SQL Server 2005
ToolsClient\Connectivity 1033 Express Edition
9.4.5000 No
SQL Server 2008 R2 SQLSERVER08EXPR2 MSSQL10_50.SQLSERVER08EXPR2 Database Engine Services 1033
Express Edition 10.50.1617.0 No
SQL Server 2008 R2 SQLSERVER08EXPR2 MSSQL10_50.SQLSERVER08EXPR2 SQL Server Replication 1033
Express Edition 10.50.1617.0 No
SQL Server 2008 R2
Management Tools - Basic 1033 Express Edition
10.50.1617.0 No
SQL Server 2012
LocalDB 1033
Express Edition 11.0.2318.0 No
SQL Server 2012
Reporting Services - SharePoint
11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: F:\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$SS2012
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: TABULAR
ASSVCACCOUNT: NT Service\MSOLAP$SS2012
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Manual
ASSYSADMINACCOUNTS: PC\Haansi
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, BIDS, CONN, IS, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SS2012
FTSVCPASSWORD: <empty>
HELP: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SS2012
INSTANCENAME: SS2012
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SS2012
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Manual
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SS2012
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: Haansi-PC\Haansi
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Server Data Tools
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Integration Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Analysis Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\SystemConfigurationCheck_Report.htm

Please help.
I did what you suggested, but, still got error message to install SQL server data tools: Here is the log.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068037632
Start time: 2014-09-29 15:05:38
End time: 2014-09-29 15:15:55
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SSDTBI_VS2012: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: MSBI
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
SQL Server 2008 Management Tools - Basic
1033 Express Edition 10.0.1600.22 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Basic
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Complete
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Connectivity
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Backwards Compatibility
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools SDK
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 SQL Server Data Tools
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Integration Services
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Reporting Services - SharePoint
11.0.2100.60 No Yes
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: C:\9f7a58aa5d6d76ffe6be968a4ad339f5\x86\setup\
Installation edition: Express
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x86
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x86
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SSDTBI_VS2012, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTANCEID: <empty>
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: true
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\ConfigurationFile.ini
Detailed results:
Feature: SQL Server Data Tools - Business Intelligence for Visual Studio 2012
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft Visual Studio Tools for Applications 2012
Component error code: 0x80044000
Component log file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\VSTA2012_LangsSupport_Cpu32_1.log
Error description: VS Shell 2012 installation has failed with exit code -2147205120.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3436.0&EvtType=VSTA2012_LangsSupport%40Install%400x-2147205120
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\SystemConfigurationCheck_Report.htm

Time Capsule WDS trial and error--working now

*{ I }*
I consider myself an expert in using Mac computers and Mac wireless systems although I am no hacker and no programmer by any stretch of the imagination (although I did teach myself how to use HyperStacks way back in 1990!). Although Apple overall provides a relative ease of use for computer technology, setting up a WDS network under b or g mode is still not always perfect. In this post, I relay my experiences of using a new Time Capsule to join an existing WDS network in 802.11g mode. It took several trials and errors and there might still be some glitches but for now it seems to be working.
note: you might want to skip to the last section roman numeral five if you want to skip the "travels with Conal and his Time Capsule" and see what my most helpful hint is.
*{ II }*
WDS stands for Wireless Distribution System which is when you use wireless routers to extend the range of your networks using a wireless method rather than linking each router by long cables. In the ideal situation, you would link the routers by cables but in a home situation one may not be able to have unsightly cables hanging everywhere.
My previous WDS system looked something like this:
DSL Modem == Extreme ~~ Express1 ~~ Express2 ## laptop
Key
== represents wired connection between routers
~~ represents wireless connection between routers
## represents wireless connection to a wireless device that is not a router (eg., laptop)
Extreme = Airport Extreme, the previous generation that looked like a saucer (or humourously I have heard called a "boob-style" station.
Express1 and Express2 = Airport Express, the previous generation that only could broadcast in b or g
My laptop usually connects to the network from Express2 because that has the strongest signal in my room.
*{ III }*
When I received my Time Capsule, I wanted to replace the existing Express2 and make Express2 simply become a wifi client (not a router) so that I can still use it for AirTunes and not to have it broadcast router signals. The reason for this is because Express2 and Time Capsule reside in the same room and aside from the redundancy of network signals, I don't know if having two wireless routers in such close proximity to each other would cause havoc on my network performance. I wanted the network to look like this schematic:
Extreme ~~ Express1 ~~ Time Capsule
I unplugged Express 2 and took it to the same location as Express 1 and Extreme 1. Then I plugged in Time Capsule. The idea of putting them in close proximity for set up was so that they could properly configure each other.
I opened up Airport Utility and it saw all four of my routers. I went through the wizard for Time Capsule selecting the option for it to replace an existing router. When all configurations were automatically set Time Capsule rebooted and in about two minutes or less, Airport Utility tells me there was an error configuring the Time Capsule. I knew immediately then that I had a few long hours ahead of me.
After that first failure I tried these various ways:
1. retried the wizard automatic way (never worked for my setup which albeit is not the simplest of network setups is neither the most complicated)
2. performed a manual configuration whereby I added the Time Capsule Airport ID to Express1 making Time Capsule a remote router of Express1; then I manually added Express1 to TimeCapsule as a router that it should connect to (that didn't work for some reason)
3. finally I got out the ethernet cable, hard reset Time Capsule, plugged in ethernet cable from laptop to TimeCapsule, and the manually added the Airport ID to Express1 and vice versa.
Note that I went through trial #2 several times fiddling around with other various WDS configuration etc. Finally what really worked for me was #3. I find that despite that I should be able to configure a new router wirelessly, I was not able to do so with success. I had to do it in a wired ethernet fashion.
After that was done, all was set. Well, almost because I still had to reconfigure Express2 so that it no longer would work as a router but as a wifi client.
*{ IV }*
Now my whole network looks like this
DSL Modem == Extreme ~~ Express1 ~~ TimeCapsule ## Express2 ## laptop
Note that Express2 and my laptop are actually both connected wirelessly to TimeCapsule. I am unable to draw it in another way due to the limitations of using linear text to represent parallel items.
*{ V }*
So, my advice for those who are having trouble with configuring Time Capsule or other wireless router, sometimes you might want to try plugging in an ethernet cable so that not only is the connection more solid but that pretty much continual contact with the router is available.
I realise that WDS in 802.11n is configured slightly differently and so perhaps WDS setup has improved but as it stands in 802.11g and 802.11b in the way Apple has implemented it, I would not suggest someone below the level of expert doing it. It can be very baffling, confusing, and irritating. I would never ask my father to try to set up WDS on his own even though there is a wizard for it. I know some people (like Chris Prillo) has had no problems with the wizard, but I have always had problems with the wizard. Not only did I have problems with it when trying to get the Time Capsule to replace an existing router, but when I set up my original WDS network I also couldn't use the wizard to set it up. It kept giving me errors.
Message was edited by: Conal Ho
Message was edited by: Conal Ho

You are over complicating things. I have a Time Capsule (TC), AirPort Extreme (AE) Base Station and AirPort Express (AX) all working flawlessly with WDS.
Make sure to write down the MAC addresses of the TC, AE, and AX. You will need them to configure WDS.
Using the AirPort Admin util configure the TC. Turn on WDS and set the TC to be the main.
Using the AirPort Admin software configure the first AX. Turn on the WDS and set it as a remote client of the TC. You will need the MAC address of the TC.
Using the AirPort Admin software configure the second AX. Turn on the WDS and set it as a remote client of the TC. You will need the MAC address of the TC.
You may have to reboot each device after each config change.
See my blog post on this at http://islandinthenet.com/2008/07/01/airport-everywhere-with-wireless-distributi on-system-wds/
Message was edited by: Khurt Williams

Vista problem and error createding users.

Hi All. About 4 weeks back I took on a task to install Leopard server in a small office. 5 macs all running leopard and one dell running Vista home basic.
The server is a brand new Mini with 4 Gigs of Ram and the 320 Gig HD. Storage is on a 2T external box.
Installation was a nightmare. I had to install via Target disk as the Mini was too new to boot from the Leopard DVD (10.5.4) then apply the updates while running the server on the host mac using the mini's HD as the startup drive. It took about 4 goes to get it all up and running.
I set up the users and all's well - except for the dell. It can access the shares and read but cannot write, despite having the same priviledges as the rest of the group. What puzzles me (I know too little about windows and even less about vista) is that while the macs all presented a log-in/password box when they first connected, the dell just went straight to the shares. I cannot find a way of making the dell authenticate. Have I done something wrong or is it Vista home Basic that is the culprit.
Next issue, I cannot get a shared iCal to work (but the wiki calendar works brilliantly) as I keep getting told (this is me the admin) that I don't have permission!
Third issue (and this is worrying me), while testing with the dell I created another user with a new name just to see if it was the original settings that were at fault - but - I couldn't. Everytime I tried to create a new user I get an error message -
"User creation failed. The server reported the error '-14120' while trying to create the user"
It doesn't matter what I do I cannot create another user.
I'd really appreciate some help here.
Finally, (it's not a problem - yet) I have to set it up so that all the users can log in from home to access the shares - and that includes the dell.

Hi David, I'm back again.
The problem I'm having with the new user error may be hidden in this short section from the log:
Also, one of the users (who has been perfectly OK) is now getting a Kerberos log-in error and can no longer write to the shares.
LOG:
Sep 28 13:33:57 MuseMini imap[81400]: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No principal in keytab matches desired name)
Sep 28 13:33:57 MuseMini imap[81400]: badlogin: [172.16.1.36] GSSAPI [SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No principal in keytab matches desired name)]
Sep 28 13:36:06 MuseMini ctl_cyrusdb[81445]: checkpointing cyrus databases
Sep 28 13:36:06 MuseMini ctl_cyrusdb[81445]: done checkpointing cyrus databases
Sep 28 13:36:22 MuseMini servermgrd[61]: servermgr_accounts: got error -14098 trying to log to local LDAP node
Sep 28 13:36:22 MuseMini servermgrd[61]: servermgr_accounts: got error -14120 trying to write config record
Sep 28 13:38:43 MuseMini servermgrd[61]: DirectoryService crash detected, reauthorizing node
Sep 28 13:38:43 MuseMini servermgrd[61]: servermgr_accounts: got error -14098 trying to log to local LDAP node
Sep 28 13:38:43 MuseMini servermgrd[61]: DirectoryService crash detected, reauthorizing node
Sep 28 13:38:43 MuseMini servermgrd[61]: servermgr_accounts: got error -14098 trying to log to local LDAP node
Sep 28 13:38:43 MuseMini servermgrd[61]: DirectoryService crash detected, reauthorizing node
Sep 28 13:38:43 MuseMini servermgrd[61]: servermgr_accounts: got error -14098 trying to log to local LDAP node
Sep 28 13:38:43 MuseMini servermgrd[61]: DirectoryService crash detected, reauthorizing node
Sep 28 13:38:43 MuseMini servermgrd[61]: servermgr_accounts: got error -14098 trying to log to local LDAP node
Sep 28 13:38:43 MuseMini servermgrd[61]: DirectoryService crash detected, reauthorizing node
Sep 28 13:38:43 MuseMini Server Preferences[80311]: XSAdminQueueController: gotServerError: -14120 forTransaction: <XSAdminTransaction: 0x1711f980>
Sep 28 13:38:43 MuseMini servermgrd[61]: servermgr_accounts: got error -14098 trying to log to local LDAP node
Sep 28 13:38:43 MuseMini Server Preferences[80311]: Error creating user: {\n command = createUser;\n error = "-14120";\n}
Sep 28 13:38:57 MuseMini imap[81506]: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No principal in keytab matches desired name)
Sep 28 13:38:57 MuseMini imap[81506]: badlogin: [172.16.1.36] GSSAPI [SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No principal in keytab matches desired name)]
Sep 28 13:38:57 MuseMini imap[81509]: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No principal in keytab matches desired name)
Sep 28 13:38:57 MuseMini imap[81509]: badlogin: [172.16.1.36] GSSAPI [SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No principal in keytab matches desired
It looks to me as though I may have to go through the entire install again - and I really don't want to do that.
Help!

New LUN Takes A long Time To Format and Errors Out

Good afternoon,<o:p></o:p>
I have a Hyper-V Cluster composed of 4 nodes and these nodes are able to access multiple CSVs (14 in total). I recently requested a new LUN (LUN 15)to be provisioned
to my Hyper-V cluster in the size of 500GB. Here is my problem:<o:p></o:p>
1. Formatting of a 500GB LUN (with quick format selected) should not take more than a few seconds. Instead, the quick format takes about 2hrs if not longer. I have actually
seen it go for half the day.<o:p></o:p>
2. Once the formatting has completed (no errors), taking the formatted LUN offline freezes the Computer Management screen and shows the status (Not Responding). This
will take place for 30 minutes or less and show that the LUN has been taken offline.<o:p></o:p>
3. In the Failover Cluster Manager, detecting the disks takes about 15 minutes. Once the available LUNs have been detected I can add the 500GB LUN to the Disks screen
without any problems.<o:p></o:p>
4. While in the Disks screen, adding the LUN to the Clustered Shared Volumes takes about 5 minutes (too long).<o:p></o:p>
Already seeing that there is a problem, I went ahead and used the Hyper-V Manager to create a 200GB vhd on the new LUN which has been added to the CSV. The bar indicating
the progress of the vhd creation does not display any progress (no green progress bar appears, not even a tiny bit of it) and after 3 hours (more or less) I receive an error, stating that the creation of the vhd failed.
<o:p>NOTE: The vhd shows up in Volume 9 (LUN 15) but I can only bet that it will not work, plus I would not want to work with a vhd file which failed during the
creation process.</o:p>
<o:p>Long story short, I repeated the above steps to see if that was a temporary problem, but it is not. The same problem occurs no matter which Hyper-V cluster
node the operations are performed on. I would like to add, that I tested the creation of a vhd on an already configured LUN and the creation was completed successfully, and within a n expected time frame.</o:p>
NOTE: When LUN 15 errors out, it's status shows "Failed" in the Failover Cluster Manager. This in turn, causes the re-scanning of available disks to take forever (in Computer Management) and it keeps searching. Pretty
much, the fail of one LUN affects the entire functionality of the entire Hyper-V Cluster.
Errors Listed In Event Details For LUN 15:
1. Cluster Shared Volume 'Volume9' ('Cluster Disk 5') is no longer accessible from this cluster node because of error 'ERROR_TIMEOUT(1460)'. Please troubleshoot this node's connectivity to the storage device and
network connectivity.
Event ID: 5142; Source: Microsoft-Windows Failover Clustering;Task Category: Cluster Shared Volume
2. Cluster Shared Volume 'Volume9' ('Cluster Disk 5') is no longer available on this node because of 'STATUS_IO_TIMEOUT(c00000b5)'. All I/O will temporarily be queued until a path to the volume is reestablished.
Event ID: 5120; Source: Microsoft-Windows Failover Clustering;Task Category: Cluster Shared Volume
3.Cluster resource 'Cluster Disk 5' of type 'Physical Disk' in clustered role '4530acc9-8552-4696-b6c3-636ff8d58c46' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover
Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Event ID: 1069; Source: Microsoft-Windows Failover Clustering;Task Category: Resource Control Manager
4.
Cluster resource 'Cluster Disk 5' (resource type 'Physical Disk', DLL 'clusres.dll') did not respond to a request in a timely fashion. Cluster health detection will attempt to automatically recover by terminating the Resource Hosting Subsystem (RHS)
process running this resource. This may affect other resources hosted in the same RHS process. The resources will then be restarted.
The suspect resource 'Cluster Disk 5' will be marked to run in an isolated RHS process to avoid impacting multiple resources in the event that this resource failure occurs again. Please ensure services, applications, or underlying infrastructure
(such as storage or networking) associated with the suspect resource is functioning properly.
Event ID: 1230; Source: Microsoft-Windows FailoverClustering;Task Category: Resource Control Manager
Any and all help will be appreciated!

Hi AquilaXXIII,
What server edition you are using? If you are using 2012r2 as cluster node, please install Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
update first,
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
http://social.technet.microsoft.com/Forums/en-US/f9c1a5f7-4fcf-409a-8d7e-388b85512bfe/new-lun-takes-a-long-time-to-format-and-errors-out?forum=winserv
Before you install the new shared storage please first validation this storage first, you can refer the following KB to validation the new LUN.
Understanding Cluster Validation Tests: Storage
http://technet.microsoft.com/en-us/library/cc771259.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

(com.apple.collabd[15483]): Service setup event to handle failure and will not launch until it fires.

Hello,
I am fairly new at Xserve administration, but I got thrown in the fire and i need your help.
My system.log is being hammered with this error:
(com.apple.collabd[15483]): Service setup event to handle failure and will not launch until it fires.
I did my research and it seems to be related to Wiki, but I disabled wiki and restarted and it is still coming up. Any advice would really help
System Version: OS X 10.10.1 (build 14B25)
Server Version: Server 4.0.3 (Build 14S350)

Try deleting the preferences file

Verification Failure and potential counterfeit software

I recently purchased a student license and DVD Adobe Creative Suite 6 Design Standard for Windows from www.srs.usg.edu, the supplier of software for my university. After partially downloading, the installer said there was a verification failure and that "the product you are trying to install is not an Adobe Genuine Software and appears to be counterfeit.
The only issue I can think of is that I downloaded a free trial of Photoshop CS6 that is still on my computer. I didn't uninstall it before trying to install my purchase because if it didn't work, I didn't want to be left without a program to finish my homework on. If this is the solution, I can try that, but I would think I would've gotten a different notification if that were the error.
Is there a solution? Thank you

The Genuine Software Failure error could be due to damaged installation media. Please try downloading the trial of Creative Suite 6 Design Standard from http://www.adobe.com/cfusion/tdrc/index.cfm?product=design_standard. You can then try the installation again with the freshly downloaded install files.

FREQUENT FAILURES AND ERRORS:PLZ

Similar Messages

Maybe you are looking for