Users can't login after upgrading to Server 4

I've upgraded my classroom server to OS X Yosemite 10.10 and Server.app to Server 4. All of my client stations are running OS X Mavericks 10.9.5. Users were unable to login. I've then upgraded the entire lab to 10.10, that seems to have fixed the issue. Sort of. 2 of the client stations are still unable to login. They are Mid 2010 Mac Minis, I have 4 of them with the same specs, yet 2 work fine and 2 don't. The rest of the lab is also Mac Minis, all newer than the previous, all working fine. Any suggestions as to why those 2 don't want to cooperate?

In server administration, under Open Directory was set to Open Directory Master. I changed it to Standalone Server which is what we have and that took care of everything.

Similar Messages

Wiki won't accept OD user logins after upgrading to server 3.1.1

I have an OS X server 3.x running on OS X 10.9.3. I have several WiKi users, most are OpenDirectory (neiwork) users and one is a 'local' user. Prior to the weekend I was running Server 3.0.3 and all was good. Since uograding to Server 3.1.1 none of the network/OD users can log in to their Wikis. The local user can log in just fine. The network users can log in to all their other servcies (Mail, Calendar,Contacts, SMB/AFP shares etc.) just fine. They can also log into my regular SSL web-site which requires passwords. Only the wiki login is broken.
In the collabd.dlog file I see:
May 21 19:28:20 anarion.home.thejenkinsfamily.org.uk collabd[3747] <Error>: [CSAuthService.m:316 5b04000 +0ms] Digest did not validate
May 21 19:28:20 anarion.home.thejenkinsfamily.org.uk collabd[3747] <Error>: [CSServiceDispatcher.m:260 5b04000 +0ms] Caught exception "Invalid Credentials" [CSAuthBadDigest] executing [http]Request{AuthService.validateUsernameAndPasswordDigest:remember:(<<scrubbe d>>)}:
followed by an exception stack trace.
But of course the credential are valid.
Anyone seen this? Any ideas on how to fix it? Might it be fixed in the 3.1.2 update that came out a few days ago (I have not updated to that as yet)?
Thanks,
Chris

Okay, this problem has re-surfaced (on server 3.1.2). Here are the symptoms:
1.    It only affects network (Open Directory) users. It affects all network users.
2.    It only affects the Wiki service; OD users can authenticate for all other services (Mail, Contacts, Calendar, VPN, Time Machine, OS X login on client machines) without problem.
3.    Stopping and restarting the Wiki Servcie and the OD servcie does not fix the problem, but rebooting the server does. Things will then be fine for a while (I have not yet quantified how long 'a while' is) and then the problems occurs again.
4.    When the problem is present, even a newly created user cannot login to the Wiki servcie.
5.    When the login failure occurs, the collabd.log file contains the following:
Jun 1 09:52:23 anarion.home.thejenkinsfamily.org.uk collabd[73366] <Info>: [CSServiceDispatcher.m:237 b904000 +10979ms] TIMER: 0ms ---> Executed [http]Request{SettingsService.authSettings()}
Jun 1 09:52:23 anarion.home.thejenkinsfamily.org.uk collabd[73366] <Info>: [CSServiceDispatcher.m:237 b904000 +0ms] TIMER: 1ms ---> Executed [http]Request{AuthService.challengeForUsername:advanced:(newtesty,1)}
Jun 1 09:52:23 anarion.home.thejenkinsfamily.org.uk collabd[73366] <Info>: [CSExecutionTimer.m:14 b904000 +0ms] TIMER: 2ms ---> Executed batch BatchRequest{(
            "[http]Request{AuthService.challengeForUsername:advanced:(newtesty,1)}"
Jun 1 09:52:23 anarion.home.thejenkinsfamily.org.uk collabd[73366] <Info>: [CSServiceDispatcher.m:237 b904000 +119ms] TIMER: 0ms ---> Executed [http]Request{SettingsService.authSettings()}
Jun 1 09:52:23 anarion.home.thejenkinsfamily.org.uk collabd[73366] <Error>: [CSAuthService.m:316 b904000 +0ms] Digest did not validate
Jun 1 09:52:23 anarion.home.thejenkinsfamily.org.uk collabd[73366] <Error>: [CSServiceDispatcher.m:260 b904000 +0ms] Caught exception "Invalid Credentials" [CSAuthBadDigest] executing [http]Request{AuthService.validateUsernameAndPasswordDigest:remember:(<<scrubbe d>>)}:
                0   CoreFoundation                      0x00007fff920e325c __exceptionPreprocess + 172
                1   libobjc.A.dylib                     0x00007fff95709e75 objc_exception_throw + 43
                2   CSService                           0x000000010897ca2e -[CSAuthService sessionForDigest:remember:] + 1583
                3   CSService                           0x000000010897c3a7 -[CSAuthService validateUsernameAndPasswordDigest:remember:] + 65
                4   CoreFoundation                      0x00007fff91fcea5c __invoking___ + 140
                5   CoreFoundation                      0x00007fff91fce8c4 -[NSInvocation invoke] + 308
                6   CSService                           0x00000001088eba40 -[CSServiceDispatcher executeRequest:asPartOfBatch:usingServiceImpl:] + 4589
                7   CSService                           0x00000001088ec4dc __43-[CSServiceDispatcher executeBatchRequest:]_block_invoke_3 + 83
                8   CSService                           0x00000001088f1df0 -[NSArray(CollabBlockMethods) map:] + 233
                9   CSService                           0x00000001088ec435 __43-[CSServiceDispatcher executeBatchRequest:]_block_invoke_2 + 160
                10 CSService                           0x00000001088f2490 +[CSExecutionTimer recordTime:ofBlock:] + 78
                11 CSService                           0x00000001088f22c2 +[CSExecutionTimer timerNamed:aroundBlock:] + 77
                12 CSService                           0x00000001088ec1dd __43-[CSServiceDispatcher executeBatchRequest:]_block_invoke + 296
                13 PostgreSQLClient                    0x0000000108855941 -[PGCConnection transactionInBlock:onError:] + 150
                14 CSService                           0x00000001088ec03b -[CSServiceDispatcher executeBatchRequest:] + 285
                15 CSService                           0x000000010896f748 +[CSServiceDispatchHTTPRouter routeServiceRequest:response:] + 999
                16 CSService                           0x00000001088f2d1f __21-[CSServiceBase init]_block_invoke_6 + 48
                17 CSService                           0x000000010896c81a __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
                18 CSService                           0x000000010896fd6c -[CSHTTPBackgroundResponse bounce:] + 286
                19 Foundation                          0x00007fff91a2276b __NSThread__main__ + 1318
                20 libsystem_pthread.dylib             0x00007fff98b0f899 _pthread_body + 138
                21 libsystem_pthread.dylib             0x00007fff98b0f72a _pthread_struct_init + 0
                22 libsystem_pthread.dylib             0x00007fff98b13fc9 thread_start + 13
Jun 1 09:52:23 anarion.home.thejenkinsfamily.org.uk collabd[73366] <Info>: [CSExecutionTimer.m:14 b904000 +0ms] TIMER: 3ms ---> Executed batch BatchRequest{(
            "[http]Request{AuthService.validateUsernameAndPasswordDigest:remember:(<<scrubb ed>>)}"
Anyone have any suggestions before I log a bug with Apple?

Can't login after upgrade to version 7

After the forced upgrade to version 7 I can't login any longer (by microsoft account) to Skype. It shows the following error (see attachment).
Can someone please help me? For first time in years, I can't login to Skype and I really can't do without.
Solved!
Go to Solution.
Attachments:
foutskype.jpg ‏22 KB

Try this:
Reset all Internet Explorer settings:
http://support.microsoft.com/kb/923737
Open Internet Explorer. Go to Tools -> Internet Options -> Connections -> LAN settings. Make sure that the only option selected is “Automatically detect settings”.
Clear all Temporary Internet Files.
Open Internet Explorer -> Tools -> Internet Options -> General. In the section “Browsing history” press the “Settings” button and in the next window the “View files” button. Delete all files from the Temporary Internet Files folder.

Can't login after upgrade to 10.6.8

Hi
I am stuck in a login loop after upgrading from 10.6.4 to 10.6.8, the Login window accepts the password, the screen clears and after a short delay the login window reappears.
Some background info:
this is a 2010 iMac 21.5"
I have replaced a failed drive with a new one, reinstalled 10.6.4 with the install disc that came with the Mac
Did a successful Time Machine restore where the computer would boot and desktop and files were all intact.
A couple of programs complained about the OS needing updating so I used the Update feature to download and install 10.6.8
Now I cannot get past the logon screen.
Any suggestions to get past this screen?
thanks
Bob

Hi Eric
Thanks for your continued help
I borrowed another 10.6.4 DVD and have now managed to install 10.6.4 and update it to 10.6.8 and no longer have the logon loop issue. I've also verified/repaired the disc and repaired the file permissions successfully.
Time Machine has restored the desktop, all the music files are there, Photo's are there and Google Picassa runs, but little else.
Safari complains I have the wrong version of OSX and will not run so I can't browse the net (typing this on my laptop)
iTunes reports it requires 10.7.5 or later as do most other apps I've tried.
Fortunately Finder works, I've run the Software Update and it says I have the latest updates.
If I click on 'App Store', the store opens ok but the only Upgrade option I now see is to Yosemite, if I select that the App Store screen gives a spinning pointer and never does anything, I have to force quit through finder to get out of it.
any suggestions as to what to try next?
thanks
Bob

Can't login after upgrading to leapord

My accounts show up but when I click on one to enter my password I get the beach ball I've let it run for 20 minutes but the beach ball stays... Am I screwed?

I wanted to post as well so Apple can be assured there is a problem. I am also having the same password issues, after upgrading... only one "backup" non-admin account is accessible. I am positive I am typing everything correctly. Also, when I "log out" of this user, I get the blue screen and the "forever" beach ball as well.
Thanks goodness a friend of mine mentioned he was going to test the new system on his laptop first before installing on his main work computer. I decided to do the same. Good thing I did. I can only imagine the problems that are going to erupt after many people receive their upgrades today.
I am going to try the suggestions listed here - *thank you to those that posted* - even though some of the answers are making my head spin . I am beyond aggravated and disappointed that I am having such an issue and I haven't even gotten into using the new system. This is not the Apple I know and love.
Aggravated...

Can't login after upgrade...

I've just updated a 24 inch iMac (Aluminium 2.8ghz 4GB RAM 1TB HD) from 10.4.10 to Leopard, and when I log in to the main account (the 501 admin account), the screen fades to blue and then login screen fades back up after a few seconds. It just won't let me log in!
I've tried the solutions here of booting up in single user mode and resetting the password and account privileges on that account in case it's lost it's admin rights. I've also tried logging in using the root account by setting it's password but the same thing happens when I login with that account. I've also tried repairing the permissions and the disk from the Leopard DVD to no joy.
The Tiger system was pretty clean having only had Final Cut Studio 2 and Movie Magic ScreenWriter installed on it. It had been used for about two weeks doing some light-weight FCP work.
+I did the following things before I upgraded to Leopard:+
• Deleted an account (a second admin account)
• Ran software update in Tiger
• Install the iLife Support 8.1.1 update and the iMac Software Update 1.2 (Tiger)
• Shutdown
• Booted off the Leopard DVD and the update seemed to go fine.
I have a feeling that the iMac Software Update 1.2 (Tiger) broke things when I updated to Leopard as there seems to be a separate one for Leopard.
I think I'll probably reinstall the machine in case of any future issues, but has anyone else seen this issue before?
*A word of warning then* - don't run the iMac Software Update 1.2 (Tiger) update then upgrade to Leopard as you won't be able log in, _even as root!_

Hi Andrew - I'm having the exact same problem. Same computer tried the same fixes and getting the same blue screen that fades back to the login screen. The only exception is that I had no other programs installed - I pulled the computer straight out of the box and installed the Leopard update. I did however let Tiger run a software update for iLife and a few other things (I'm embarrassed to say that I didn’t pay enough attention to what was actually updated – too excited about moving on to Leopard I guess.) I was going to try and call tech support later today and will post back if I get a solution to this issue. Thanks for posting it, at least I know there is one other person out there with the same problem.

Can't Login After Upgrading To Snow Leopard

I finally updated to Snow Leopard but have run into a problem I don't know how to resolve. After installation completed and my MacBook booted up it won't take my password. I know the password is right because I just used it to update the software before installing 10.6 and my password hint corresponds with it. What can I do?
Thanks in advance!

Well, I thought it worked. When I booted from the disk and changed the password and then restarted it started up and did not ask me for the password but when I went to "About This Mac" it showed I was still running 10.5. I went through the 10.6 install again and got the same result. What can I do?

Can't login after upgrading to Leopard

There is a similar thread to this (http://discussions.apple.com/thread.jspa?threadID=1264420), but after reading and attempting to fix it using the solution from Apple about logging into single user, I ran into some problems.
After step 6, the list of users are shown. Mine shows:
.Ds_Store .localized Shared myusersname
Then after step 8, it says:
delete: Invalid Path
<dscl_cmd> DS Error: -14009 (eDSUnknownNodeName)
And after step 10, it tells me that the username shown from step 6 is an unknown username. That is strange since in the list of usernames, it shows that my username does exist. What is wrong? Thanks in advance.

Apparently, you're following the steps in http://support.apple.com/kb/TS1543 If so, that's what you should have referenced.
If you got an invalid path message, then you mistyped the string:
*dscl . -delete /Users/myusername AuthenticationAuthority*
IIRC, the error after step 10 results from not deleting it in step 8.
A hint. When posting problems, it's very beneficial if you post the command you used and the result. If my suspicion that you entered an incorrect item in step 8, that's what's causing your issue. Try again, ensuring that you write the commands and the results down for future postings.

Lync 2013 disabled user can still login.

Ok. so we have this weird behavior and it's been driving us crazy for over a week. We have a lync 2013 deployment on a forest with several child domains.<o:p></o:p>
In the middle of the deployment, we noticed that our changes to the user characteristics were not being updated. Eg: we enable or disable
enterprise voice, no changes. We change the sip URI, log out, login, nothing, no changes. And we noticed that if we disable the user from Lync server (from the lync controlpanel), the user can still login. We assumed some lag on AD replication, but no, a user
can still login after a week!<o:p></o:p>
The deployment is a standard Lync 2013, single FE, with a single Edge server. We have enabled Enterprise voice, changes to the enterprise voice routes are
working, if we enable or disable a route we can see it on the client, but changes on the dialplan are not reflected.<o:p></o:p>
I can’t find any reference to this behavior. I know if I disable a user from the AD he can still signing into Lync, but this is different, we are disabling
the user from Lync server. We even removed the user completely from Lync and he can still use it as normal.<o:p></o:p>
We checked the user using adsiedit and the msrtcsip-userenabled is set to false, we even voided the certificate via lync console. Still able to use it.
Suggestions?
Thanks in advance.
Fabio Ricci.

Hi,
Please check if there is any error message on FE Server when the issue happen.
It seems to be the issue of CMS replication.
Please check CMS replication status by running Get-CsManagementStoreReplicationStatus.
If CMS replication not update to the latest version, run Invoke-CsManagementStoreReplication.
If the issue persists, please check Lync Server update, make sure Lync Server update to the latest version, and then test again.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Users can't login to Groupwise after export

Hi All
We have a two-node cluster running GW7.01 on Netware 6.5 SP7. As part of our disaster recovery test we've done the following:
1. Installed netware 6.5 sp7 onto a new server in its own tree.
2. Installed GW7 on this server, with an identical groupwise system i.e same domain name, etc (only difference is server name, IP, and tree name).
3. We then exported the NDS/GW objects from the current production tree using the GWport32 utility into the new tree on the new server.
4. We've restored from a backup tape the PO database file and the accompanying files, the domain database file, and all the files and sundirectories from the ofuser, ofmsg, and offiles directories onto their corresponding locations on the new server.
5. After getting C00F and D019 errors, we've tried to rebuild the ngwguard.db and the PO by running a standalone GWCheck.
Our problem is that I can login to the new server (edirectory tree) as any user albeit without any password but unable to login to groupwise. I've set and reset passwords in ConsoleOne but I still can't login to groupwise.
We would be very grateful if anyone could tell us what else we need to do.
We're hoping to achieve a situation where in an extreme disaster, we are able to restore mail from tape backups so that users can still logon to this new server and have full access to their mailboxes with ease.
regards
AD

awuku wrote:
> Hi All
> We have a two-node cluster running GW7.01 on Netware 6.5 SP7. As part
> of our disaster recovery test we've done the following:
>
> 1. Installed netware 6.5 sp7 onto a new server in its own tree.
>
> 2. Installed GW7 on this server, with an identical groupwise system i.e
> same domain name, etc (only difference is server name, IP, and tree
> name).
>
> 3. We then exported the NDS/GW objects from the current production tree
> using the GWport32 utility into the new tree on the new server.
>
> 4. We've restored from a backup tape the PO database file and the
> accompanying files, the domain database file, and all the files and
> sundirectories from the ofuser, ofmsg, and offiles directories onto
> their corresponding locations on the new server.
>
> 5. After getting C00F and D019 errors, we've tried to rebuild the
> ngwguard.db and the PO by running a standalone GWCheck.
>
> Our problem is that I can login to the new server (edirectory tree) as
> any user albeit without any password but unable to login to groupwise.
> I've set and reset passwords in ConsoleOne but I still can't login to
> groupwise.
>
> We would be very grateful if anyone could tell us what else we need to
> do.
>
> We're hoping to achieve a situation where in an extreme disaster, we
> are able to restore mail from tape backups so that users can still logon
> to this new server and have full access to their mailboxes with ease.
>
> regards
> AD
>
>
I would NEVER have use GWPORT32. Why did you?
1. You have to restore eDirectory in a different way.
2. If tree is still intact reimporting is bad
3. IF tree is not intact, you still have to restore eDirectory differently.

After upgrading Exchange Server 2007 to SP3 with update rollup 13, OWA not working

Hi,
We have just installed Service Pack 3 and update rollup 13 on our Exchange Server 2007, but unfortunately our OWA has gone inaccessible.
PROBLEM- The following error comes up when we try to access OWA :
Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: Object reference not set to an instance
of an object.
Call stack
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication()
Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart(Object sender, EventArgs e)
Inner Exception
Exception type: System.NullReferenceException
Exception message: Object reference not set to an instance
of an object.
Call stack
Microsoft.Exchange.Clients.Owa.Core.Configuration.CheckPublicFolders(ADSystemConfigurationSession session, ADObjectId[] pfdbIds, Boolean& allLegacy, Boolean& allLater)
Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor(ADSystemConfigurationSession session, String virtualDirectory, String webSiteName, ADObjectId distinguishedName, Boolean isPhoneticSupportEnabled)
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration()
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
ACTION TAKEN SO FAR :
1. Removed OWA virtual directories and recreated them again.
2. IIS has been reset.
3. Restarted the HUB/CAS server.
4. Created public folder database.
Even after doing all these activities, owa is still inaccessible. Please help.
Regards,
Ankur

Hi Ankur,
From your description, you can't access to OWA after upgrading Exchange server 2007 to SP3 rollup 13. Firstly, please locate to C:\ExchangeSetupLogs and make sure that it is a successful installation. If not, this issue often occurs.
If it is a successful upgrading, please follow the steps below for troubleshooting.
1. Open IIS Manager, click Default Web Site -> Authentication, make sure that Anonymous Authentication and Windows Authentication are enabled.
2. Click Default Web Site -> SSL Settings, check "Require SSL" and click Ignore.
3. Click Default Web Site -> HTTP Redirect, check Redirect (enter your
https://URL), check "Only redirect" box and Status code Found 302.
4. Expand Server Configuration -> Client Access ->double click owa ->Authentication tab. Check the Basic Authentication and check the Use forms-based authentication button Logon Format: Domain\user name.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Caldavd failing to start after upgrade to Server 3.2.1

This problem, caldavd not starting after upgrading to Server 3.2.1, is a variation on the theme of PostgresQL not starting. It too boils down to a postgres database not having been updated properly. Below are the steps needed to fix this problem:
sudo su -
# Change to the directory with the postgres database for the calendars and contacts
cd /Library/Server/Calendar\ and\ Contacts/Data/Database.xpg
# Disable caldavd for now
launchctl unload -w /Applications/Server.app/Contents/ServerRoot/System/Library/LaunchDaemons/org.c alendarserver.calendarserver.plist
# move the broken database out of the way and build a new empty one
mv cluster.pg broken-cluster.pg
mkdir cluster.pg && chmod 700 cluster.pg && chown _calendar:_calendar cluster.pg
sudo -u _calendar /Applications/Server.app/Contents/ServerRoot/usr/bin/initdb "/Library/Server/Calendar and Contacts/Data/Database.xpg/cluster.pg" -E utf8 --lc-ctype=C
# Finish the upgrade job that never completed by explicitly invoking the previous version of postgres:
sudo -u _calendar /Applications/Server.app/Contents/ServerRoot/usr/bin/pg_upgrade -b /Applications/Server.app/Contents/ServerRoot/usr/libexec/postgresql9.2 -B /Applications/Server.app/Contents/ServerRoot/usr/bin -d /Library/Server/Calendar\ and\ Contacts/Data/Database.xpg/cluster.pg.original_for_upgrade/ -D /Library/Server/Calendar\ and\ Contacts/Data/Database.xpg/cluster.pg
# Mark the newly upgraded database as no longer in need of an upgrade
sudo -u _calendar touch cluster.pg/.NoRestoreNeeded
# Start caldavd back up
launchctl load -w /Applications/Server.app/Contents/ServerRoot/System/Library/LaunchDaemons/org.c alendarserver.calendarserver.plist
And everything should be the way it should have been in the first place!

Hi, I have the same issue and Linc Davis pointed me to this thread from Re: Server Calendar migration failed.
Your solution already got me somewhere, so thanks for that
I need to note that my machine is on Yosemite (10.10.1) and I'm running Server 4.
The only issue I have is that I get an error message when running pg_upgrade, the log says:
pg_upgrade run on Fri Jan 23 09:31:30 2015
command: "/Applications/Server.app/Contents/ServerRoot/usr/libexec/postgresql9.2/pg_ctl" -w -l "pg_upgrade_server.log" -D "/Library/Server/Calendar and Contacts/Data/Database.xpg/b$
waiting for server to start....LOG: database system was interrupted; last known up at 2013-11-02 12:21:52 CET
LOG: creating missing WAL directory "pg_xlog/archive_status"
LOG: starting archive recovery
LOG: restored log file "000000010000000000000002" from archive
LOG: invalid magic number D075 in log file 0, segment 2, offset 0
LOG: invalid checkpoint record
FATAL: could not locate required checkpoint record
HINT: If you are not restoring from a backup, try removing the file "/Library/Server/Calendar and Contacts/Data/Database.xpg/broken-cluster.pg/backup_label".
LOG: startup process (PID 12315) exited with exit code 1
LOG: aborting startup due to startup process failure
........................................................... stopped waiting
pg_ctl: could not start server
Examine the log output.
The log talks about removing the backup_label file. When I do that the log says the following:
pg_upgrade run on Fri Jan 23 09:41:34 2015
command: "/Applications/Server.app/Contents/ServerRoot/usr/libexec/postgresql9.2/pg_ctl" -w -l "pg_upgrade_server.log" -D "/Library/Server/Calendar and Contacts/Data/Database.xpg/b$
waiting for server to start....LOG: database system was interrupted; last known up at 2013-11-02 12:21:52 CET
LOG: starting archive recovery
LOG: invalid magic number D075 in log file 0, segment 2, offset 0
LOG: invalid primary checkpoint record
LOG: could not open file "pg_xlog/000000010000000000000001" (log file 0, segment 1): No such file or directory
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
FATAL: the database system is starting up
.LOG: startup process (PID 15068) was terminated by signal 6: Abort trap
LOG: aborting startup due to startup process failure
stopped waiting
pg_ctl: could not start server
Examine the log output.
Thanks already for the help

A particular network user can't login to a mac in a classrom but other network users can. Then the network user can login to other identical macs in same classroom. Anyone seen this before?

A particular network user can't login to a mac in a classrom but other network users can. Then the network user can login to other identical macs in same classroom. Anyone seen this before? It has happen twice. Two different teachers in two different classrooms entering the correct user name and passwords and computer won't allow them to login. Then they try in different computers in same classroom and have no problem login.

Yes. I can login with a test user. And any other network user can login as well to this particular mac. Actually the mac has bootcamp and boots into either mac or windows. The same user entering the same login username and password can login into the windows side, but not the mac side.
I had this same issue last semester in another classroom, another mac and a different teacher. This summer I reformatted and imaged that mac and I asked that teacher to login today to that reimagened mac and she had no problem today doing so.

For Those Who Can't Boot After Upgrading To 10.5.6

For Those Who Can't Boot After Upgrading To 10.5.6
(and i am one of those)
how is Apple supposed to make them able to install future fixes and updates
once they finally acknowledge and address this horrible bug?
will they send free bootable CDs with the updates to 10.5.6?

What "Boot ROM version" do you have (check in the system profiler under "Hardware")? If it's not MBP31.0070.B07 or MBP21.00A5.B08, then you will need to update your MacBook Pro's firmware. To do this, you might need to connect an external display and mouse/keyboard, and then run the computer with the lid closed to bypass the laptop's monitor. Then apply the firmware patch and reboot the system. This might also be doable via "Screen Sharing" if you have that enabled and have another mac handy.
The firmware update is here: http://www.apple.com/downloads/macosx/apple/firmware_hardware/macbookproefifirmw areupdate151.html
Message was edited by: Topher Kessler

R12 upgrade : Historical data can be traited after upgrade to 12.1.3

Hello,
I'm testing an upgrade from 11.5.10.2 to 12.1.3 =< Path = upgrade to 12.1.1 and upgrade to 12.1.3.
My question is :
If we want run upgrade historycal data in post upgrade ,do i have to run it after 12.1.1 upgrade or i can run it after upgrade 12.1.3 if i didn't start managers betwwen upgrade 12.1.1 and 12.1.3...?
thanks

I'm testing an upgrade from 11.5.10.2 to 12.1.3 =< Path = upgrade to 12.1.1 and upgrade to 12.1.3.
My question is :
If we want run upgrade historycal data in post upgrade ,do i have to run it after 12.1.1 upgrade or i can run it after upgrade 12.1.3 if i didn't start managers betwwen upgrade 12.1.1 and 12.1.3...?You can run it after the upgrade when the application is up and use option=hotpatch when running adpatch (does not require an outage).
Oracle E-Business Suite Upgrade Guide Release 11i to 12.1.1 [ID 1082375.1]
Thanks,
Hussein

Users can't login after upgrading to Server 4

Similar Messages

Maybe you are looking for