Showing posts with label old. Show all posts
Showing posts with label old. Show all posts

Thursday, March 22, 2012

couldn't rename or delete maintenance plan in Management Studio

Hi,
I tried to rename and delete one old maintenance plan which is created by
other DBA and before the machine was renamed. But, I kept getting the
following error. I can rename and delete the maintenance plan I created.
An error has occurred while establishing a connection to the server. When
connecting to SQL server 2005, this failure may be cuased by the fact that
under the default settinfs SQL server does not allow remote connections
(provider: Named Pipes providers, error: 40 - could not open a connection to
SQL server) (Microsoft SQL server, Error: 53)
Shared Memory, TCP and Named Piples are all enabled.
Please advise.
Best Regards,
Lynn
I think the problem is that the maintenance plan use the Local Server
Connection which still point to the old machine name. (I couldn't move this
connection or modify the server name for this connection at all). I add
another connection, but I still couldn't delete this maintenance plan.
Please advise.
Best Regards,
Lynn
"Lynn" wrote:

> Hi,
> I tried to rename and delete one old maintenance plan which is created by
> other DBA and before the machine was renamed. But, I kept getting the
> following error. I can rename and delete the maintenance plan I created.
> An error has occurred while establishing a connection to the server. When
> connecting to SQL server 2005, this failure may be cuased by the fact that
> under the default settinfs SQL server does not allow remote connections
> (provider: Named Pipes providers, error: 40 - could not open a connection to
> SQL server) (Microsoft SQL server, Error: 53)
> Shared Memory, TCP and Named Piples are all enabled.
> Please advise.
> --
> Best Regards,
> Lynn
|||I've been pounding my head with a similar problem. A Server was renamed and
now I can't do anything with the plan.
Any more thoughts?
"Lynn" wrote:
[vbcol=seagreen]
> I think the problem is that the maintenance plan use the Local Server
> Connection which still point to the old machine name. (I couldn't move this
> connection or modify the server name for this connection at all). I add
> another connection, but I still couldn't delete this maintenance plan.
> Please advise.
> --
> Best Regards,
> Lynn
>
> "Lynn" wrote:

Sunday, March 11, 2012

Could not load file or assembly SQLXMLBULKLOADLib

Greetings,

I'm in the process of migrating several SQL Server 2000 DTS packages to Integration Services packages. One of the old 2000 DTS packages used the SQLXML Bulk Loader component. In order to use the new SQLXML 4 COM object in my Script Task (to initiate the Bulk Loader using .NET code) I've used the tlbimp.exe tool to create a .NET wrapper DLL. I've placed the DLL in the appropriate directory (C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies), successfully added it to my project (with Intellisense working), but when I run the package it fails with the following error:

Could not load file or assembly 'SQLXMLBULKLOADLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

Note: I also tried placing the DLL in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 with no prevail.

I've confirm the file exists (and any dependencies) in their appropriate locations. Has anyone else run into this? Any help is much appreciated.

Thanks, Shaun

i'm not sure if this resolves your issue, but have you considered using the ole db destination component to bulk load the data?|||Reason I leaned toward the SQLXML Bulk Loader class is because i have a ton of XML I'm downloading and want to leverage the performance of the XML bulk loader. I'm not aware of how the OLE DB Destination object can help me with this.|||

I've resolved this issue by using... well... what I'm supposed to use. I created a Data Flow task and implemented an XML Source (applying an XSD transformation), Data Conversion (to convert from Unicode) and Ole Db Destination. This successfully loads the data into the database from XML.

|||shaun,

i'm glad that you found a solution to your problem. as you probably already know, the ole db destination is designed to bulk load data.|||

Did you add it to the GAC? You need to add it to the framework folder for design-time only (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727) but at runtime it uses the GAC.

I think the better solution is to re-write to use the XML Source as this is very powerful and handles hierarchical data, but obviously this may not be ideal if you have a lot of packages and XMl formats.

Tuesday, February 14, 2012

Corrupted TDS packets

I have the same problem as this posting, but It has never
been answered. Could somebody help?
Here is the old posting:
I have repeatedly error message in the application log:
17805, severity:20, Stqte:3 invalid buffer received from
client"
The KB 295113 - fix offer to load the latest SQL SP, but I
already have SQL SP3. Do I need SP 3A?
What else I need to do to clean the errors,
Thanks a lot.
.do you know if the error occurs for all client computers
or for a particular one? try reinstalling sql client. try
to find out if the problem is with the server or client.
if you think there is something wrong with the sql server
then try uninstalling the sql server and then reinstall
sql server and sp3a. if you still get errors then call MS
support.
>--Original Message--
>I have the same problem as this posting, but It has never
>been answered. Could somebody help?
>Here is the old posting:
>I have repeatedly error message in the application log:
>17805, severity:20, Stqte:3 invalid buffer received from
>client"
>The KB 295113 - fix offer to load the latest SQL SP, but
I
>already have SQL SP3. Do I need SP 3A?
>What else I need to do to clean the errors,
>Thanks a lot.
>..
>
>.
>