Comments for Ben Miller's World http://dbaduck.com My musings, personal and technological Sat, 05 Nov 2011 21:34:22 +0000 hourly 1 http://wordpress.com/ Comment on Working with SSIS in SQL Server 2005 by eshop http://dbaduck.com/2007/08/20/working-with-ssis-in-sql-server-2005/#comment-130 Sat, 05 Nov 2011 21:34:22 +0000 http://dbaduck.com/2007/08/20/working-with-ssis-in-sql-server-2005/#comment-130 Youre completely correct with this one…

]]> Comment on Verified SQL 2005 Cluster bug… by Denver Microsoft Training http://dbaduck.com/2007/07/23/verified-sql-2005-cluster-bug/#comment-125 Fri, 24 Jun 2011 01:59:03 +0000 http://dbaduck.com/2007/07/23/verified-sql-2005-cluster-bug/#comment-125 I think this bug has already been resolved.

]]> Comment on An honor to be among the SQL Server MVPs by rahul kumar ghosh http://dbaduck.com/2011/01/01/an-honor-to-be-among-the-sql-server-mvps/#comment-124 Fri, 17 Jun 2011 16:06:21 +0000 https://benmiller.wordpress.com/2011/01/01/an-honor-to-be-among-the-sql-server-mvps/#comment-124 hi..
congo!!!!! man MVP great..
I am MCITP-DBA in sql 2005, even now i want to be MVP in SQL but how to do that can you please guide me how to do that, i am just waiting for your valuable replie……

]]> Comment on Error in SQL (Error: 17806, Error: 18452) SSPI Problem by Nery R. Gonzalez http://dbaduck.com/2007/08/31/error-in-sql-error-17806-error-18452-sspi-problem/#comment-91 Wed, 10 Feb 2010 19:32:34 +0000 http://dbaduck.com/2007/08/31/error-in-sql-error-17806-error-18452-sspi-problem/#comment-91 I had the same problem and tried almost all the tips in this thread and others around the Internet. However, none of them were useful for me. In my development environment I had been using a connection string which used a DNS name (Host A record, as a matter of fact) pointing to the IP of the server where SQL 2005 is installed.

After trying several things, I finally went to the web.config and changed the connection string to the server name. After this, I got another message: Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’. [CLIENT: ]

I had seen another article saying to give this user access to the data base under User Mappings and after that all worked like a charm.

Hope this is helpful for anyone.

]]> Comment on Working with SSIS in SQL Server 2005 by Mahendra http://dbaduck.com/2007/08/20/working-with-ssis-in-sql-server-2005/#comment-90 Tue, 22 Dec 2009 09:13:36 +0000 http://dbaduck.com/2007/08/20/working-with-ssis-in-sql-server-2005/#comment-90 Good Article

]]> Comment on Error in SQL (Error: 17806, Error: 18452) SSPI Problem by Leon T http://dbaduck.com/2007/08/31/error-in-sql-error-17806-error-18452-sspi-problem/#comment-80 Tue, 19 May 2009 08:34:24 +0000 http://dbaduck.com/2007/08/31/error-in-sql-error-17806-error-18452-sspi-problem/#comment-80 Hi,

I found that this error was caused by users who’s password had expired and had decided not to change it. Although they remained logged in and were able to operate on the network. When connecting from one SQL server to the next, kereberos was unable to pass their authentication details.

]]> Comment on Working with SSIS in SQL Server 2005 by Josef http://dbaduck.com/2007/08/20/working-with-ssis-in-sql-server-2005/#comment-79 Mon, 30 Mar 2009 04:08:55 +0000 http://dbaduck.com/2007/08/20/working-with-ssis-in-sql-server-2005/#comment-79 Your article helped me get a few steps further but now i’m stuck again. Package runs ok. security is server storage but when scheduled job runs it complains about not finding the wsdl file for my web service.

Started: 1:41:24 PM Error: 2009-03-30 13:41:41.05 Code: 0xC002F304 Source: Web Service Task 1 Web Service Task Description: An error occurred with the following error message: “Microsoft.SqlServer.Dts.Tasks.WebServiceTask.WebserviceTaskException: The input Web Services Description Language (WSDL) file is not valid. at Microsoft.SqlServer.Dts.Tasks.WebServiceTask.WebServiceTaskUtil..ctor(Object connection, String downloadedWSDL) at Microsoft.SqlServer.Dts.Tasks.WebServiceTask.WebServiceTask.executeThread()”. End Error DTExec: The package execution returned DTSER_SUCCESS (0). Started: 1:41:24 PM Finished: 1:41:41 PM Elapsed: 16.391 seconds. The package executed successfully. The step succeeded.

Running the package directly does not cause a problem with the wsdl file. I think the job can’t find it but don’t understandy why?

Anyone run into this before ?

]]> Comment on Working with SSIS in SQL Server 2005 by Ron http://dbaduck.com/2007/08/20/working-with-ssis-in-sql-server-2005/#comment-78 Wed, 18 Mar 2009 23:31:47 +0000 http://dbaduck.com/2007/08/20/working-with-ssis-in-sql-server-2005/#comment-78 Stupid greyed-out boxes that don’t look like they’re doing anything. I guess some MS departments think they’re too good to hire a decent UI to point these things out to them. But yeah, I spent a couple hours trying stuff, looking online for answers, and finally found your blog. I had done everything EXCEPT clicking on that stupid button to specify the protection level when importing. Funny MS SQL devs…very funny.

]]> Comment on Working with SSIS in SQL Server 2005 by Mike http://dbaduck.com/2007/08/20/working-with-ssis-in-sql-server-2005/#comment-73 Fri, 19 Dec 2008 20:05:56 +0000 http://dbaduck.com/2007/08/20/working-with-ssis-in-sql-server-2005/#comment-73 I’ve been troubleshooting the same issue for the past day. I was on the right track, but this post saved me a few hours and gave me the pieces of the puzzle I was still missing. Thanks!

]]> Comment on Working with SSIS in SQL Server 2005 by swetha http://dbaduck.com/2007/08/20/working-with-ssis-in-sql-server-2005/#comment-72 Thu, 13 Nov 2008 10:16:50 +0000 http://dbaduck.com/2007/08/20/working-with-ssis-in-sql-server-2005/#comment-72 I resovled my problem for which i was struggling from two days with this article .. Good one.:-) Really helpful

]]>