Main account fails to login

I am using a G4 iBook running OS X 10.4.10. I have already run repair permissions and the automated maintenance of Onyx.
The main account I use, which is not an admin account, fails to login. My wife's account and the admin account both still works. What happens is that I select the account and type in the password. When I hit enter the password is highlighted and the "log in" and "back" buttons become disabled. However, the loading bar does not appear at all and no logging in happens. I have noticed that I can still re-enter the password but the buttons are still disabled. I have the restart the computer to get back to the login screen.
This problem began immediately after the computer suddenly turned off while I was browsing the iTunes store.
Message was edited by: Robert Monroe

Two things to try, Robert. Go to System Preferences > Accounts and see if there is anything strange in your Login Items.
Then boot from your Mac OS X install DVD and go to Disk Utility and run repair disk. You've already correctly run repair permissions (you do this while booted from your internal HD). But you have to boot from your install DVD to run repair disk. Somethin in your Mac's directory might have been disturbed when the computer suddenly turned off while you were using it. Repair disk is capable of fixing some of these problems.
Regards,
Steve M.

Similar Messages

SP2010 Application Pool Service Account fails to login to master database on a SQL Server mirror

This is a weird problem that just started showing up, cause unknown. Could go in this forum or in SQL 2008...I put it here because for me the context is SP2010.
We have 2 SQL servers (2008 R2 with SP1). Each server has 2 named instances, the second being a mirror for the other server's main instance. In other words, the named instance /SQL has a /SQLMirror on the other server and vice versa.
The error is: Login failed for user 'domain\sharepointapppoolaccount'. Reason: Failed to open the explicitly specified database.
As best I can tell, the specified database is "master" on the mirror instance. I am unaware of any reason for the app pool account to be connecting to the master on the mirror (the master database itself is NOT mirrored). There is nothing
in the user mapping that would suggest any reason to try connecting. And there are no equivalent errors in the main instance (SQL).
SP2010 Event ID 18456 - Why would a service account try to connect to the master database?

Hi,
When the principal server(SQL) disconnects clients from the principal database, then the mirror server(SQL) will take charge of clients’ requests.
So the error is regarding to the mirror server may be due to that the mirror server is taking charge of the clients’ request instead of the principal server when the principal is becomes unavailable.
I recommend to grant sysadmin permissions to the service account in SQL(mirror server) to see if the issue still occurs.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Can not log into server computer with any accounts - "You are unable to login to the user account "abcdefg" at this time. Logging in to the account failed because an error occurred."

I have a Mac mini running the latest version of OS X and Server. Been running fine and flawlessly. However, I had a strange problem with the iCloud preferences panel crashing when I tried to access it, so I rebooted. Now I can not log into the system with any accounts. My master admin account (along with all the others) gives me the error:
You are unable to login to the user account "abcdefg" at this time. Logging in to the account failed because an error occurred."
I am able to see the server from other macs and I can log into it using the same account, but it only shows me a few of the shared folders I have access to but NOT to my main directories.
Rebooting into Command-R and doing a disk utility, I try and repair permission on that drive and get a bunch of errors like:
ACL found but not expected on Users
Repaired "Users"
ACL found but not expected on Users/.localized
Repaired "Users/.localized"
ACL found but not expected on Users/Shared
Repaired "Users/shared"
ACL found but not expected on Users/Shared/.localized
Repaired "Users/Shared/.localized"
Permissions repair complete.
But rebooting is no joy...same problem. Any idea what is going on or how to repair it? Should I do a time machine restore? Complete new OS X install? Any idea what is causing this or how to salvage it?

Got everything to re-install and it worked fine...for a few hours. Then I came in to find ALL of my network users deleted. Just GONE. Then found out the Open Directory was trashed and was unable to open, recover or restore from a backup. Looks like I may have a bad drive here.
I installed a new drive in the system, re-installed and so far (for a couple of hours anyway) the system seems to be working and stable.

No task bar/menu bar or icons appear when I login into my main account, however this is not a problem with my guest accout

So was trying to use install disk ! to solve the problem but did not want to reinstall the system because I have not backed up many of my photographs. Then the disk got stuck and would not come out so when I shut down and restarted I could not get past the gray screen. Well I was able to solve the problem and remove the disk, and finally it would load to the login screen, although it took some time to get there. Then when I log in to my main account the desktop will load but the task bar and icons will not its completely blank except for the wall paper. When I login into my guest account there is not a problem everything is there and functional. I've been researching but have had no luck on a solution. Thank you for your help.

Hello,
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive & clear caches.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.

An account failed to log on unknown username or password. Causing Login audit failures

I have a SBS11 Essentials server that is getting audit Failures over and over again. There computer account says it's the SBS11 server it's self. It says unknown user name or bad password. I have checked for scheduled tasks, backup jobs, services and
non of them are using any special user accounts. I have used MS network monitor and can't find anything helpful to lead to the issue. All computers in the network are running Windows 7. The domain functional level is 2008 R2.
I get a the 4768 event ID about a Kerberos event and then just after I get a Event ID 4625 account failure with Logon Type 3. I have includes the events below. I need to figure what is causing the audit failures as my GFI Test Hacker alert is
catching it every morning. Disabling the Test Hacker alert is not a option. I have used Process Explorer also but can't seem to pin it down. I also enabled Kerberos logging.
http://support.microsoft.com/kb/262177?wa=wsignin1.0. All event codes state its a unknown or no existing account but how do I stop it from happening?
This is from the System Event log
A Kerberos Error Message was received:
on logon session TH.LOCAL\thsbs11e$
Client Time:
Server Time: 14:59:53.0000 3/4/2014 Z
Error Code: 0x6 KDC_ERR_C_PRINCIPAL_UNKNOWN
Extended Error:
Client Realm:
Client Name:
Server Realm: TH.LOCAL
Server Name: krbtgt/TH.LOCAL
Target Name: krbtgt/[email protected]
Error Text:
File: e
Line: 9fe
Error Data is in record data.
This is from the Security Event log
A Kerberos authentication ticket (TGT) was requested.
Account Information:
Account Name: S-1-5-21-687067891-4024245798-968362083-1000
Supplied Realm Name: TH.LOCAL
User ID: NULL SID
Service Information:
Service Name: krbtgt/TH.LOCAL
Service ID: NULL SID
Network Information:
Client Address: ::1
Client Port: 0
Additional Information:
Ticket Options: 0x40810010
Result Code: 0x6
Ticket Encryption Type: 0xffffffff
Pre-Authentication Type: -
Certificate Information:
Certificate Issuer Name:
Certificate Serial Number:
Certificate Thumbprint:
Certificate information is only provided if a certificate was used for pre-authentication.
Pre-authentication types, ticket options, encryption types and result codes are defined in RFC 4120.
I then get teh following error in the next event
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: THSBS11E$
Account Domain: TH
Logon ID: 0x3e7
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name:
Account Domain:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064
Process Information:
Caller Process ID: 0x25c
Caller Process Name: C:\Windows\System32\lsass.exe
Network Information:
Workstation Name: THSBS11E
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Schannel
Authentication Package: Kerberos
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Well I opened the case for him and he never followed up with Microsoft :-(
It's a kerberos issue, we're told to ignore it. Would you be willing to be patient and stubborn and work with CSS to at least understand what's going on better? I can tell you it's normal with Essentials but not the exact technical reason it's
happening.
Unfortunately TechNet isn't coming back, sorry folks :-(

CSCtg09895 - percentMGBL-exec-3-ACCT_ERR main: command accounting failed

Dear fellows,
I am facing below problem in one of ASR 9010 router while configuring . I am unable to config anything after entering any command this error shows up
RP/0/RSP0/CPU0:hostname(config)#interface TenGigE0/1/0/0
RP/0/RSP0/CPU0:Jan 15 12:48:41.186 IST: config[65887]: %MGBL-CONFIGCLI-3-AAA_ERR : Failed to execute a AAA operation - Command accounting failed - - 'LOCALD' detected the 'fatal' condition 'No available method was able to process the request'
RP/0/RSP0/CPU0:(config-if)# description # TO-Remote_site
RP/0/RSP0/CPU0:hostname(config-if)#RP/0/RSP0/CPU0:Jan 15 12:48:41.263 IST: config[65887]: %MGBL-CONFIGCLI-3-AAA_ERR : Failed to execute a AAA operation - Command accounting failed - - 'LOCALD' detected the 'fatal' condition 'No available method was able to process the request'
RP/0/RSP0/CPU0:hostname(config-if)#commit
Thu Jan 15 12:48:50.521 IST
RP/0/RSP0/CPU0:Jan 15 12:48:50.521 IST: config[65887]: %MGBL-CONFIGCLI-3-AAA_ERR : Failed to execute a AAA operation - Command accounting failed - - 'LOCALD' detected the 'fatal' condition 'No available method was able to process the request'
it is not allowing even to commit any change
and unable to find any online solutions for this.
please help
following packages are active right now
disk0:asr9k-doc-px-4.3.4
disk0:asr9k-fpd-px-4.3.4
disk0:asr9k-k9sec-px-4.3.4
disk0:asr9k-mcast-px-4.3.4
disk0:asr9k-mgbl-px-4.3.4
disk0:asr9k-bng-px-4.3.4
disk0:asr9k-mini-px-4.3.4
disk0:asr9k-mpls-px-4.3.4

it is a fresh installation and the device is not connnected to ny network yet.
I am facing below problem in one of ASR 9010 router while configuring . I am unable to config anything after entering any command this error shows up
RP/0/RSP0/CPU0:hostname(config)#interface TenGigE0/1/0/0
RP/0/RSP0/CPU0:Jan 15 12:48:41.186 IST: config[65887]: %MGBL-CONFIGCLI-3-AAA_ERR : Failed to execute a AAA operation - Command accounting failed - - 'LOCALD' detected the 'fatal' condition 'No available method was able to process the request'
RP/0/RSP0/CPU0:(config-if)# description # TO-Remote_site
RP/0/RSP0/CPU0:hostname(config-if)#RP/0/RSP0/CPU0:Jan 15 12:48:41.263 IST: config[65887]: %MGBL-CONFIGCLI-3-AAA_ERR : Failed to execute a AAA operation - Command accounting failed - - 'LOCALD' detected the 'fatal' condition 'No available method was able to process the request'
RP/0/RSP0/CPU0:hostname(config-if)#commit
Thu Jan 15 12:48:50.521 IST
RP/0/RSP0/CPU0:Jan 15 12:48:50.521 IST: config[65887]: %MGBL-CONFIGCLI-3-AAA_ERR : Failed to execute a AAA operation - Command accounting failed - - 'LOCALD' detected the 'fatal' condition 'No available method was able to process the request'
it is not allowing even to commit any change
and I am unable to find any online solutions for this.
please help
following packages are active right now
disk0:asr9k-doc-px-4.3.4
    disk0:asr9k-fpd-px-4.3.4
    disk0:asr9k-k9sec-px-4.3.4
    disk0:asr9k-mcast-px-4.3.4
    disk0:asr9k-mgbl-px-4.3.4
    disk0:asr9k-bng-px-4.3.4
    disk0:asr9k-mini-px-4.3.4
    disk0:asr9k-mpls-px-4.3.4
PS: please tell what more output are needed so that this problem can be solved.

Main Account Login error

Here was my situation:
I've had my MacBookPro since it first came out years ago so I was running on Tiger. I decided to upgrade to Snow Leopard (bad idea, if it ain't broke, don't fix it)
Basically the problem was that after I upgraded to SL I was not able to access my main administrator account because of a FileVault error and I didn't back up my data. So what did I do to recover them?
1. If you don't have a second administrator account just create one and log in (you should have no problems but if you do, sorry I can't help you there, I'm not an expert, I just got lucky).
2. Double click into macintosh HD>users> look at your other administrator's account folder, it has a red dot, and when you double click on it it a message will say you need permission.
3. Click on it one then go to File>Get Info
at the bottom you will see sharing and permission, just simply add your user to have read&write access, make sure to go to the drop down menu right below that and choose "apply to enclosed items"
I was able to go in and back up my music, word documents and pictures from my main account
If you are not able to access your main administrator account by using that method then I suggest you try Target Mode. That's when you use a firewire cable to connect your mac to another mac, restart the mac that does not have the problem white holding T, it will now act like an external drive and you might be able to retrieve your data. If no good then take it to a mac expert near you. Good Luck!

I have a much better suggestion. *Back up your data before upgrading!* then you don't have to jump through hoops in case things go wrong with the upgrade. you should back up at all times in any case. and if you are using filevault without regularly backing up you are simply begging for so much trouble that it is sure to accommodate you eventually. disk images frequently get corrupted. when an encrypted disk image like the one keeping your filevault data gets corrupted the chances of data recovery are just about zero.
Message was edited by: V.K.

Error message: "Logging into the account failed because an error occurred."

Hello,
We had an XServe G5 2.0 DP 5GB/80/2x250 running Mac OS X 10.3.9 Server with all updates as a main server for a school. The server provides Open Directory Master as well as File-Sharing (AFP and SMB) and e-mail services to about 30 teachers and 300 students. The user home directories reside on the server. A web server also runs on the machine. The students use a pool of laptops, which are configured with a local guest and admin account as well as access to the server-based home directories with Directory Access. The server had the OS running on the 80 GB hard drive and all data (Home directories, mail database, website, etc. were on the two mirrored 250 GB drives.) All was working well until...
A few weeks ago, one of the two 250 GB died. We decided to use the opportunity to upgrade the server and set it up with 3 x 750 GB, two drives running as a mirrored pair to hold OS AND Data, the other as a stand-by unit to help replace a failing drive.
We migrated the OS and all data from the previous drives without a problem. Since now, all data is residing on one pair of drives, we put the data from the old "Data" drive in a folder on the root level of the new HD pair. We wrote a script that launches at startup which creates the symlink in /Volumes/Data to link to /Data. We thought that with this, all would be well.
However: When any user tries to log into his account from any iBook (10.3.9 or 10.4.11) (wirelessly), he gets the message:
"Logging into the account failed because an error occurred. The home folder for the user account is located on an afp or smb server. contact your system administrator for help"
If the user logs in to the guest account on the iBook, then accesses his home directory via file-sharing, he can see (read/write) all his data. So, the data and privileges seem to be OK, as well as Open Directory working correctly. Mail and the web work well also, as does logging in to a user account from one of the PC's (wired).
Can anyone make any suggestions as to how to fix the situation? Currently, the users are using the guest accounts and accessing their data via filesharing, as well as using webmail for their e-mail, but this is a major nuisance.
Any help will be greatly appreciated.
Best regards,
Alain Chammas
A user trying to access his account from a PC (wired) has no problems.

A good number of folks are having problems with this same error message at login, and nobody seems to have found a fix.
I believe I have stumbled upon, if not a solution, at least part of the answer. If you're logged into a 10.4 workstation, open a Finder window and click the "Network" icon. The first time you do this, you'll only see "Library" and "Servers" icons, but if you let it sit for a moment, other folders will magically appear. One of these is "My Network" which is the critical part.
In Workgroup Manager, edit one of your users' home directory configuration. There's a URL piece, usually "afp://server.domain.com/Users" (which is what shows up in the window when you click on the "Home" tab for that user), and then there's a "Home" path that is usually something like "/Network/Servers/servername/Users/username". Trouble is, you've noticed that 10.4 doesn't put servers into the "Servers" path, but rather into the "My Network" path.
So, if you change that "Home" path to read "/Network/My Network/servername/Users/username", it should work--with one caveat. Apparently 10.4 doesn't create the "My Network" path on a given client until you actually browse the network on that client. If you haven't logged into a 10.4 workstation and browsed the network, the "My Network" path won't be there, and you'll still get the error. Login as a local user, browse the network (so that the "My Network" folder shows up), logout, and then login as an Open Directory user, and it should work.
I'm betting that 10.3, 10.4, and 10.5 all handle this issue differently, so if you're in a mixed-version situation, you may have to experiment to find a workable fix.
Derndest thing I ever saw.

Logging in to the account failed because an error occurred

I've been looking after Mac's in an ophthalmologist's office for about 6 years. We initially used Panther server with networked home directories. With the large images, slow computers, and slow network we moved about 4 years ago to local accounts and local home directories using a Leopard Server for file sharing and print serving. About a year ago we moved to a Mac Mini Server but kept local home directories. We would like to move back to networked home directories and implement group folders for sharing.
I have another Mac Mini Server at home and am trying to set up a test environment but am having trouble getting networked home directories to work. I'm trying to log in using my MacBook Pro. Both machines are at 10.6.8. I followed the outstanding setup instructions from
         http://www.wazmac.com/servers_network/fileservers/osxserver_setup/osxserver106_s etup.htm
but omitted the part of setting up the groups.   I just set up an account, Test1 but am unable to log in using it. I can log into the account and access the home folder through my finder though. When I try log in I get:
         You are unable to log in to the user account "test1" at this time
          logging in to the account failed because an error occurred.
I have looked for several days now and have found no answers that have resolved this.
My DNS tests fine and it appears that my password is working. I have turned off all the services except for AFP, DNS, and Open Directory. The home folder is on the second drive /Volumes/MacHD2/Homes/test1 and it is set for automount and home directories. I set each of the separately with a save between. The server appears in my /Network/Servers/ directory right down to the Homes directory.
The following is the only log file that indicates any error. This is from the most recent reboot:
Directory Services Error Log:
2011-07-09 09:19:12 PDT - T[0x00007FFF70C75CC0] - DNSServiceProcessResult returned -65563
2011-07-09 09:19:45 PDT - T[0x0000000101C8D000] - Misconfiguration detected in hash 'Global SID':
2011-07-09 09:19:45 PDT - T[0x0000000101C8D000] - Computer 'guest' (/LDAPv3/127.0.0.1) - ID -1 - UUID 3A0E5953-EC2B-4F6E-A929-3B32406A10C3 - SID S-1-5-21-3687144454-2494095375-1043814123-998
2011-07-09 09:19:45 PDT - T[0x0000000101C8D000] - Computer 'MiniServer.tolan.homeip.net$' (/Local/Default) - ID -1 - UUID 87FB76C0-A528-44FC-ADBF-2A7EC7809A9A - SID S-1-5-21-3687144454-2494095375-1043814123-998
2011-07-09 09:19:45 PDT - T[0x0000000101C8D000] - Misconfiguration detected in hash 'Global SID':
2011-07-09 09:19:45 PDT - T[0x0000000101C8D000] - Computer 'guest' (/LDAPv3/127.0.0.1) - ID -1 - UUID 3A0E5953-EC2B-4F6E-A929-3B32406A10C3 - SID S-1-5-21-3687144454-2494095375-1043814123-998
2011-07-09 09:19:45 PDT - T[0x0000000101C8D000] - Computer 'MiniServer.tolan.homeip.net$' (/Local/Default) - ID -1 - UUID 87FB76C0-A528-44FC-ADBF-2A7EC7809A9A - SID S-1-5-21-3687144454-2494095375-1043814123-998
The following are the relevant messages from the other log files that captured the login attempt:
AFP Access Log:
IP 192.168.77.20 - - [09/Jul/2011:11:25:11 -0800] "Login test1" 0 0 0
IP 192.168.77.20 - - [09/Jul/2011:11:25:11 -0800] "Logout test1" 0 0 0
DNS Log:
09-Jul-2011 09:38:09.777 received control channel command 'freeze'
09-Jul-2011 09:38:09.778 freezing all zones: success
09-Jul-2011 09:38:09.885 received control channel command 'reload'
09-Jul-2011 09:38:09.885 loading configuration from '/private/etc/named.conf'
09-Jul-2011 09:38:09.886 using default UDP/IPv4 port range: [49152, 65535]
09-Jul-2011 09:38:09.886 using default UDP/IPv6 port range: [49152, 65535]
09-Jul-2011 09:38:09.888 reloading configuration succeeded
09-Jul-2011 09:38:09.888 reloading zones succeeded
09-Jul-2011 09:38:09.889 zone 77.168.192.in-addr.arpa/IN/com.apple.ServerAdmin.DNS.public: loaded serial 2011070804
09-Jul-2011 09:38:09.889 zone tolan.homeip.net/IN/com.apple.ServerAdmin.DNS.public: loaded serial 2011070900
09-Jul-2011 09:38:09.893 received control channel command 'thaw'
09-Jul-2011 09:38:09.893 thawing all zones: success
09-Jul-2011 09:38:09.893 zone 77.168.192.in-addr.arpa/IN/com.apple.ServerAdmin.DNS.public: loaded serial 2011070804
09-Jul-2011 09:38:09.893 zone tolan.homeip.net/IN/com.apple.ServerAdmin.DNS.public: loaded serial 2011070900
Kerberos Server Log:
Jul 09 11:25:07 MiniServer.tolan.homeip.net krb5kdc[55](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.77.20: NEEDED_PREAUTH: [email protected] for krbtgt/[email protected], Additional pre-authentication required
Jul 09 11:25:07 MiniServer.tolan.homeip.net krb5kdc[55](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.77.20: NEEDED_PREAUTH: [email protected] for krbtgt/[email protected], Additional pre-authentication required
Jul 09 11:25:07 MiniServer.tolan.homeip.net krb5kdc[55](debug): handling authdata
Jul 09 11:25:07 MiniServer.tolan.homeip.net krb5kdc[55](debug): handling authdata
Jul 09 11:25:07 MiniServer.tolan.homeip.net krb5kdc[55](debug): .. .. ok
Jul 09 11:25:07 MiniServer.tolan.homeip.net krb5kdc[55](debug): .. .. ok
Jul 09 11:25:07 MiniServer.tolan.homeip.net krb5kdc[55](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.77.20: ISSUE: authtime 1310235907, etypes {rep=18 tkt=16 ses=18}, [email protected] for krbtgt/[email protected]
Jul 09 11:25:07 MiniServer.tolan.homeip.net krb5kdc[55](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.77.20: ISSUE: authtime 1310235907, etypes {rep=18 tkt=16 ses=18}, [email protected] for krbtgt/[email protected]
Jul 09 11:25:11 MiniServer.tolan.homeip.net krb5kdc[55](info): TGS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.77.20: ISSUE: authtime 1310235907, etypes {rep=18 tkt=16 ses=18}, [email protected] for afpserver/[email protected]
Jul 09 11:25:11 MiniServer.tolan.homeip.net krb5kdc[55](info): TGS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.77.20: ISSUE: authtime 1310235907, etypes {rep=18 tkt=16 ses=18}, [email protected] for afpserver/[email protected]
Password Service Server Log:
Jul 9 2011 11:25:07    RSAVALIDATE: success.
Jul 9 2011 11:25:07    AUTH2: {0x4e17e4b75f13dc1d0000000600000006, test1} DHX authentication succeeded.
Jul 9 2011 11:25:07    KERBEROS-LOGIN-CHECK: user {0x4e17e4b75f13dc1d0000000600000006, test1} is in good standing.
Jul 9 2011 11:25:07    KERBEROS-LOGIN-CHECK: user {0x4e17e4b75f13dc1d0000000600000006, test1} authentication succeeded.
Jul 9 2011 11:25:07    GETPOLICY: user {0x4e17e4b75f13dc1d0000000600000006, test1}.
Jul 9 2011 11:25:07    GETPOLICY: user {0x4e17e4b75f13dc1d0000000600000006, test1}.
I would appreciate any and all assistance with this. I've never had a problem in the past with configuring and using networked home directories. This has me stumped. This is now my 3rd day working on it. I've been through numerous discussion groups, googled endlessly, and even re-installed the server software twice to make sure I'm working with a clean current copy.
Thanks in advance for any advice you can offer....

Thanks for your comments, and particularly for confirming that the Kerberos and AFP logs indicated success.   I did have my sharing set properly as you describe however checking that I had set sharing appropriately it led me to the answer to my problem...
You were right about the location of Test1's home directory and it is on the second disk.   I have always had a level of discomfort setting up the Home URL under 'Home' when setting up a home directory. I thought I had to put the fully qualified directory name, in this case:
      afp://miniserver.tolan.homeip.net/Volumes/MacHD2/Homes
After turning sharing off and on for the Homes directory, just to ensure, I saw that WGM had inserted another, more abbreviated URL for me to select:
      afp://MiniServer.tolan.homeip.net/Homes
When I selected this URL all started working.   I guess I've been outsmarting myself over the years by overthinking what I had to do.
So, while your suggestion was correct, that wasn't my problem, but checking to ensure that I'd done it right did lead me to the solution.   Hence, a helpful answer, rather than a correct one even though you are correct.
This issue of what the URL should look like has always bothered me but now I know. I guess I've just been lucky up until now and in this business good luck doesn't teach you anything...   :-)
Cheers, and thanks for this...

Cannot open database "ReportServer" requested by the login. The login failed. Login failed for user 'USER LOGON'

I want to grant permissions to all domain users to view reports on our Report Server. Domain users are able to access our Report Server URL and folder, but when they click on a report item they get an error message:
"Cannot open database "ReportServer" requested by the login. The login failed. Login failed for user 'USER LOGON'"
I'm using windows authentication and configured the local service account in SSReportS Config Manager as the credentials to connect to the Report Server DB.
Can someone please help how I should properly do this step by step to give all domain users permissions to view a report in SSRS?
Thanks much! - Rookie DBA

Hi IWAR,
The error message "Cannot open database "ReportServer" requested by the login. The login failed. Login failed for user 'USER LOGON'" means the user 'USER LOGON' does not have permissions to access the "ReportServer" database.
To fix this issue, please verify that the user has a valid database user login. For more details, please refer to the following steps.
In SQL Server Management Studio, open Object Explorer and expand the Databases folder.
Expand the database in which to create the new database user.
Right-click the Security folder, point to New, and then click User.
On the General page, enter a name for the new user in the User name box.
In the Login name box, enter the name of a SQL Server login to map to the database user.
Click OK.
Reference:
http://technet.microsoft.com/en-us/library/ms156468(v=sql.105).aspx
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

The User Profile Service service failed to Login user Profile error in Windows 7 Home Premium

Hi,
I recently purchased a new Dell Inspirion 1564 Laptop which had Microsoft Windows 7 Home Premium 64-bit installed.
The hardware configuration is i5 core Processor, 4GB Ram , 320GB HDD and 512MB Graphics card.
Today morning, I couldn't login as the system returned the following error after I entered the password.
"The User Profile Service service failed to login.
User Profile cannot be loaded"
I couldn't login at all as i had not created any other user account, even the face recognition didn't work.
I had to restore my pc to the previous state. I believe this happened after the installation of Windows Malicious Software Removal Tool x64 - March 2010 (KB890830) update, not immeditately though as i used the system few times after the installation of this update.
Is this a bug? I cant imagine if this happens if I am about to give a presentation, its going to be disastrous!
Any help is appreciated
Avinash

I'm getting the same issue - I'm the IT Manager at a school where every student has a laptop (fujitsu tablet T4410). This occurs to at least one new student every day. I have been unable to re-create the issue on demand, although I suspect it occurs when a temporary user profile gets created after the logon process takes too long (due to some disk activity, possibly related to windows updates or some thing). When we were creating student accounts on the machines, this would occur if we attempted to log in the newly created account before the computer had 'settled down' - it seems that there is a logon timeout, after which something stops working. If the new user's first logon happened too soon after booting, the profile would be corrupted. But this doesn't quite explain why it occurs seemingly randomly now.
My current solution is to boot into safe mode, back up the user's files, delete the account, create it again (the other suggested solutions on the internet did not work)
If you're desperate, you can log in while in safe mode, and use that to create a new account.
In any case, this is proving a very bad experience of Windows 7 for my students, and I hope to see a more useful fix for this soon.

New notebook~ "Fails to login"

We received our new Acer Notebook on Friday. We had no problems setting it up and getting online. It worked up until yesterday afternoon. When we try you login we get the following message: "The User Profile service failed to login. User profile cannot be loaded." Not sure what we are suppose to do and the user manual is very brief. Any help would be greatly appreciated. Thanks.

I've seen this before on other computers. Reboot your computer, and Press F8 as soon as the BIOS screen goes away. Select Safe Mode and let it load. On the user select screen log into the Administrator profile. It should log into windows unless the administrator profile is corrupt. But after you log into the profile, click yes on the box that pops up talking about system recovery. It will take you into the desktop from there. Go ahead and close the Help and support window that pops up.
From the desktop go into the start menu and select the control panel then into user acounts. select the account name you are having a problem with and delete it. After that, click on create new account. Once complete reboot the machine and try to log in normally.
Let us know if this helps.

Failed to login console

Hello,
It's failed to login console with ACSAdmin account. The ACSAdmin is able to login in GUI.
No idea about the reason. Anything configuration is not correct in my ACS 5.2?
Thanks,
-Alejin

Hello Alejin,
there are two types of admin users for ACS. One for the appliance and one for the application (GUI). and there idependent of each other.
if you lost the appliance admin password, you might try this.
http://www.cisco.com/en/US/products/sw/secursw/ps5338/products_installation_guide_chapter09186a0080203004.html#wp1038722
regards
alex

Locating failed wireless login attempts and which access point they're hitting

We have a cisco 5508 WLC with about 190 access points. They use Cisco Secure ACS to authenticate Microsoft Active Directory logins. We sometimes get non-normal accounts attempting to login to our wireless but are unable to figure out which access point they're hitting.
When I look at the failed attempts in our Cisco Secure ACS 5.5 Radius Authentications report, I don't see an IP address, just the MAC address of the failing device. Is their a way to configure either the WLC or the ACS box to report either the IP address or MAC address of the access point they're connecting to?

Is this something I need to set the ACS or WLC to send? When I go to Other attributes in the "Authentications - RADIUS - Today" report, this is all I'm currently seeing.
Other Attributes:
ACSVersion=acs-5.5.0.46-B.723
ConfigVersionId=3
DetailedInfo=Invalid username or password specified, Retry is allowed

Network accounts do not login in

Hi everyone,
last month our Xserve G5 with Leopard Server which controlled user accounts in our computer labs died. We replaced it with a Mac mini server (that includes Lion Server) –by the way, this is the first server that I ever setup–.During initial configuration, the server was fully updated to Lion server 10.7.3, and stablished as an OD Master. I didn't import anything from the old server, so all accounts and groups and preferences and everything have been defined from scratch.
Everything was working good until I finish the setup and try to connect from one of our Leopard client machines. I configure that machine with Directory Utility with settings from the server, and the server responds just fine, the client sets everything up automatically for authentication and contacts. Everything seems to be normal until I log out and try to connect with one of the network accounts.The account will not login, the login window just shakes and does nothing. Odd enough, the login window tells that network accounts are available (captures are in Spanish).
When I login again as a local admin account, I check Directory Utility and when I look at the LDAP configuration, in the search & maps tab of the window, I find these two red registers (UserAuthenticationData and OLCLDIFConfig). I don't know if this is related to the problem, but this is where I get stuck and don't know where else to go...
Any ideas?

I was able to activate the debug log in the Leopard client machine, but I don't know how to look from another machine via SSH... Could you explain a bit the procedure? Is it possible to try to log in as a network user and then, after failure, log in as an admin account and check the log with Console?
Today I found out that Snow Leopard clients are also not able to log in... Similar problem in Directory Utility:
This is what I found in the log for this machine (tried to log in with two different accounts):
25/04/12 20:09:17          SecurityAgent[321]          User info context values set for XXX
25/04/12 20:09:18          authorizationhost[320]          Failed to authenticate user <XXX> (tDirStatus: -14103).
25/04/12 20:09:25          SecurityAgent[321]          User info context values set for YYY
25/04/12 20:09:25          authorizationhost[320]          Failed to authenticate user <YYY> (tDirStatus: -14103).
Couldn't find much about this in Google.
I'm starting to feel really disappointed about this!
(sorry for the delay in answering, been abroad...)

Main account fails to login

Similar Messages

Maybe you are looking for