Re: ForeFron Identity error after installing using AutoSPInstaller

2012-08-23 Thread Web Admin
If anyone ever gets this sorted out please let me know. I still have only 5
profiles imported despite selecting our AD root.

And when attempting to create Audiences, the *Select Security Group or
Distribution List* is displaying SharePoint webs!!

[image: Inline images 1]

On 23 August 2012 23:41, Prashanth Thiyagalingam
wrote:

>  These are related services/service applications and they are not
> mandatory for the creation of UPS, they are required if you want make use
> of the full social computing features of SharePoint 2010.
> http://technet.microsoft.com/en-us/library/ee662538.aspx#related
>
> For debugging UP Synchronisation issues I found FIM Synchronisation
> Service Manager tool very useful, its in
> *C:\Program Files\Microsoft Office Servers\14.0\Synchronization
> Service\UIShell\miisclient.exe *
> **
> --
> From: akhanna...@gmail.com
> Date: Thu, 23 Aug 2012 20:31:42 +1200
>
> Subject: Re: ForeFron Identity error after installing using AutoSPInstaller
> To: ozmoss@ozmoss.com
>
>
> User Profile Services is dependent on
>
> - BCS
> - Managed metadata services
> - Subscription settings services
>
>
>
> On Thu, Aug 23, 2012 at 8:20 PM, Marko Salonen <
> marko.salo...@moretonbay.qld.gov.au> wrote:
>
>  Hi
>
> ** **
>
> I have followed that to the letter, and I still get the unexpected error
> when trying manage the UPS.
>
> ** **
>
> What I am doing now is manually configuring all the service (a good
> learning exercise I suppose) and I was wondering if anyone happens to have
> a list of services that should be running before I try to configure the UPS?
> 
>
> ** **
>
> Cheers guys!
>
> ** **
>
> Regards,
>
> ** **
>
> Marko
>
> ** **
>
> ** **
>
> *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 
> 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_owne

RE: ForeFron Identity error after installing using AutoSPInstaller

2012-08-23 Thread Prashanth Thiyagalingam

These are related services/service applications and they are not mandatory for 
the creation of UPS, they are required if you want make use of the full social 
computing features of SharePoint 
2010.http://technet.microsoft.com/en-us/library/ee662538.aspx#related
 For debugging UP Synchronisation issues I found FIM Synchronisation Service 
Manager tool very useful, its inC:\Program Files\Microsoft Office 
Servers\14.0\Synchronization Service\UIShell\miisclient.exe  From: 
akhanna...@gmail.com
Date: Thu, 23 Aug 2012 20:31:42 +1200
Subject: Re: ForeFron Identity error after installing using AutoSPInstaller
To: ozmoss@ozmoss.com

User Profile Services is dependent on

- BCS
- Managed metadata services
- Subscription settings services



On Thu, Aug 23, 2012 at 8:20 PM, Marko Salonen 
 wrote:










Hi
 
I have followed that to the letter, and I still get the unexpected error when 
trying manage the UPS.


 
What I am doing now is manually configuring all the service (a good learning 
exercise I suppose) and I was wondering if anyone happens to have a list of 
services
 that should be running before I try to configure the UPS?
 
Cheers guys!
 
Regards,
 
Marko
 
 
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  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 
 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/

Re: ForeFron Identity error after installing using AutoSPInstaller

2012-08-23 Thread Maxine Harwood
If you get this working, please share the  solution... Ups drives me mad and I 
still don't have mine running perfectly!

Ya
Max. 

Sent from Max's iPhone 

On 23/08/2012, at 6:20 PM, Marko Salonen  
wrote:

> Hi
>  
> I have followed that to the letter, and I still get the unexpected error when 
> trying manage the UPS.
>  
> What I am doing now is manually configuring all the service (a good learning 
> exercise I suppose) and I was wondering if anyone happens to have a list of 
> services that should be running before I try to configure the UPS?
>  
> Cheers guys!
>  
> Regards,
>  
> Marko
>  
>  
> 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  
> 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 
>  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


Re: ForeFron Identity error after installing using AutoSPInstaller

2012-08-23 Thread Ajay
User Profile Services is dependent on

- BCS
- Managed metadata services
- Subscription settings services



On Thu, Aug 23, 2012 at 8:20 PM, Marko Salonen <
marko.salo...@moretonbay.qld.gov.au> wrote:

>  Hi
>
> ** **
>
> I have followed that to the letter, and I still get the unexpected error
> when trying manage the UPS.
>
> ** **
>
> What I am doing now is manually configuring all the service (a good
> learning exercise I suppose) and I was wondering if anyone happens to have
> a list of services that should be running before I try to configure the UPS?
> 
>
> ** **
>
> Cheers guys!
>
> ** **
>
> Regards,
>
> ** **
>
> Marko
>
> ** **
>
> ** **
>
> *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 
> 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 liab

RE: ForeFron Identity error after installing using AutoSPInstaller

2012-08-23 Thread Marko Salonen
Hi

I have followed that to the letter, and I still get the unexpected error when 
trying manage the UPS.

What I am doing now is manually configuring all the service (a good learning 
exercise I suppose) and I was wondering if anyone happens to have a list of 
services that should be running before I try to configure the UPS?

Cheers guys!

Regards,

Marko


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 
mailto: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 
mailto: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<mailto:ozmoss@ozmoss.com>
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


___
ozmoss mailing list
ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


Re: ForeFron Identity error after installing using AutoSPInstaller

2012-08-21 Thread Jey Srikantha (GMail)

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  
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  
> 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 
>  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 
> attachment

RE: ForeFron Identity error after installing using AutoSPInstaller

2012-08-20 Thread Marko Salonen
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<http://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 
mailto: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 
mailto: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<mailto:ozmoss@ozmoss.com>
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


___
ozmoss mailing list
ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: ForeFron Identity error after installing using AutoSPInstaller

2012-08-20 Thread Roger Carran

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Chris Grist
Sent: Tuesday, 21 August 2012 1:46 PM
To: ozMOSS
Subject: RE: ForeFron Identity error after installing using AutoSPInstaller

Never start the FIM services manually.. (+1)

From: ozmoss-boun...@ozmoss.com<mailto:ozmoss-boun...@ozmoss.com> 
[mailto:ozmoss-boun...@ozmoss.com]<mailto:[mailto:ozmoss-boun...@ozmoss.com]> 
On Behalf Of Prashanth Thiyagalingam
Sent: Tuesday, 21 August 2012 12:37 PM
To: ozMOSS
Cc: ozMOSS
Subject: Re: ForeFron Identity error after installing using AutoSPInstaller

Check the FIM services are running else manually start them manually in the 
windows services and the try user profile and sync
Cheers,
Prashanth

Sent from my iPhone

On Aug 21, 2012, at 10:07 AM, "Marko Salonen" 
mailto: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<mailto:ozmoss@ozmoss.com>
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

___
This message is intended only for the use of the addressee.
This email and any attachments are confidential and may
contain legally privileged information or copyright material.

If you are not the intended recipient, you are hereby notified that any use or
dissemination of this communication is strictly prohibited. If you received
this e-mail in error, please notify us immediately by telephone on +61 8 8338
2833 or by return email and delete the original message. It is important to
check for viruses and defects before opening or using attachments. Beach Energy
Limited accepts no liability for any damage caused by this email or its 
attachments due to viruses, interference, interception, corruption or
unauthorised access. Thank you.

Please consider the environment before printing this email.
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: ForeFron Identity error after installing using AutoSPInstaller

2012-08-20 Thread Chris Grist
Never start the FIM services manually..

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Prashanth Thiyagalingam
Sent: Tuesday, 21 August 2012 12:37 PM
To: ozMOSS
Cc: ozMOSS
Subject: Re: ForeFron Identity error after installing using AutoSPInstaller

Check the FIM services are running else manually start them manually in the 
windows services and the try user profile and sync
Cheers,
Prashanth

Sent from my iPhone

On Aug 21, 2012, at 10:07 AM, "Marko Salonen" 
mailto: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<mailto:ozmoss@ozmoss.com>
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

___
This message is intended only for the use of the addressee. 
This email and any attachments are confidential and may 
contain legally privileged information or copyright material.

If you are not the intended recipient, you are hereby notified that any use or
dissemination of this communication is strictly prohibited. If you received
this e-mail in error, please notify us immediately by telephone on +61 8 8338
2833 or by return email and delete the original message. It is important to 
check for viruses and defects before opening or using attachments. Beach Energy
Limited accepts no liability for any damage caused by this email or its 
attachments due to viruses, interference, interception, corruption or
 unauthorised access. Thank you. 

Please consider the environment before printing this email.
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


Re: ForeFron Identity error after installing using AutoSPInstaller

2012-08-20 Thread Prashanth Thiyagalingam
Check the FIM services are running else manually start them manually in the 
windows services and the try user profile and sync

Cheers,
Prashanth

Sent from my iPhone

On Aug 21, 2012, at 10:07 AM, "Marko Salonen" 
 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


Re: ForeFron Identity error after installing using AutoSPInstaller

2012-08-20 Thread Ajay
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 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


Re: ForeFron Identity error after installing using AutoSPInstaller

2012-08-20 Thread Sezai Komur
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