Quantcast
Channel: AutoSPInstaller
Viewing all 2279 articles
Browse latest View live
↧

New Post: Exception after Step "Done applying object cache accounts to"

July 9, 2014, 6:09 am
$
0
0
Yes i mean july 7th 2014 (i will fix it in my opening post)
↧
Search

Commented Issue: Checking Index component - fail [20230]

July 9, 2014, 3:35 pm
$
0
0
Experienced a fail during a 2013 installation. Had previously installed on the same server, uninstalled SP2013 and deleted DB's. When reinstalling script failed at creating the Search Index as files from the previous installation still existed.

_System.Management.Automation.ParameterBindingException: Cannot bind parameter 'RootDirectory'
to the target. Exception setting "RootDirectory": "___New index location must be empty___" --->
System.Management.Automation.SetValueInvocationException: Exception setting "RootDirectory":
"New index location must be empty" ---> System.ArgumentException: New index location must be
empty_

Fix is probably just a simple case of checking for any existing files in the location, and if exist delete, prior to creating ??
Comments: ** Comment from web user: mcox13579 **

The work-around may not be quite that simple. I got this same error using PowerShell to create the search topology. I tried to delete the contents of the index location. I found files in that folder were in use by SharePoint so could not so easily delete them. Even when I force-cleared out the index folder, I could not get the index folder to remain empty long enough to run the New-SPEnterpriseSearchIndexComponent cmdlet, which is the line in the PowerShell that takes the -RootDirectory parameter and returns this error message.

I suspect the Search Host Controller Service got the index location from some SharePoint registry entry or DB record that got set way back in SharePoint Setup, because when running SharePoint setup on the Search server -- in the Server Type page -- I foolishly clicked the "File Location" tab and selected the index location like it says to do.

Here's how I resolved the issue:

1. From Central Administration, navigate to Services on server.
2. From the Services on Server page, use the Server: prompt in the upper right corner to select Change Server and select your search server
3. From the Services on Server page, scroll down and locate __Search Host Controller Service__ and click __Stop__
4. Go back to your Search Server and delete everything out of the folder at the Search Index location.
5. With the Search Host Controller service still stopped, re-run the PowerShell script you are using that includes the New-SPEnterpriseSearchIndexComponent command.

Interestingly, I found the Search Host Controller Service started running again automatically and I did not have to go back to Central Administration to re-start it.

↧
↧

New Post: Exception after Step "Done applying object cache accounts to"

July 11, 2014, 2:15 am
$
0
0
Most service applications were not installed. does it make sense to install these service applications by hand or should I wait for a new version of spautoinstallen?
↧

New Post: Exception after Step "Done applying object cache accounts to"

July 11, 2014, 8:50 am
$
0
0
Can you post your XML, looks like youre missing something.
↧

New Post: Exception after Step "Done applying object cache accounts to"

July 11, 2014, 8:53 am
↧
↧

Created Unassigned: missing config-OWA-2010.xml [21140]

July 11, 2014, 4:26 pm
$
0
0
Thanks for all your hard work and keeping your software so current, brilliant effort helping us out all over the world.

I've noticed in your V3 release that the config-OWA-2010.xml is missing from the install folders. I've not tried this before and don't have a copy from previous versions, can you include please?

Many thanks.
↧

Commented Unassigned: missing config-OWA-2010.xml [21140]

July 11, 2014, 5:20 pm
$
0
0
Thanks for all your hard work and keeping your software so current, brilliant effort helping us out all over the world.

I've noticed in your V3 release that the config-OWA-2010.xml is missing from the install folders. I've not tried this before and don't have a copy from previous versions, can you include please?

Many thanks.
Comments: ** Comment from web user: brianlala **

It's no longer required - automatically generated based on info you provide in the Input XML.

Cheers
Brian

↧

New Post: Exception after Step "Done applying object cache accounts to"

July 14, 2014, 1:16 am
↧
Search

New Post: Exception after Step "Done applying object cache accounts to"

July 14, 2014, 6:42 am
$
0
0
As Ivan correctly mentioned. You need to populate sitecollections nodes. Compare your XML with the original.
↧
↧

New Post: Exception after Step "Done applying object cache accounts to"

July 14, 2014, 7:12 am
$
0
0
Hi all,

i update the AutoSPInstallerFunctions.ps1 as described in https://autospinstaller.codeplex.com/workitem/21106
The error no longer occurs but now the scriptend with this error:
 - Granting rights to Metadata Service Application:
  - domain\sharepointservices...
Grant-SPObjectSecurity : The pipeline has been stopped.
At D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2386 char:43
+                     Grant-SPObjectSecurity <<<<  $metadataServiceAppSecurity -Principal $accountPrincipal -Rights "Fu
ll Access to Term Store"
    + CategoryInfo          : InvalidData: (Microsoft.Share...tObjectSecurity:SPCmdletGrantObjectSecurity) [Grant-SPOb
   jectSecurity], PipelineStoppedException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletGrantObjectSecurity

Grant-SPObjectSecurity: The argument "Rights" is not valid
↧

New Post: Exception after Step "Done applying object cache accounts to"

July 15, 2014, 7:47 am
↧

Created Unassigned: Distributed Cache starting (muli-server) [21155]

July 16, 2014, 5:28 pm
$
0
0
Hi,

I have noticed that whenever I use the script to create a multi-server farm the distributed cache service fails to start. The script returns a pass however the service does not actually start. Digging into it I have found that the windows firewall rule for ICMP incoming (under file and print sharing) must be enabled as AppFabric uses ICMP to check the state of servers before enabling the service.

Can the script be amended to enable these rules 1 for IPv4 and 1 for IPv6?
↧

Commented Unassigned: Distributed Cache starting (muli-server) [21155]

July 16, 2014, 6:00 pm
$
0
0
Hi,

I have noticed that whenever I use the script to create a multi-server farm the distributed cache service fails to start. The script returns a pass however the service does not actually start. Digging into it I have found that the windows firewall rule for ICMP incoming (under file and print sharing) must be enabled as AppFabric uses ICMP to check the state of servers before enabling the service.

Can the script be amended to enable these rules 1 for IPv4 and 1 for IPv6?
Comments: ** Comment from web user: Terafirma **

To fix this after deployment I have to run the following script on the servers it fails to start on:

$SPFarm = Get-SPFarm
$cacheClusterName = "SPDistributedCacheCluster_" + $SPFarm.Id.ToString()
$cacheClusterManager = [Microsoft.SharePoint.DistributedCaching.Utilities.SPDistributedCacheClusterInfoManager]::Local
$cacheClusterInfo = $cacheClusterManager.GetSPDistributedCacheClusterInfo($cacheClusterName);
$instanceName ="SPDistributedCacheService Name=AppFabricCachingService"
$serviceInstance = Get-SPServiceInstance | ? {($_.Service.Tostring()) -eq $instanceName -and ($_.Server.Name) -eq $env:computername}
$serviceInstance.Delete()
Add-SPDistributedCacheServiceInstance
$cacheClusterInfo.CacheHostsInfoCollection

Taken from http://techblog.rakasatria.com/

↧
↧

New Post: Error when creating central administration web application.

July 17, 2014, 6:13 am
$
0
0
Hi everyone,

When I ran autospinstaller with prerequisite files installed manually, I ran into the following problem when it was creating central administration site.

New-SPCentralAdministration : index was out of range


Then I restarted my vm and it worked again without the mentioned error. Is it because the IIS is not activated/installed?

Do I have to install IIS before installing .Net 4?

Thank you so much in advance.
↧

New Post: Installing just a Cumulative Update

July 17, 2014, 1:34 pm
$
0
0
I just completed my Farm creation using AutoSPInstaller. I got prerequisites and CU April 2014 using AutoSPSourceBuilder, and these were applied during the initial execution of AutoSPInstaller which created the farm.

I now want to install CU June 2014 - can I use AutoSPInstaller or is it best to just use the standard MS process?
Is AutoSPInstaller designed for the initial install only or can it be used to maintain the farm during its life?

Will AutoSPInstaller change any settings I may have changed manually since I last ran it - e.g. if I stopped a service to conserve resources, will it start that service back up?

Do I need to clean up my /SP/2013/Updates or my /SP/2013/SharePoint/Updates folders before running AutoSPSourceBuilder to get the "June 2014" update?

Thank you
↧
Search

New Post: Installing just a Cumulative Update

July 17, 2014, 1:46 pm
$
0
0
If you place the CU in /2013/Updates folder, I assume you could use AutoSPInstaller

If you place the CU in /2013/SharePoint/Updates folder however, you cannot use AutoSPinstaller whatsoever as native slipstreaming only works during the first install of binaries.

Hope this helps.
↧

New Post: Installing just a Cumulative Update

July 17, 2014, 1:48 pm
↧
↧

New Post: Installing just a Cumulative Update

July 17, 2014, 2:40 pm
$
0
0
Hi Joseph, thanks for your response, it was helpful.
↧

New Post: The given key was not present in the dictionary

July 18, 2014, 6:21 am
$
0
0
For

a new SharePoint 2013 with SP1 agaist SQLServer 2012 Sp1 install I am seeing:
  • Creating config database "AutoSPInstaller_Config2"...
    New-SPConfigurationDatabase : The given key was not present in the dictionary.
    At C:\dev\ps\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1651 char:13
  • New-SPConfigurationDatabase -DatabaseName "$configDB" -DatabaseServe ...
    • Registering managed account DOMAIN\SP_DANDevAppPool...
      New-SPManagedAccount : The given key was not present in the dictionary.
      At C:\dev\ps\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2076 char:17
  • New-SPManagedAccount -Credential $credAccount | Out-Null
  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Fortunately the fix is easy

http://leowu70.blogspot.co.uk/2011/06/error-new-spconfigurationdatabase-given.html


But I am a bit confused as for this client I have having to do this for
  • SP_Install
  • SP_Farm
  • SP_Services ( SQL account)
  • SP_PortalAppPool
  • SP_MySItesAppPool
----- Do I do have to do the rest?
↧

New Post: The given key was not present in the dictionary

July 18, 2014, 6:43 am
$
0
0
If you are planning to use claims/ADFS you will need to heed Steve Peschka's warning in http://blogs.technet.com/b/speschka/archive/2010/06/12/key-not-found-in-dictionary-error-when-validating-user-accounts.aspx

Otherwise, I almost certain that you:
1) Did not have to do SP_install, your installation was already running OK.
2) Have to do this for all managed accounts. So, You have to do it for the search service account if different from the ones that you listed.
3) Do not have to do this for cache read, cache write or search crawl accounts or user profile import.

You will have to test this thoroughly though.

I am familiar with some other issues with user profile sync not starting caused by Windows 2003 Domain controllers. http://blogs.msdn.com/b/yvan_duhamel/archive/2010/06/29/you-get-a-system-security-securityexception-when-you-try-to-start-the-fim-synchronization.aspx

If you are still using windows 2003, this must retire soon. It is already out of support.
↧
Viewing all 2279 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>