Wednesday, May 8, 2013

[SQL 2012] SSMS 2012 Restarts Itself

[SQL 2012] SSMS 2012 Restarts Itself

SSMS 2012 Restarts Itself

Posted: 08 May 2013 02:16 AM PDT

When I close SSMS 2012 it will restart. I can click the X or click File Exit; however, SSMS will restart. This happens at the end of the day when closing all programs to shutdown my workstation (I leave it up all day). I am running Windows 7 SP1 32 bit and SSMS 2012 SP1 CU2 (11.0.3339.0). Any ideas?

Does the Availability-Group (AG) Listener name need to be *precreated* in Active Directory before adding listener to AG?

Posted: 08 May 2013 01:12 AM PDT

Before running the statement below to add a listener to an Availability Group, does the listener name need to be pre-created in active directory?Or does the statement below actually [b]create [/b]the listener object in active directory?(code sample taken from [url]http://msdn.microsoft.com/en-us/library/hh213080.aspx#WinPermissions[/url]:[code="sql"]ALTER AVAILABILITY GROUP MyAg2 ADD LISTENER 'MyAg2ListenerIvP6' ( WITH IP ( ('2001:db88:f0:f00f::cf3c'),('2001:4898:e0:f213::4ce2') ) , PORT = 60173 ); GO[/code]I think it's the latter, and according to the above link, the cluster-name-object needs to have Create-Object permissions in active directory for this to work.Is my understanding correct?

SQL Server 2012 - SSIS issue

Posted: 02 Apr 2013 12:02 PM PDT

HiWe installed SQL Server 2012 SP1 on Windows 2008R2(VM) and have setup DNS aliases for our servers.I am an admin on the Windows server with SA access to the SQL server. [u]Current Issues:[b][/b][/u]I am able to connect to both Database Engine and Integration services using the Server Name.I am able to connect to the Database Engine but not to the Integration Services using the Alias.I have tried adding user explicitly to the Microsoft SQL Server Integration Services 11.0 on DCOM Config and restarted SSIS.Added DisableLoopbackCheck, modified to 1 and have rebooted the server, still the error persists. [b]Below is the error message: [u][/u][/b]Cannot connect to <AliasName>.===================================Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)------------------------------For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476------------------------------Program Location: at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request) at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server) at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()===================================Connecting to the Integration Services service on the computer "AliasName" failed with the following error: "Access is denied."By default, only administrators have access to the Integration Services service. On Windows Vista and later, the process must be running with administrative privileges in order to connect to the Integration Services service. See the help topic for information on how to configure access to the service.------------------------------For help, click: http://go.microsoft.com/fwlink/?LinkId=220763------------------------------Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server, String& serverVersion) at Microsoft.SqlServer.Dts.SmoEnum.DTSEnum.GetData(EnumResult erParent) at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData() at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci) at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request) at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)===================================Connecting to the Integration Services service on the computer "AliasName" failed with the following error: "Access is denied."By default, only administrators have access to the Integration Services service. On Windows Vista and later, the process must be running with administrative privileges in order to connect to the Integration Services service. See the help topic for information on how to configure access to the service.------------------------------Program Location: at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.GetServerInfo(String bstrMachineName, String& serverVersion) at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server, String& serverVersion)Any insight would be helpful.

Has anyone implemented SQL Server 2012 Always On for disaster recovery

Posted: 12 Apr 2013 11:31 AM PDT

Am helping a client upgrade his servers (currently SS 2005 with Windows 2003 cluster). Talked to Dell sales rep this afternoon and he had not heard of anyone implementing Always On for DR. He said all his sales for SS2012 have been for active/passive cluster. I've attended several SQL Saturday sessions and webinars on Always On, but now are worried that nobody has really implemented it in production. I don't want the client to be on the technology tip by himself, but would like to take advantage of Always On if it really works.I would appreciate it if anybody could tell me if they have implemented Always On and what pros and cons they have found.Thanks in advance,Mike Byrd

Exporting Sql 2008 SSIS packages from MSDB to Sql 2012 MSDB

Posted: 07 May 2013 09:58 PM PDT

Hi,I'm sorry if I missed the solution here somewhere but I need to export SEVERAL projects (folders) with tens of SSIS packages from Sql Server 2008 MSDB to Sql Server 2012 MSDB.Any smooth way to do this?Ville

proxy error in replication.

Posted: 07 May 2013 11:20 AM PDT

I have this setup, server A is the distributor/Subscriber and server B is the publisher, SQL agent account is different in each server and they are domain accounts. Each server has an application ID, a domain account as well, say user A for server A and User B for Server B. User A and User B are both member of Admin group of both server and both are sysadmin in SQL instances in both servers. I setup a replication using the procedure by the vendor.(they have the tool to do the setup for replication for their application. just input informations and let the tool do it(in other words, a wizard. ;-)) I used User B as log reader agent(that's the only account/ID required by the tool aside from the repldata folder of subscriber and the server names). The tool said the replication is setup properly but there's error in the replication.Date 7/05/2013 12:18:29 PMLog Job History (<<jobname>>)Step ID 2Server <<ServerA>>Job Name <<jobname>>Step Name Run agent.Duration 00:00:00Sql Severity 0Sql Message ID 0Operator Emailed Operator Net sent Operator Paged Retries Attempted 27MessageUnable to start execution of step 2 (reason: Error authenticating proxy <<UserB>>, system error: Logon failure: user not allowed to log on to this computer.)What I did was to change the credentials of the proxy(in the subscriber) to use User A instead of User B and the replication worked. I have no idea how the vendor tool setup the replication but I am guessing that the log reader agent which the one I inputted as User B are the one used by the tool to set as proxy account. but the thing is, both users are admin and sysadmin on both boxes, i wonder why i got this error. when I tried to connect via RDC using those user A to server B, i've got the error saying not allowed to use the computer. same goes with User B connecting to server A. could this be an issue? but they able to connect to the instances. both SQLs are Enterprise, build 11.0.2325can someone shed some light?:-)
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Search This Blog