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

Closed Unassigned: Documentation not found [21669]

$
0
0
Post about versión 3.0 not found: https://www.nothingbutsharepoint.com/?p=19204 not found
Comments: Updated URL to http://spinsiders.com/brianlala/2012/02/14/whats-in-store-for-autospinstaller-v-next/

Commented Unassigned: Script halts with SP Foundation selected [21690]

$
0
0
Script output:
```
- Script halted!
- The Product ID (PIDKey) is missing or badly formatted.
- Check the value of <PIDKey> in "AutoSPInstallerInput.xml" and try again.
```

Although the comment in XML states there is no PIDKey needed when selecting Foundation the validation is still active..

following code at line 268 in AutoSPInstallerFunctions.ps1 should fix the problem

```
$pidKey = $xmlinput.Configuration.Install.PIDKey
$sku = $xmlinput.Configuration.Install.SKU
# Do a rudimentary check on the presence and format of the product key
if ($sku -ne "Foundation" -and $pidKey -notlike "?????-?????-?????-?????-?????")
```
Comments: ** Comment from web user: brianlala **

Can you confirm that your Configuration.Install.SKU in the XML actually appears as <SKU>Foundation</SKU>?

Brian

New Post: WinRM

$
0
0
Can't get past sectoin that executes winRM:

"The WinRMclient cannot process the request. A computer policyh does not allow the delegatoin of the user credentilas to the targe computer because the computer is not trusted. "

I'm trying to load software on WFE located in differnt domain (dmz).

Any help is appreciated.

Commented Unassigned: SharePoint Designer cannot see a the workflow 2013 option when AutoSPInstaller creates the site collection [21678]

$
0
0
When I create the site collection (root web) using AutoSPInstaller, for a reason unknown to me yet, SharePoint Designer 2013 does not recognize the fact that I have a workflow manager farm registered.

Only:
1) when I delete the site collection and recreate from the user interface, then SharePoint designer recognizes that I could create 2013 Workflows for that site collection as an option.
2) or switch to another web application in the same farm that have its site collection created from central administration, then I would also be able to see the 2013 workflows option.

I will continue to update this thread when (and if) I know more,.

Thanks, Joseph.
Comments: ** Comment from web user: brianlala **

Hey Joseph, OK so unless there's something wrong with the way AutoSPInstaller uses New-SPSite (missing/bad parameter etc.), this would seem to be more of a PowerShell / cmdlet issue than one that arises purely from using AutoSPInstaller... have you tried creating a site collection using pure PowerShell?

Brian

Commented Unassigned: Script halts with SP Foundation selected [21690]

$
0
0
Script output:
```
- Script halted!
- The Product ID (PIDKey) is missing or badly formatted.
- Check the value of <PIDKey> in "AutoSPInstallerInput.xml" and try again.
```

Although the comment in XML states there is no PIDKey needed when selecting Foundation the validation is still active..

following code at line 268 in AutoSPInstallerFunctions.ps1 should fix the problem

```
$pidKey = $xmlinput.Configuration.Install.PIDKey
$sku = $xmlinput.Configuration.Install.SKU
# Do a rudimentary check on the presence and format of the product key
if ($sku -ne "Foundation" -and $pidKey -notlike "?????-?????-?????-?????-?????")
```
Comments: ** Comment from web user: brianlala **

Actually I see what you mean now. As Foundation support is still experimental, I have only tested scenarios where the config xml file already exists and haven't implemented the functionality to automatically generate the config xml file as the script normally does with Enterprise or Standard. I will be fixing this in the near future.

Brian

Edited Issue: Script halts with SP Foundation selected [21690]

$
0
0
Script output:
```
- Script halted!
- The Product ID (PIDKey) is missing or badly formatted.
- Check the value of <PIDKey> in "AutoSPInstallerInput.xml" and try again.
```

Although the comment in XML states there is no PIDKey needed when selecting Foundation the validation is still active..

following code at line 268 in AutoSPInstallerFunctions.ps1 should fix the problem

```
$pidKey = $xmlinput.Configuration.Install.PIDKey
$sku = $xmlinput.Configuration.Install.SKU
# Do a rudimentary check on the presence and format of the product key
if ($sku -ne "Foundation" -and $pidKey -notlike "?????-?????-?????-?????-?????")
```

New Post: sqlncli.msi , the “SQL Native Client” version makes the difference for User Profile Service.

$
0
0
Thank you all!

I ran into the same issue when I loaded SQL Management Studio 2012 from the SQL media ISO on a SP front end. Guess I should have started UPS before that. All is good now thanks to this posting. Appreciate the help!

"UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS post database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: ERR_CONFIG_DB"

Created Unassigned: AutoSPInstallerInput.xml [21708]

$
0
0
There is a missing "/" in the following:

<AdminComponent Provision="localhost" >

Commented Unassigned: AutoSPInstallerInput.xml v3.98 [21708]

$
0
0
There is a missing "/" in the following:

<AdminComponent Provision="localhost" >
Comments: ** Comment from web user: IvanJosipovic **

This Element has a child Node, and shouldn't be closed off there.

<AdminComponent Provision="localhost">
<ApplicationPool Name="SharePoint Search Application Pool" />
</AdminComponent>

Commented Unassigned: AutoSPInstallerInput.xml v3.98 [21708]

$
0
0
There is a missing "/" in the following:

<AdminComponent Provision="localhost" >
Comments: ** Comment from web user: mcnga1 **

You are correct!

I apologize for the false alarm. I was migrating my v3.96 XML to v3.98 and, in haste, made an incorrect observation.

Created Unassigned: Script Continues to reload on SP2010 / SVR2012 [21709]

$
0
0
This week I have had the occasion to use this script to install SP2010 on Svr2012 and as I got the point where the script needed to reload in PowerShell Version 2 to create the Farm it continued to do so. Continually getting to the same point in the script and reloading again and again, resulting in a cascade of sessions that didn't get anywhere.

It turns out that Powershell was only ever loading the latest version regardless of correct use of the -Version 2 switch. This was evidenced when the copyright notice came up and showed 2013 and, when extracting information from $psversiontable showed Version 4. This was caused by the following entries in the registry being set to 1.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\OnlyUseLatestCLR
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\OnlyUseLatestCLR

Updating to 0 immediately resulted in PowerShell being able to load into Version 2 correctly. Not sure if it would be worth putting those checks/updates in the installer script.

Reviewed: AutoSPInstaller for SharePoint 2010 + 2013 (Feb 04, 2015)

$
0
0
Rated 5 Stars (out of 5) - One of the best work on SharePoint.

Edited Task: Script Continues to reload on SP2010 / SVR2012 [21709]

$
0
0
This week I have had the occasion to use this script to install SP2010 on Svr2012 and as I got the point where the script needed to reload in PowerShell Version 2 to create the Farm it continued to do so. Continually getting to the same point in the script and reloading again and again, resulting in a cascade of sessions that didn't get anywhere.

It turns out that Powershell was only ever loading the latest version regardless of correct use of the -Version 2 switch. This was evidenced when the copyright notice came up and showed 2013 and, when extracting information from $psversiontable showed Version 4. This was caused by the following entries in the registry being set to 1.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\OnlyUseLatestCLR
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\OnlyUseLatestCLR

Updating to 0 immediately resulted in PowerShell being able to load into Version 2 correctly. Not sure if it would be worth putting those checks/updates in the installer script.
Comments: ** Comment from web user: brianlala **

I'll activate the issue. Any idea how your registry got set this way in the first place?

Brian

Closed Unassigned: AutoSPInstallerInput.xml v3.98 [21708]

$
0
0
There is a missing "/" in the following:

<AdminComponent Provision="localhost" >

Commented Task: Script Continues to reload on SP2010 / SVR2012 [21709]

$
0
0
This week I have had the occasion to use this script to install SP2010 on Svr2012 and as I got the point where the script needed to reload in PowerShell Version 2 to create the Farm it continued to do so. Continually getting to the same point in the script and reloading again and again, resulting in a cascade of sessions that didn't get anywhere.

It turns out that Powershell was only ever loading the latest version regardless of correct use of the -Version 2 switch. This was evidenced when the copyright notice came up and showed 2013 and, when extracting information from $psversiontable showed Version 4. This was caused by the following entries in the registry being set to 1.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\OnlyUseLatestCLR
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\OnlyUseLatestCLR

Updating to 0 immediately resulted in PowerShell being able to load into Version 2 correctly. Not sure if it would be worth putting those checks/updates in the installer script.
Comments: ** Comment from web user: Craig_Vallis **

I am trying to find out. These servers were new build provided by my client's Managed Service Provider.

I am not sure of the scale of the problem and I found these Registry Keys more by luck than anything else so this could also just be used to document the potential problem if anybody else runs into it.

Thanks for a fantastic script.


Created Unassigned: Project Server 2013 SP1 [21715]

$
0
0
Hi Brian,

the Project Server 2013 SP1 package "projectserversp2013-kb2817434-fullfile-x64-en-us.exe", used in used in AutoSPInstallerFunctions.ps1, was substituted by the new release "projectserversp2013-kb2880553-fullfile-x64-en-us.exe".

http://support.microsoft.com/kb/2880553

Regards
Matthias

New Post: Errror "There are other servers specified as farm members in"

$
0
0
I got this error when trying to use a poorly adapted config.xml file, the block of xml with services in it had "true" instead of "localhost", once I changed it over to localhost it worked fine:
<Services>
            <SandboxedCodeService Start="false" />
            <!-- The UpdateAccount attribute will set the Claims To Windows Token Service (C2WTS) to run under an account other than the default Local System (the general spservice account), and thus avoid a Health Analyzer warning. However it might break things like PowerPivot and Excel Services so best bet is to leave it "false". -->
            <ClaimsToWindowsTokenService Start="false" UpdateAccount="false" />
            <SMTP Install="false" />
            <OutgoingEmail Configure="true">
                <SMTPServer></SMTPServer>
                <EmailAddress></EmailAddress>
                <ReplyToEmail></ReplyToEmail>
            </OutgoingEmail>
            <IncomingEmail Start="localhost" /> <!-- These had "true" values -->
            <!-- DistributedCache (SharePoint 2013 only) - Start should never be set to "false", only either "true" for ALL servers (usually not recommended either), or a comma-delimited list of specific servers (maximum 4 cache host servers per farm). -->
            <DistributedCache Start="localhost" /> <!-- These had "true" values -->
            <!-- As a general rule WorkflowTimer - Start should never be set to "false", only either "true" for all servers, or a comma-delimited list of specific servers.
                 Normally you would specify the same servers to provision WorkflowTimer as you would FoundationWebApplication below. -->
            <WorkflowTimer Start="localhost" /> <!-- These had "true" values -->
            <!-- As a general rule FoundationWebApplication - Start should never be set to "false", only either "true" for all servers, or a comma-delimited list of specific WFE servers.
                 *Note* if you want to remotely install dedicated WFEs in your farm (i.e. RemoteInstall Enable="true") you should name the servers here, in a comma separated list - e.g. Start="WFE1,WFE2,WFEx" -->
            <FoundationWebApplication Start="localhost" /> <!-- These had "true" values -->
        </Services>

New Post: Problem with Script....

$
0
0
Hallo all

Thank you for the tipp! I had the same problem. It crashed everytime at "Provisioning Search" - "Searching for stuck Search Host controller Service".
Then I found this link and added a Tray-Catch to the function AddResourcesLink:
# ====================================================================================
Function AddResourcesLink([string]$title,[string]$url)
{
    $centraladminapp = Get-SPWebApplication -IncludeCentralAdministration | ? {$_.IsAdministrationWebApplication}
    $centraladminurl = $centraladminapp.Url
    $centraladmin = (Get-SPSite $centraladminurl)

    Try
    {
        $item = $centraladmin.RootWeb.Lists["Resources"].Items | Where { $_["URL"] -match ".*, $title" }
        If ($item -eq $null )
        {
            $item = $centraladmin.RootWeb.Lists["Resources"].Items.Add();
        }

        $url = $centraladminurl + $url + ", $title";
        $item["URL"] = $url;
        $item.Update();
    }
    Catch
    {
        # Modified by vii 2015-02-13
        Write-Host -ForegroundColor Yellow " Error in Function AddResourcesLink: param title: ($title), param url: ($url)"
    }
}
Know I get the following output:
  - Checking for stuck Search Host Controller Service (known issue)...
 Error in Function AddResourcesLink: param title: (Search Service Application), param url: (searchadministration.aspx?appid=a08e8fd7-b8d5-469e-84e2-7a136b4a0b11)
regards

Vii

New Post: WSMANCredSSP

$
0
0
Script crashes when executing WSManCredSSP. I have set all the variables I know of through GPOs, but I'm missing something>

New Post: Install of SP2013 failing...

$
0
0
csyvenky,

How or where can we get the Install bits for SharePoint 2013 with SP1? I have access to install bits of sharepoint from MSDN, and i can also download SP1 for SharePoint but i am unaware of where to get a combined bits?

Can you help?

Matt

----------------------------- UPDATE ---------------
i did find them on MDSN

THank you Cory for explaining, although it did take me a few times re-reading it to understand what you meant.
Viewing all 2279 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>