Hot answers tagged access-services
The actual details of your error will be in SharePoint's ULS log files. The key here is the correlation ID that has been listed out. You have to parse through the appropriate log file and filter down to log events that use that correlation ID. Then, within that group of items, there should be more detailed error messages about what happened. Where to find ...
Access Services is supported in E3 and E4 - as well as the P1 plan. In other words, yes.
Yes it is. See the Office 365 page on Access Services and this MSDN Lab. I am pretty sure they are available in the E3 and E4 plans. A quote from the Office 365 Page: Do you have valuable data that is stored in an old, unsupported database, where it’s hard to query or maintain? By moving your data to Microsoft Access 2010, and then publishing the ...
Goto control was fixed, but you cannot move a control in another web form. So you cannot modify or change the controls say in another web form that might be doing your on-line banking. So goto control should work just fine, but the code has to be executed by code INSIDE the form in question. So if this form in question is a sub form, then the code has to be ...
how far you can customize it? I would say its depend upon the requirement and skills set you have.It is very much open ended. Security level. Is that using SharePoint security or other security? Get more control over who can modify your app. SharePoint now comes with three default permissions levels–Designer, Author, and Reader. Only Designers can make ...
Is it possible that the service account has a expired password? Test the service application with a new service account and see if you get the same results.
With SharePoint 2010 you'll likely be using IIS7 which won't have SelfSSL.exe. Use makecert instead: makecert -r -pe -n 'CN=my.domain.here' -b 01/01/2000 -e 01/01/2036 -eku 184.108.40.206.220.127.116.11.1 -ss my -sr localMachine -sky exchange -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12 Then edit the https binding on the website to use the new cert.
The error "The name of the security certificate is invalid or does not match the name of the site" comes when the 'common name' in the certificate doesn't match the address you provided in browser to access the site. When you create certificate,using SelfSSl.exe, you have to specify common name(cn), for example as: selfssl.exe /T /N:cn=testsharepoint.com ...
You are confusing two things. Kerberos versus NTLM are authentication protocols. This is how the credentials are passed and verified, not the authentication itself. Claims Based Authentication can be used with either Active Directory or Forms Based Authentication (SQL, usually) users to provide a way for the user to log into the sites. I have not heard of ...
Only top voted, non community-wiki answers of a minimum length are eligible