..and sysadmin on the SQL server

On Fri, Nov 28, 2014 at 5:41 PM, Paul Winstanley <[email protected]>
wrote:

> Is the site server a local admin?
>
> On Fri, Nov 28, 2014 at 4:15 PM, Suzzi Williams <[email protected]>
> wrote:
>
>> Paul
>>
>> Yes, restarted the services and rebooted the server, my account is local
>> admin and sysadmin and the sccm server is local admin and sysadmin
>>
>> Suz x
>>
>> On Fri, Nov 28, 2014 at 4:09 PM, Paul Winstanley <[email protected]>
>> wrote:
>>
>>> Did you restart sql services after setting the ports on the tcp config.
>>> Is your account a sysadmin in the sql server as well as local admin.
>>>
>>>
>>>
>>> On 28 Nov 2014, at 15:16, Suzzi Williams <[email protected]>
>>> wrote:
>>>
>>> Paul.
>>>
>>> Yes, collation is correct, and the sql services are using a domain
>>> account
>>>
>>> On Fri, Nov 28, 2014 at 3:13 PM, Paul Winstanley <[email protected]>
>>> wrote:
>>>
>>>> Have you set the collation correctly? SQL_Latin1_General_CP1_CI_AS
>>>>
>>>> On Fri, Nov 28, 2014 at 2:58 PM, Suzzi Williams <
>>>> [email protected]> wrote:
>>>>
>>>>> Paul
>>>>>
>>>>> It is SQL 2012 SP1
>>>>>
>>>>> Andrew
>>>>>
>>>>> Yes dynamic set to blank and 1433 on all IPs
>>>>>
>>>>> On Fri, Nov 28, 2014 at 2:43 PM, Andrew Craig <
>>>>> [email protected]> wrote:
>>>>>
>>>>>>  Hi Suzzi,
>>>>>>
>>>>>>
>>>>>>
>>>>>> Did you set dynamic to blank and 1433 on all IPs not just the IPAll?
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From:* [email protected] [mailto:
>>>>>> [email protected]] *On Behalf Of *Suzzi Williams
>>>>>> *Sent:* 28 November 2014 15:32
>>>>>> *To:* [email protected]
>>>>>> *Subject:* Re: [mssms] Install and remote SQL
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hey Paul
>>>>>>
>>>>>>
>>>>>>
>>>>>> Port set to 1433 and I can telnet to it and SQL is set to allow
>>>>>> remote connections. I will check the service pack version now
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Nov 28, 2014 at 2:23 PM, Paul Winstanley <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>  Have you set to run TCP on port 1433 - can you telnet to the server
>>>>>> on that port? Have you set the SQL server properties to allow remote
>>>>>> connections?  What version of SQL 2012? Must be CU2 for non SP or SP1 no
>>>>>> min CU.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Nov 28, 2014 at 2:17 PM, Suzzi Williams <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>  Arghh
>>>>>>
>>>>>>
>>>>>>
>>>>>> No, what wasn't it. Still the same error. Any one have any ideas?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Suz xx
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Nov 28, 2014 at 1:34 PM, Suzzi Williams <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>  I have fixed it, yay
>>>>>>
>>>>>>
>>>>>>
>>>>>> It was dynamic port settings
>>>>>>
>>>>>>
>>>>>>
>>>>>> Suz xx
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Nov 28, 2014 at 12:51 PM, Suzzi Williams <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>   I need your help again as this is really doing my head in.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I am installing SCCM 2012 with a remote SQL 2012 server.
>>>>>>
>>>>>>
>>>>>>
>>>>>> The account I am using has local admin rights on the remote SQL
>>>>>> server and full access to the SQL instance.
>>>>>>
>>>>>>
>>>>>>
>>>>>> But I am getting the following error
>>>>>>
>>>>>>
>>>>>>
>>>>>> Setup is unable to connect to SQL Server with connection information
>>>>>> provided. Verify the following:
>>>>>> The SQL Server and instance names are entered correctly
>>>>>> The specified SQL Server instance is not configured to use dynamic
>>>>>> ports
>>>>>> If a firewall is enable on the SQL Server, inbound rules exist to
>>>>>> allow connections to the correct ports
>>>>>> The account used to run Setup has permissions to connect to the
>>>>>> specified SQL Server instances
>>>>>>
>>>>>>
>>>>>>
>>>>>> I have disable all the firewalls, I can connect to the SQL server and
>>>>>> instance with management studio.
>>>>>>
>>>>>>
>>>>>>
>>>>>> The error appears very quickly and there is nothing in the SQL server
>>>>>> logs about a failed login.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Please help I have run out of ideas
>>>>>>
>>>>>>
>>>>>>
>>>>>> Suz xx
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>


Reply via email to