SMB issues on 10.10.1 server 4
I am running file sharing on 10.10.1 with server version 4.
AFP continuously works but SMB will seem to stop functioning every few weeks. This will result in "There was a problem connecting to the server ...." when a user attempts to connect.
I've used serveradmin to restart the SMB service, but users are still unable to connect.
Restarting the server corrects the issue for a couple of weeks.
I'm curious if anyone has ran into similar issues and if they've come across a solution.
Thanks.
You might try the OS X Server forum.
Similar Messages
-
Hey everyone,
Hopefully I can get some help or at least someone else can recognize the issue at hand. We recently upgrade our Mac Mini Server to 10.9.2 and are having major SMB issues. It's hard to specifically tell but it seems like when we hit a magic number around 150~200 users the server shuts down all filesharing. When I look at Activity Monitor, SMBD is around 99% CPU usage. The only remedy is to restart the server.
Any help would be greatly appriciated. Thank you!There have been some other posts suggesting that Apple might have messed up some default TCP configuration parameters in 10.5.2. It might be instructive to compare the result of:
sysctl -a | grep tcp
on otherwise similar 10.5.1 and 10.5.2 systems. -
Monday all of our OS X Lion Macs can access SMB file shares on our file server and we come in Tuesday morning and now they take at least 1 minute to pull up the file share and sometimes longer. Windows PC's are immediate when connecting to the same shares. I've seen where others with different versions of OS Xhave this issue but what gets me is it happend all at once to machines that were working perfectly the day before.
I've also looked into changes on our servers and as far as I can tell there have been none.
Does anyone have any ideas? Thanks....This solution worked for me!
I had a MobileMe account with iDisk configured on my MBP even though I never actually used it. The night they officially shutdown MobileMe the next morning I could no longer connect to my work's SMB file shares (Windows server shares). I found a work around based on some other support threads. If in the "Connect to Server" address field in Finder I specified my crendentials (i.e. smb://username:password@server/) then it worked perfectly fine. This told me it was a crendential issue. Simply deleting the saved server crendentials in KeyChain Access did not resolve the issue. No matter what I would did it would not prompt for login crendentials. Since my Mac login is different than my work domain login I was dead in the water without manually specifiying (not a permenant solution).
After finding this thread I did the following steps and it resolved the issue 100%.
1. Open Terminal
2. cd ~/Library/Preferences
3. ls .GlobalPreferences.plist to verify file exists in that directory
4. rm .GlobalPreferences.plist to delete file
5. ls .GlobalPreferences.plist to verify file no longer exists
4. Go to Force quit to relaunch Finder
5. Lauch "Connect to Server" within Finder and all was good, server connects perfectly
Thank you very much DavidRSewell!!!! -
Issues with Mac OS X Server 10.4.8 and Windows File sharing
We are having lots of issues with our SMB share on Mac OS X Server 10.4.8. The main issues are the following:
- Group ACLs seem to not work properly, and I have had to add dozens of manual permissions on a per-user basis
- Often, users open a file in read-only mode, without any reason, and can't modify it
- Often, users open a file with full write access, but then cannot save it and have to use a "save as function".
After having looked all over the Internet and on the Apple's discussions forum, it seems like this issue has been around for quite some time now:
http://discussions.apple.com/search.jspa?forumID=702&threadID=&q=smbANDpermissions&objID=f702&dateRange=thisyear&userID=&numResults=15&rankBy=10001
http://discussions.apple.com/thread.jspa?messageID=1546867�
http://discussions.apple.com/thread.jspa?messageID=647251
And no real answer/solution has been provided by Apple yet.
I also looked on Samba related pages, and it seems like these issues were Samba related (both ACL/OpenLDAP and Microsoft Office file handling issues), and the current version of Samba (3.0.23c) seem to have solved lots of issues in these areas:
http://us1.samba.org/samba/history/samba-3.0.23c.html
Apple ships Samba 3.0.10 (16 Dec 2004) with 10.4.8, which makes the shipping version at list 15 versions (and 18 months) behind the current Samba release (30 Aug 2006).
People within the company are obviously quite unhappy with the situation and beyond me looking like a fool for migrating from Windows Server to OS X, I now need to find a solution to the issues.
I would like to know what is the official and Apple recommended way to solve this issue.
Kind regards,
Pejvan
It seems like Apple is totally ignoring the issues, users are facing with SMB shares, while their emphasize as a selling point how OS X Server is a great "windows file" server.Hiya
Thanks for the reply.
>Is there a UPS involved?
I wish there had been. I might not be having to deal with it now! :-)
>If you boot from the Install Disc & use System Profiler there, does the Same RAM situation? Did you physically >check those slots? Thinking maybe the OS is kicking them out on bootup?
I've had the following suggested to me on another forum - "My guess on the RAM error is this. You have a processor that wants the RAM to be dual channeled and since it reads both A slot are populated it wants both B slots to be populated. Remove A2 and put it in B1"
But unless it is degrading performance I'll probably just leave it.
> Still can't get it to boot from the Clone holding the Option/alt key at bootup?
I can get it to boot from the Clone using the option key but it's a pretty random event. I can try for ages and then suddenly it'll work. Or it may work first time. It does seems to work more easily after a PRAM zap. The funny thing is that once it is booted up it will re-start in any way I want it to (the boot volume, the clone, a disk, single user mode etc). It is just hard to boot from a full shutdown.
I'm thinking that if I ca get the start-up issue fixed then I can fix the RAID issue at my leisure and even add the hard-drive that the clone is currently on to the RAID array.
Thanks again. -
JMS/JTA issue is case of a server crash
Hi All
I am having some JMS/JTA related issue in case of a server crash. This is there
for both 6.1 and 7.0. Its like this - an MDB is getting data from a Queue and
its CMT [ie JTA]. Now when the MDB has the onMessage call back that time a usertransaction
has been opened by the JMS framework of WLS 7.0/6.1. Now when the onMessage block
is executing if the server crashes - before the TX has been rolled back/commited
then next time when that server is restarted that message does mot appear on the
Queue for 4-5 minutes and the Queue shows the message in "Bytes Pending". So the
user has to wait for 4-5 minutes before getting back the message. In this time
period whatever u try - like use QueueBrowser /QueueReceiver to find the message
shows no result. This is something to do with JTA/JMS combination.
Is there anyway to control this "invisible time" of the message? This is causing
a lot of problem in our user base.
thanks
Anamitra
I don't think there are any issues. You might get more info from the
transaction newsgroup and/or customer support.
Tom
Anamitra wrote:
> Hi Tom
> thats good - but this brings another question. If that was to be reduced are there
> any side effects that I should be aware of?
> thanks
> Anamitra
>
> Tom Barnes <[email protected]> wrote:
>
>>This is a FAQ, but is not in the FAQ.
>>
>>1) As an enhancement, the transaction recovery delay has been reduced,
>>
>>or even eliminated in 8.1.
>>
>>2) There are plans to back-port this reduction to 7.0 - I think the
>>back-port is already available. Contact customer support.
>>
>>3) Meanwhile, there is somewhat of a work-around. You can reduce the
>>
>>recovery delay to as little as 60 seconds by setting
>> RecoveryThresholdMillis="60000"
>>in the "JTA" section of your config.xml, programmatically via JMX on
>>the
>>"JTAMBean".
>>
>>Tom
>>
>>Anamitra wrote:
>>
>>>Hi All
>>>I am having some JMS/JTA related issue in case of a server crash. This
>>
>>is there
>>
>>>for both 6.1 and 7.0. Its like this - an MDB is getting data from a
>>
>>Queue and
>>
>>>its CMT [ie JTA]. Now when the MDB has the onMessage call back that
>>
>>time a usertransaction
>>
>>>has been opened by the JMS framework of WLS 7.0/6.1. Now when the onMessage
>>
>>block
>>
>>>is executing if the server crashes - before the TX has been rolled
>>
>>back/commited
>>
>>>then next time when that server is restarted that message does mot
>>
>>appear on the
>>
>>>Queue for 4-5 minutes and the Queue shows the message in "Bytes Pending".
>>
>>So the
>>
>>>user has to wait for 4-5 minutes before getting back the message. In
>>
>>this time
>>
>>>period whatever u try - like use QueueBrowser /QueueReceiver to find
>>
>>the message
>>
>>>shows no result. This is something to do with JTA/JMS combination.
>>
>>>Is there anyway to control this "invisible time" of the message? This
>>
>>is causing
>>
>>>a lot of problem in our user base.
>>>
>>>thanks
>>>Anamitra
>>
>
-
On a server 2012R2 Essentials when trying to install the essentials experience the first install works ok but the configuration allways stops with the message "Certificate Issuer is installed on this server" and no way to continue the configuration.
Windows/Logs/CBS/
2014-07-24 21:10:04, Info CBS TI: --- Initializing Trusted Installer ---
2014-07-24 21:10:04, Info CBS TI: Last boot time: 2014-07-24 18:36:03.489
2014-07-24 21:10:04, Info CBS Starting TrustedInstaller initialization.
2014-07-24 21:10:04, Info CBS Ending TrustedInstaller initialization.
2014-07-24 21:10:04, Info CBS Starting the TrustedInstaller main loop.
2014-07-24 21:10:04, Info CBS TrustedInstaller service starts successfully.
2014-07-24 21:10:04, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
2014-07-24 21:10:04, Info CBS Startup processing thread terminated normally
2014-07-24 21:10:04, Info CBS Starting TiWorker initialization.
2014-07-24 21:10:04, Info CBS Ending TiWorker initialization.
2014-07-24 21:10:04, Info CBS Starting the TiWorker main loop.
2014-07-24 21:10:04, Info CBS TiWorker starts successfully.
2014-07-24 21:10:04, Info CBS Universal Time is: 2014-07-24 19:10:04.379
2014-07-24 21:10:04, Info CBS Loaded Servicing Stack v6.3.9600.17200 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17200_none_fa7026dd9b04586e\cbscore.dll
2014-07-24 21:10:04, Info CSI 00000001@2014/7/24:19:10:04.379 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffd2cb360e5 @0x7ffd2de92e53 @0x7ffd2de924ac @0x7ff60b37d2df @0x7ff60b37d9e4
@0x7ffd588d2385)
2014-07-24 21:10:04, Info CBS Could not load SrClient DLL from path: SrClient.dll. Continuing without system restore points.
2014-07-24 21:10:04, Info CBS SQM: Initializing online with Windows opt-in: True
2014-07-24 21:10:04, Info CBS SQM: Cleaning up report files older than 10 days.
2014-07-24 21:10:04, Info CBS SQM: Requesting upload of all unsent reports.
2014-07-24 21:10:04, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2
2014-07-24 21:10:04, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2014-07-24 21:10:04, Info CBS NonStart: Set pending store consistency check.
2014-07-24 21:10:04, Info CBS Session: 30386034_3758808251 initialized by client WinMgmt.
2014-07-24 21:10:04, Info CBS Enumerating Foundation package: Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~6.3.9600.16384, this could be slow
2014-07-24 21:10:05, Info CSI 00000002 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x172dbed940
2014-07-24 21:10:05, Info CSI 00000003 Creating NT transaction (seq 1), objectname [6]"(null)"
2014-07-24 21:10:05, Info CSI 00000004 Created NT transaction (seq 1) result 0x00000000, handle @0x25c
2014-07-24 21:10:08, Info CSI 00000005 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
2014-07-24 21:10:08, Info CSI 00000006@2014/7/24:19:10:08.151 Beginning NT transaction commit...
2014-07-24 21:10:08, Info CSI 00000007@2014/7/24:19:10:08.182 CSI perf trace:
CSIPERF:TXCOMMIT;32854
2014-07-24 21:10:08, Info CSI 00000008 CSI Store 99552754976 (0x000000172dce7d20) initialized
2014-07-24 21:10:08, Info CSI 00000009@2014/7/24:19:10:08.182 CSI Transaction @0x172e9bcaa0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002
and client id [26]"TI5.30386034_3758808251:1/"
2014-07-24 21:10:08, Info CSI 0000000a@2014/7/24:19:10:08.182 CSI Transaction @0x172e9bcaa0 destroyed
2014-07-24 21:10:19, Info CBS Session: 30386012_3156824848 initialized by client DISM Package Manager Provider.
2014-07-24 21:12:19, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2014-07-24 21:12:19, Info CBS TiWorker signaled for shutdown, going to exit.
2014-07-24 21:12:19, Info CBS Ending the TiWorker main loop.
2014-07-24 21:12:19, Info CBS Starting TiWorker finalization.
2014-07-24 21:12:19, Info CBS Ending the TrustedInstaller main loop.
2014-07-24 21:12:19, Info CBS Starting TrustedInstaller finalization.
2014-07-24 21:12:19, Info CBS Ending TrustedInstaller finalization.
2014-07-24 21:12:20, Info CBS Ending TiWorker finalization.
Any ideas?
//ChristerHi Justin!
nltest /server:"servername" /sc_reset:"domaninname" returns: "I_NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN"
Dcdiag /q returns : An error occurred. EventID: 0xC0001B77
The text log was not small enough to post here..
Regards.
Christer
Can not find anything directly related in windows-logs but here is the latest log from CBS folder..
2014-07-28 11:04:25, Info CSI 00000888 [DIRSD OWNER WARNING] Directory [ml:520{260},l:118{59}]"\??\C:\Windows\Inf\Windows Workflow Foundation 3.0.0.0\041D" is not owned but specifies
SDDL in component Microsoft-Windows-WWFCoreComp.Resources, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"sv-se", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2014-07-28 11:04:25, Info CSI 00000889 [DIRSD OWNER WARNING] Directory [ml:128{64},l:126{63}]"\??\C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\MsDtc\en" is not owned but specifies
SDDL in component Microsoft.Dtc.PowerShell.Non_msil.Resources, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2014-07-28 11:04:28, Info CSI 0000088a [DIRSD OWNER WARNING] Directory [ml:134{67},l:132{66}]"\??\C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\MsDtc\en-US" is not owned but specifies
SDDL in component Microsoft.Dtc.PowerShell.Scripts.Resources, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2014-07-28 11:04:28, Info CSI 0000088b [DIRSD OWNER WARNING] Directory [ml:520{260},l:134{67}]"\??\C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework" is not owned but specifies
SDDL in component Microsoft-Windows-WWFCoreComp, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2014-07-28 11:04:28, Info CSI 0000088c [DIRSD OWNER WARNING] Directory [ml:520{260},l:118{59}]"\??\C:\Windows\Inf\Windows Workflow Foundation 3.0.0.0\0000" is not owned but specifies
SDDL in component Microsoft-Windows-WWFCoreComp, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2014-07-28 11:04:28, Info CSI 0000088d [DIRSD OWNER WARNING] Directory [ml:520{260},l:114{57}]"\??\C:\Program Files (x86)\Reference Assemblies\Microsoft" is not owned but specifies SDDL
in component Microsoft-Windows-WWFCoreComp, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2014-07-28 11:04:28, Info CSI 0000088e [DIRSD OWNER WARNING] Directory [ml:520{260},l:144{72}]"\??\C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0" is not owned
but specifies SDDL in component Microsoft-Windows-WWFCoreComp, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2014-07-28 11:04:28, Info CSI 0000088f [DIRSD OWNER WARNING] Directory [ml:520{260},l:94{47}]"\??\C:\Program Files (x86)\Reference Assemblies" is not owned but specifies SDDL in component
Microsoft-Windows-WWFCoreComp, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2014-07-28 11:04:30, Info CSI 00000890 Ignoring duplicate ownership for directory [l:72{36}]"\??\C:\Windows\microsoft.net\authman" in component Microsoft.Interop.Security.AzRoles, Version
= 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2014-07-28 11:04:31, Info CSI 00000891 [SR] Verify complete
2014-07-28 11:04:31, Info CSI 00000892 [SR] Verifying 100 (0x0000000000000064) components
2014-07-28 11:04:31, Info CSI 00000893 [SR] Beginning Verify and Repair transaction
2014-07-28 11:04:36, Info CSI 00000894 [SR] Verify complete
2014-07-28 11:04:36, Info CSI 00000895 [SR] Verifying 100 (0x0000000000000064) components
2014-07-28 11:04:36, Info CSI 00000896 [SR] Beginning Verify and Repair transaction
2014-07-28 11:04:40, Info CSI 00000897 [DIRSD OWNER WARNING] Directory [ml:520{260},l:120{60}]"\??\C:\Windows\Microsoft.NET\Framework\v2.0.50727\RedistList" is not owned but specifies
SDDL in component NetFx-ASSEMBLYLIST_XML, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral
2014-07-28 11:04:42, Info CSI 00000898 [SR] Verify complete
2014-07-28 11:04:42, Info CSI 00000899 [SR] Verifying 100 (0x0000000000000064) components
2014-07-28 11:04:42, Info CSI 0000089a [SR] Beginning Verify and Repair transaction
2014-07-28 11:04:46, Info CSI 0000089b [SR] Verify complete
2014-07-28 11:04:46, Info CSI 0000089c [SR] Verifying 100 (0x0000000000000064) components
2014-07-28 11:04:46, Info CSI 0000089d [SR] Beginning Verify and Repair transaction
2014-07-28 11:04:52, Info CSI 0000089e [SR] Verify complete
2014-07-28 11:04:52, Info CSI 0000089f [SR] Verifying 100 (0x0000000000000064) components
2014-07-28 11:04:52, Info CSI 000008a0 [SR] Beginning Verify and Repair transaction
2014-07-28 11:04:58, Info CSI 000008a1 [SR] Verify complete
2014-07-28 11:04:58, Info CSI 000008a2 [SR] Verifying 100 (0x0000000000000064) components
2014-07-28 11:04:58, Info CSI 000008a3 [SR] Beginning Verify and Repair transaction
2014-07-28 11:05:02, Info CSI 000008a4 [SR] Verify complete
2014-07-28 11:05:02, Info CSI 000008a5 [SR] Verifying 100 (0x0000000000000064) components
2014-07-28 11:05:02, Info CSI 000008a6 [SR] Beginning Verify and Repair transaction
2014-07-28 11:05:08, Info CSI 000008a7 [SR] Verify complete
2014-07-28 11:05:08, Info CSI 000008a8 [SR] Verifying 52 (0x0000000000000034) components
2014-07-28 11:05:08, Info CSI 000008a9 [SR] Beginning Verify and Repair transaction
2014-07-28 11:05:09, Info CSI 000008aa [DIRSD OWNER WARNING] Directory [ml:520{260},l:56{28}]"\??\C:\Windows\system\Speech" is not owned but specifies SDDL in component Windows-Media-SpeechSynthesis-WinRT,
pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2014-07-28 11:05:09, Info CSI 000008ab Ignoring duplicate ownership for directory [l:56{28}]"\??\C:\Windows\system\Speech" in component Windows-Media-SpeechSynthesis-WinRT, Version =
6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2014-07-28 11:05:09, Info CSI 000008ac [SR] Verify complete
2014-07-28 11:05:09, Info CSI 000008ad [SR] Repairing 1 components
2014-07-28 11:05:09, Info CSI 000008ae [SR] Beginning Verify and Repair transaction
2014-07-28 11:05:09, Info CSI 000008af Hashes for file member \??\C:\Program Files\Windows Server\Bin\WebApps\RemoteAccess\Web.config do not match actual file [l:20{10}]"Web.config"
Found: {l:32 b:jiP+IRWGZxsG0nX6il5MCZofFThiSfytb8Ih27r5EPk=} Expected: {l:32 b:KR7DbPqdCKMwdiZI2XDSr42o4ujtpZlzfX9ud+ODKRM=}
2014-07-28 11:05:09, Info CSI 000008b0 [SR] Repairing corrupted file [ml:520{260},l:120{60}]"\??\C:\Program Files\Windows Server\Bin\WebApps\RemoteAccess"\[l:20{10}]"Web.config" from
store
2014-07-28 11:05:09, Info CSI 000008b1 [SR] Repair complete
2014-07-28 11:05:09, Info CSI 000008b2 [SR] Committing transaction
2014-07-28 11:05:09, Info CSI 000008b3 Creating NT transaction (seq 2), objectname [6]"(null)"
2014-07-28 11:05:09, Info CSI 000008b4 Created NT transaction (seq 2) result 0x00000000, handle @0xba4
2014-07-28 11:05:11, Info CSI 000008b5@2014/7/28:09:05:11.308 Beginning NT transaction commit...
2014-07-28 11:05:11, Info CSI 000008b6@2014/7/28:09:05:11.470 CSI perf trace:
CSIPERF:TXCOMMIT;163479
2014-07-28 11:05:11, Info CSI 000008b7 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2014-07-28 11:07:13, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2014-07-28 11:07:13, Info CBS TiWorker signaled for shutdown, going to exit.
2014-07-28 11:07:13, Info CBS Ending the TiWorker main loop.
2014-07-28 11:07:13, Info CBS Starting TiWorker finalization.
2014-07-28 11:07:13, Info CBS Ending the TrustedInstaller main loop.
2014-07-28 11:07:13, Info CBS Starting TrustedInstaller finalization.
2014-07-28 11:07:13, Info CBS Ending TrustedInstaller finalization.
2014-07-28 11:07:13, Info CBS Ending TiWorker finalization.
Regards. Christer -
Is there an issue with the software update server? My iphone has been trying to update to the new iOS for almost two hours
Hello brownie67,
Thanks for using Apple Support Communities.
If you're currently unable to update your iOS device Over The Air, then please update it using iTunes.
Update your iPhone, iPad, or iPod touch iOS software
Take care,
Alex H. -
FOUND SOLUTION TO EMAIL ISSUE - "message not downloaded from server"
It took me 4 days to figure it out but there is a solution to the problem "the messsage has not been downloaded from server" and "the message has no content".
I do not have to set up "push" accounts from yahoo or gmail and it works with my corporate email.
Apple can reach me at <Message was edited by: Host> to discuss this issue.I'm not a computer technician, and if you were to give me a few days looking at the problem, i'm sure I or anyone else could provide a solution. I'm not too bothered about the message appearing 50% of the time as i'm usually within easy reach of a Laptop or PC or can find another method to get access to my email.
So i'm not pi**ed off that you have found a solution. I'm just trying to obtain information for a post that says "FOUND SOLUTION TO EMAIL ISSUE - "message not downloaded from server" in the Apple HELP FORUMS... -
10.8.1 Server and windows smb issues
Ever since upgrading to 10.8.1 server my windows clients now have issues copying to the share point on the server. "Network error, there is a problem accessing \\SERVER\WORK"
It's only with large file transfers 3GB and above. It also randomly shows the same warning when they are saving projects to the server occasionally and they have to manully reconnect.
Latest windows 7 64bit pro on all clients and latest mac os X on server.
The share point is an attached thunderbolt raid and has all permissions switched off, and is configured to RAID 0. This is backed up hourly by another drive.
Is there anyway of rolling back to lion? I no longer have a lion back up on my time machine.
Anyone else having these issues?Apple's SMB implentation is weak and buggy. I feel like I'm back in 10.3 trying to talk to Windows servers. Those were horrible days.
To Fix.. go to your Mac and check to make sure that it has the correct WINS settings (network, advanced, WINS). Your server has to be on the same workgroup (domain) as your windows clients. For some reason, the setting does not stick on your Mac and that setting gets lost. And that is the bug...
To fix this (second part of your fix).. go ahead and turn off file sharing. Then add your settings under WINS as stated above, then turn sharing back on and your networking from windows to mac will start to work fine.
Fun bugs... please call Apple about this, so they can follow up. My case number is 357016704 -
Older Clients cannot Authenticated to 10.10 Server ( Also SMB issues)
Hello
I am having a few issues with Server.app ( running on 10.10.2)
It appears older clients ( tested but 10.6 and 10.7) cannot log into the servers open directory. They can bind to it but cannot log in. If i log in with a local account they can still access file sharing etc.
10.10 clients are fine no issues whatsoever with logging in. ( i have not had a chance to test 10.9 and i don't have any 10.8 clients )
I am guessing its something to do with the way older OSs authenticate with the OD but i am not sure, don't have a huge amount of experience with OD outside of general admin.
My second issue is with SMB.
I am using SMB for file shares, everything was working well and then i started to have issues where users get a message saying the fire cannot be read or written error 36.
The file however would copy over no issue at all.
if i connect via cifs:// rather than smb:// it works ( this uses the older version of SMB ) but in an ideal world i would prefer if i did not have to use this as i would have to run a script on every client to force it to use cifs://
AFP works fine however i cannot use AFP for 2 reasons.
MS office for mac does not agree with it , accessing files over afp with this application causes files to be corrupted and become locked for editing. Apparently you need to have a globally writable folder called .TemporyItems in the root of the share for MS office to work correctly ( good design there microsoft) but this does not appear to work.
AFP does also not appear to make file inherit the permissions when you copy something into the directory so its no good for a shared folder .
Is there any way to force yosemite server to use SMB1 so i don't have to edit every single clients settings?
I would also be happy to use AFP if the 2 issues above can be solved.
This is so strange our old 10.6 server works just fine with MS office over AFP.my 10.6 clients log in to new accounts with home folders on a new Yosemite server but take about 4 minutes...
-
SMB issue 10.4 client and 10.5 server solved?
I searched for days to solve the problem to connect via SMB from a 10.4 client on shared files on 10.5 server. But I did not find any answer except unable guest access (what is no real solution).
Why this error code -36 appears when trying to connect from the client (because encrypted password IS enabled)?
Why SMB still works using 10.5 clients and Windows PC's?
Why SMB works when guest access is unabled, but connected with defined accounts?
Does anybody can answer this questions?
Best regards,
Tom
Settings:
10.5.3 Server version
virtual LAN environment
mixed network (Mac, Windows)I had a similar issue and I was able to make things a bit better by letting all users have access to SMB under the server access settings. You can still limit who has access to each individual share. I still have some other odd issues but I can at least connect.
-
Office document sharing failure on server 2003 (SMB issue?)
We have a major issue running Office 2003 and 2010 on Windows server 2003 in a corporate AD environment. Since upgrading workstations from XP to Windows 7 we find that many users loose locking of Excel and Word files between 20 minutes and 6 hours
after opening. This allows a second user to open the file, save it, then the original user saves and the first users changes are lost.
We have tried everything we can think of, removing AV software from severe and client, patching completely, wiping serve rand building from scratch, etc. We have run out of ideas from Microsoft tech support, cannot get any joy from our account manager,
and are out of ideas. Office 2013 also seems to have the same problem from our testing.
The issue is active for files from Excel and Word, and does not matter whether it is a file format in the legacy 2003 format or the newer 2010 format.
FYI - This cannot be replaicted using Widnows XP on the same network / server / document - It is specific to WIndows 7 !
Has anyone had this problem and can anyone help?
...Jon.
...Jon.Hi Jon,
When opening an Office file, a temp file will be created in the same folder. A second open session will check if any related temp file is already exists and if it does, Office will prompt that the file is "in use".
Thus please first check if a temp file will be created (it is a hidden file) when opening an Office file - have a try with creating a new shared folder with Everyone - Full Control for the test and if this will work, check permission settings of the original
shared folder.
If you have any feedback on our support, please send to [email protected] -
Mac pro xserve 10.6.8 AD and SMB issue
Hi,
I have configured Mac OS XServe 10.6.8. This Server is joined with Windows 2008 AD Server.
I have done coming below:
1. Server Admin.app
2. File Sharing -> careated new share folder "test". This folder is located this path "/Volumes/Macintos HD/test"
3. Under Permisstion tab i have clicked + button, then i got new tab "Users & Groups". Their i can see all my windows AD users.
4. I have selacted my user name and two more users full access.
5. Then i have enabled AFP and SMB protocols.
6. Then i have saved the configrstion.
7. Then i went my mac book pro laptop i tryied connect to server afp://192.168.1.5/test
8. I can access the share Folder.
9. Then i have tried smb://192.168.1.5/test
10. User Name and Password not autendicating.
can some please help me how to resolve this issue.
ThanksBefore upgrading to Lion, I would recommend playing with OpLocks on the SMB share. Oplocks will not allow access to a folder if it is use by another share. Try turning these off and on and making sure that nobody is connected to the share by either protocol.
Worth a shot. -
Mac G5 10.3.9 Samba Issue with Windows 2000 Advanced Server??
I have just installed a new Windows 2000 Advanced Server network but the Mac G5s running OS X 10.3.9 Panther cannot navigate the server - the finder just hangs with a beachball. The PCs can navigate without any problems.
Navigation is fine on the G4 running OS X 10.2.8 Jaguar on the same network.
On the G5 I have tried creating a new user and put the Mac using DHCP but this doesn't solve the problem.
I think I have tracked down the problem to Samba but am not sure - When I type in the direct samba link to the server:-
smb://10.10.0.5
The "SMB Mount" screen asks me which share I would like to mount. This works without a problem. I create a shortcut to the share. This also works until I reboot, then the problem reoccurs!
I think I need to reinstall Samba, or update the Samba software?
Does anyone have any thoughts,
John
G5 Mac OS X (10.3.9)HELP FROM A GUY WHO IS NOT A SYS ADMIN OR ON AN I.T. STAFF!
And with that dislcaimer...
What sort of settings do you have checked in your Directory Access > Services panel? That is, do you have SMB turned on?
Also, I would make sure that your server and computer's clocks are showing the exact same times-- just in case there is a synchronization issue.
Our Macs have had similar, but not identical, problems in the past. -
OBIEE 11g SSL Configuration Issue : Unable to import the Server certs
Hello All,
We are trying to configure OBIEE 11.1.1.6.0 with SSL using Windows server 2003 (IIS) and facing some issues with that.
Followed the document : OBIEE11g SSL Setup and Configuration [1326781.1]
http://obieedue.blogspot.sg/2012/08/obiee11g-ssl-setup-and-configuration.html
and also completed generating the required certificate signing request and keystores for SSL communication and sent it to the CA (IT Admin team) to to have the certificate signed by CA. The issue comes when I am trying to import the CA certificate (Root certificate) and Server Certificate into the Java Keystore.
I am importing the Root CA Certificate first which is successfully added to the keystore.
keytool -import -trustcacerts -alias mycacert -file cacert.pem -keystore mykeystore.jks -storepass Welcome1
Trust this certificate? [no]: yes
Certificate was added to keystore.
But when trying to add the Server Certificate to the keystore using the command below :
keytool -import -v -alias testserver -file server.cer -keystore mykeystore.jks -keypass Welcome1 -storepass Welcome1
Certificate reply was installed in keystore
I get the following error:
keytool error: java.lang.Exception: Failed to establish chain from reply
java.lang.Exception: Failed to establish chain from reply
at sun.security.tools.KeyTool.establishCertChain(KeyTool.java:2662)
at sun.security.tools.KeyTool.installReply(KeyTool.java:1870)
at sun.security.tools.KeyTool.doCommands(KeyTool.java:807)
at sun.security.tools.KeyTool.run(KeyTool.java:172)
at sun.security.tools.KeyTool.main(KeyTool.java:166)
Read many forums and tried to convert it to the PKCS#7 format and import the cert to the identity keystore, but was not successful in that either. I have also checked with the IT Admin team and found there is only one RootCA and no other intermediate CA's.
Please advice if any one has similar issues or suggestions.
Thanks in advance,
SVSHi,
One obvious reason would be that you did not specify -trustcacerts, and the root CA is not included in the present server keystore. In that case, using the -trustcacerts option would solve the problem, if the root CA is indeed in the JDK cacerts.
To print out the certificates present in the JDK cacerts, use the following command:
keytool -list -keystore <JAVA_HOME>/jre/lib/security/cacerts -storepass changeit -v
Then check if the root CA that signed your server certificate is present, and has not expired (in which case,you would need to re-import a newer one into cacerts).
Another common reason for that error message is when you have used a proprietary CA to sign your server certificate. Then it would obviously not be in the JDK cacerts. The solution in that case is to import your proprietary root CA into the JDK cacerts, using the following command:
keytool -import -keystore <JAVA_HOME>/jre/lib/security/cacerts -file yourRootCA.pem -storepass changeit -alias youralias
A third reason for that error message is when your server was signed by an intermediate certificate. In that case, you would have received from your CA a chain of certificates. One way to solve this (not the only one, but this one works well): Prepend your intermediate CA file to your server cert file, and import the obtained concatenated file into the server keystore. Be careful, the intermediate CA must be BEFORE the server cert. Example:
copy rootca.cer certchain.p7b
type server.cer >> certchain.p7b
The file certchain.p7b will be the concatenation of the intermediate CA and the signed server cert. Then import the newly created file under the key alias as follows:
keytool -import -keystore serverks.jks -file certchain.p7b -alias yourkey -trustcacerts
If you only prepend the intermediate root CA, you must make sure the the final root CA is in cacerts. But you can also prepend your whole chain of trust inside the server keystore.
Regards,
Kal
Maybe you are looking for
-
I have a pornographic search line on the top banner of Safari just under the bookmark icons that appears whenever I open up the onscreen keyboard and the top drops down a bit. Don't know where it came from the iPad is only one day old brand-new. I've
-
Problem with phone line after installation of BT I...
Hi, After persuading my dad (86) to switch from aol to BT infinity he is still without a working phone line. The phone line worked perfectly before switching to BT. Bt infinity was installed 5 weeks ago and ever since then his phone line developes
-
AFTER RANGE for multiple selection
Dear Experts, When defining two colkey ranges =EVRNG(A8:B9,C8:D9) Can I restrict my AFTER RANGE value only to the sencond range (C8:D9) I mean, make that the columns created by the EVAFTER only applys after the whole colkey range display the column c
-
My CWM/Nokia Store will download about 2/3 rds of the song and then refuse to save it on the PC. It obviously has the connection to the server, just can't save. Help please. I'm up to date with software and have the right to download and save, so it
-
Photoshop layer names not appearing in DVDSP
DVDSP 4.0.3, Photoshop 7.0, MacBook 2GHz, OS 10.4.10 Once I've brought my .psd file in to SP and added it to a layered menu, the layers appear, but their names do not, and I can't turn them off and on either. For example, in the inspector, under the