Personally I would stick with feb cu. Is there something specific in July that u need?
Regards, .\jEy Jey Srikantha (j...@jeylabs.com.au) +61(0)400 846 996 Director of Consulting, Technology and Innovation jEyLaBs – SharePoint Workflow Experts (www.jeylabs.com.au) Melbourne, Australia jeylabsblog.com If you think that you have received this e-mail message in error, please delete it and notify the sender. All rights reserved by jEyLaBs pty ltd (ACN 135 541 598). jEyLaBs or the sender is not responsible for viruses, or for delays, errors or interception in transmission. Please consider our environment before printing. On 21/08/2012, at 14:57, Marko Salonen <marko.salo...@moretonbay.qld.gov.au> wrote: > Working through this, once I have installed the latest CU. Anyone had any > issues with the July 2012 CU? > > Regards, > > Marko > > -- > Marko Salonen > Senior Applications Analyst > Moreton Bay Regional Council > 220 Gympie Road, Strathpine Q 4500 > P 07 3480 6531 > F 07 5433 2188 > www.moretonbay.qld.gov.au > > From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf > Of Ajay > Sent: Tuesday, 21 August 2012 12:27 PM > To: ozMOSS > Subject: Re: ForeFron Identity error after installing using AutoSPInstaller > > I have not seen this before.. but setting the profile service is a pain. > I was able to successfully get the service and sync running on SharePoint > 2013 using the following highly recommended article. > > http://www.harbar.net/articles/sp2010ups.aspx > > And yes ensure to be patches noted below.. > > > > On Tue, Aug 21, 2012 at 2:24 PM, Sezai Komur <sharepointse...@gmail.com> > wrote: > Marko, > > Have a detailed read of the following and compare to how you're setting this > up: > http://technet.microsoft.com/en-us/library/ee721049.aspx > http://www.harbar.net/articles/sp2010ups.aspx > http://www.harbar.net/articles/sp2010ups2.aspx > There's a lot of fixes on this post SP1 + June 2011 CU refresh, ensure you're > patched up well, try a more recent CU. > > Regards, > > Sezai. > On Tue, Aug 21, 2012 at 10:06 AM, Marko Salonen > <marko.salo...@moretonbay.qld.gov.au> wrote: > Hi > > I am still trying get the User Profile Service to run after using > AutoSPInstaller. > > The Forefront Identity Manager Service cannot connect to the SQL Database > Server. The SQL Server could not be contacted. The connection failure may be > due to a network failure, firewall misconfiguration, or other connection > issue. Additionally, the SQL Server connection information could be > configured incorrectly. Verify that the SQL Server is reachable from the > Forefront Identity Manager Service computer. Ensure that SQL Server is > running, that the network connection is active, and that the firewall is > configured properly. Last, verify the connection information has been > configured properly. This configuration is stored in the Windows Registry. > > I have opened 1433 port for SQL. > > I have created an ODBC connection with the account in question to verify > access. > > The Account complies with > - It must have domain user account permissions. > - It must be a member of the local administrators group on each server in the > SharePoint Server 2010 farm, excluding SQL Server and the Simple Mail > Transfer Protocol (SMTP) server. > - This account must have access to the SharePoint Server 2010 databases. > - If you use any Windows PowerShell operations that affect a database, the > setup user administrator account must be a member of the db_owner role. > - This account must be assigned to the securityadmin and dbcreator SQL Server > security roles during setup and configuration. > > For the life of me I can’t figure out why this worked using the Wizard to > install but not when using AutoSPInstaller. > > > > MORETON BAY REGIONAL COUNCIL (MBRC) PRIVILEGED PRIVATE AND CONFIDENTIAL - The > information contained in this e-mail and any attachments is confidential and > may attract legal privilege. It is only intended for the named recipient/s. > If you are not a named recipient any use of this information including > copying, distribution and publication is prohibited. Confidentiality and > legal privilege are not waived or lost as a result of mistaken or erroneous > delivery. If you are not a named recipient, please delete all copies > immediately and contact the sender to advise of the error. > > It is recommended that you scan this email and any attachment before opening. > MBRC does not accept any responsibility or liability for loss or damage > arising directly or indirectly from opening this email, opening any > attachments or any communication errors. > > The views expressed in this email and any attachments are the personal views > of the sender unless otherwise stated. > > > _______________________________________________ > ozmoss mailing list > ozmoss@ozmoss.com > http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss > > > > _______________________________________________ > ozmoss mailing list > ozmoss@ozmoss.com > http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss > > > _______________________________________________ > ozmoss mailing list > ozmoss@ozmoss.com > http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
_______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
