Failed To Save Package File

I am just beginning to work on an ETL project at a new client site using their computers. They are an IT department new to SQL Server. We have SQL Server 2005 up and running, no probkem. But I get that error when I try to add a new package to an SSIS project. The error number is 0x8002801D "Library Not Registered". I did see the post about the MSXML DLL files and when I try to load an existing package I get 3 errors regarding XML - stating that the MSXML binaries may not be installed or registered properly. I searched and found the MSXML3 & 6 DLLs but the MSXML4.DLL appears to be missing. If I repair the installation, will this fix it? BTW - the MSXML 6.0 Parser did show as being installed in Add/Remove Programs.

Thanks for you help!

I won't guarantee that it will fix it, but it's not going to hurt |||

I do not think SSIS uses msxml4.dll. Try registering msxml3.dll and msxml6.dll.

Thanks.

|||Thanks, I will. But I do have a question. My client installed the 64 bit version of SQL Server and the client side tools from the same CD. When I search on the files, I see that both the 32 bit and 64 bit versions of the DLLs are on the system. Should I register the 64 bit DLLs?|||You should register both.

Failed To Save Package File

I am just beginning to work on an ETL project at a new client site using their computers. They are an IT department new to SQL Server. We have SQL Server 2005 up and running, no probkem. But I get that error when I try to add a new package to an SSIS project. The error number is 0x8002801D "Library Not Registered". I did see the post about the MSXML DLL files and when I try to load an existing package I get 3 errors regarding XML - stating that the MSXML binaries may not be installed or registered properly. I searched and found the MSXML3 & 6 DLLs but the MSXML4.DLL appears to be missing. If I repair the installation, will this fix it? BTW - the MSXML 6.0 Parser did show as being installed in Add/Remove Programs.

Thanks for you help!

I won't guarantee that it will fix it, but it's not going to hurt |||

I do not think SSIS uses msxml4.dll. Try registering msxml3.dll and msxml6.dll.

Thanks.

|||Thanks, I will. But I do have a question. My client installed the 64 bit version of SQL Server and the client side tools from the same CD. When I search on the files, I see that both the 32 bit and 64 bit versions of the DLLs are on the system. Should I register the 64 bit DLLs?|||You should register both.

failed to connect to the server

When I have a subscription built for a report it runs at the time expected, but the report send via e-mail fails. I can run the report from a client workstation just fine. I can also run it from the admin tool fine too, it just will not run as part of a subscription. The full context of the error message is as follows:

Failure sending mail: The transport failed to connect to the server

This is not my first Reporting services report, but I am trying to replace all Crystal reports with Reporting services reports and this functionality is greatly needed.

Thanks! - Eric-

The error is telling you the RS server cannot connect to the Mail server. Make sure that the unattended execution account is setup and is a user that has access to the mail server.

Here is a link to help you.

http://msdn2.microsoft.com/en-us/library/ms155851.aspx

Failed client connection by name\name.

Attempting ODBC connection to SQL Server by MachineName\SqlServerName doesn't work.
Can only connect by using IP address of server machine with name of SQL Server instance.
Any help would be appreciated.
thanksPlease refer to the following url, it may help you:
http://www.able-consulting.com/MDAC/ADO/Connection/OLEDB_Providers.htm#OLEDBProviderForSQLServer|||Rather than SQL-Server, can u access that machine by name from the client? It also happens bcz of WINS entry or if the Server is in DMZ etc. If u can't access the server over the LAN by name, edit ur client's HOSTS file.|||Add the entry in LMHOSTS file and if its still timeouts then ensure proper value is defined on SQL server to login timeout.

Also ensure similar protocols are enabled between client & server.

Extremely slow Excel MDX

Using Excel as a client is most of the time exceedingly slow. For example writing a simple query of the type:

SELECT [Measures].[Some Measure] ON 0,
[Product].[Product-Version].[Product] ON 1
FROM [Cubename]

in Management studio is in Excel transformed to:

SELECT NON EMPTY HIERARCHIZE(AddCalculatedMembers({DrillDownLevel({[Product].[Product-Version].[All]})})) DIMENSION PROPERTIES PARENT_UNIQUE_NAME ON COLUMNS FROM [Cubename] WHERE ([Measures].[Some Measure])

which takes several times longer to execute. As one starts drilling down it becomes increasingly worse with excel producing MDX that takes 100:s of times longer to execute then if I handwrite the mdx. This is with a very simple cube where Some Measure is not a calculated member. I can't even begin to imagine how slow it would be with a more complex cube. Is there anything to be done about this, any guidelines to follow to make it easer for Excel to generate "normal" mdx?

I had similar problem with Excel and OWC when accessing OLAP Cubes. Unfortunately, unless you optimize your cube, there is nothing can be done with how Excel generate mdx to retrieve data. Excel and OWC is closed code, and recently Microsoft announced that they will be stopping new releases for OWC. Howerver, Excel PivotTable has new version, take a look at Office 2007 in Beta version. It generates more efficient MDXs compared to Office 2003/2000.

Downside, it will take another 2-3 years for Office 2007 to be as popular as Office 2003, so, distribution of your solution in Office 2007 might be an issue if u decide to switch to Office 2007 in larger scale enterprise.

|||Thanks. Is there anything special you have in mind when you say "unless you optimize your cube"? Or do you mean the "ordinary" optimizations one does to make the server work decently fast? I will try to have a look at the 2007 beta though.|||

As mentioned earlier, you can take a look at Office 2007 sending bit different MDX queries. You also take a look at the ProClarity recently aquired by Microsoft see if you get better performance using it.

Also make sure you install latest service pack - SP1. There has been some performance improvements in it. You will see event more performance improvements in upcoming service pack 2. Watch for announcements of Community Technology Preview (CTP) to get your hands on upcoming SP2.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Extremely Slow connection time

Hi
I have recently reinstalled XP Professional as well as the MSSQL client tool
s.
Our SQL 2000 server is running Win2K with 512MB RAM, and has been doing so f
or quite a while, no changes where done to the server while I reinstalled XP
on my PC.
Now my connection to the SQL server is extremely sluggish, e.g. connecting v
ia the Query Analyzer takes up to 2 minutes, and so do any other subsequent
actions, for example opening the list of databases, tables or stored procedu
res on the object browser.
All my queries take ages to get going even for the simplest queries.
Previously the response was very reasonable, as are the other developers PCs
in the company, with similar set up.
I have tried using both forms of security but have no joy either way. I have
used the IP address – no go.
If I ping the NetBIOS name of the server the response is instantaneous.
Please help!!Did you remember to install SQL Server 2000 SP3a after the reinstall?
Without it, you are vulnerable to the Slammer.
Hope this helps.
Dan Guzman
SQL Server MVP
"Herbert Schroder" <herberts@.mweb.co.za> wrote in message
news:9FF54BCC-2F28-4F5A-9D6A-06A4D4B1CA41@.microsoft.com...
> Hi
> I have recently reinstalled XP Professional as well as the MSSQL client
tools.
> Our SQL 2000 server is running Win2K with 512MB RAM, and has been doing so
for quite a while, no changes where done to the server while I reinstalled
XP on my PC.
> Now my connection to the SQL server is extremely sluggish, e.g. connecting
via the Query Analyzer takes up to 2 minutes, and so do any other subsequent
actions, for example opening the list of databases, tables or stored
procedures on the object browser.
> All my queries take ages to get going even for the simplest queries.
> Previously the response was very reasonable, as are the other developers
PCs in the company, with similar set up.
> I have tried using both forms of security but have no joy either way. I
have used the IP address - no go.
> If I ping the NetBIOS name of the server the response is instantaneous.
>
> Please help!!
>

Extremely Slow connection time

Hi
I have recently reinstalled XP Professional as well as the MSSQL client tools.
Our SQL 2000 server is running Win2K with 512MB RAM, and has been doing so for quite a while, no changes where done to the server while I reinstalled XP on my PC.
Now my connection to the SQL server is extremely sluggish, e.g. connecting via the Query Analyzer takes up to 2 minutes, and so do any other subsequent actions, for example opening the list of databases, tables or stored procedures on the object browser.
All my queries take ages to get going even for the simplest queries.
Previously the response was very reasonable, as are the other developers PCs in the company, with similar set up.
I have tried using both forms of security but have no joy either way. I have used the IP address – no go.
If I ping the NetBIOS name of the server the response is instantaneous.
Please help!!
Did you remember to install SQL Server 2000 SP3a after the reinstall?
Without it, you are vulnerable to the Slammer.
Hope this helps.
Dan Guzman
SQL Server MVP
"Herbert Schroder" <herberts@.mweb.co.za> wrote in message
news:9FF54BCC-2F28-4F5A-9D6A-06A4D4B1CA41@.microsoft.com...
> Hi
> I have recently reinstalled XP Professional as well as the MSSQL client
tools.
> Our SQL 2000 server is running Win2K with 512MB RAM, and has been doing so
for quite a while, no changes where done to the server while I reinstalled
XP on my PC.
> Now my connection to the SQL server is extremely sluggish, e.g. connecting
via the Query Analyzer takes up to 2 minutes, and so do any other subsequent
actions, for example opening the list of databases, tables or stored
procedures on the object browser.
> All my queries take ages to get going even for the simplest queries.
> Previously the response was very reasonable, as are the other developers
PCs in the company, with similar set up.
> I have tried using both forms of security but have no joy either way. I
have used the IP address - no go.
> If I ping the NetBIOS name of the server the response is instantaneous.
>
> Please help!!
>

Extremely slow client connection to MSSQL

Hallo

i'm experiencing an extremely slow connection from a WXPP Sp2 client to a MSSQL2000 running on a W2k server. The client is running a VB6 application that connect with Windows authentication: every form requesting data opens with a long delay at the first launch; next attempts run normally fast.

In the same LAN there are some others identical clients, all running fine.

Every other network activity from that client is ok.

Where should i start to investigate from?

Can you check how much RAM is on this machine compared to the other machines.

The reason I say this is that if its slow the first time and quick thereafter, then its as if the machine is busy loading the first time, and as it has it memory thereafter, quick any subsequent times.

Regards,

Barry Andrew

|||

From what you described, looks like yourissue only happens between one machine and the server on you local network. There are several things that are normally helpful.

(1) "ping" to see the round trip latency between these two machines and compare it with others. Try multiple times. You can also try to copy files between machines and count the elapse time. If there is big discrepancies, there is network issues, you need to contact your admin to resolve it.

(2) Use provider prefixed connection string. For exampl, osql -E -Stcp:servername,portnunber. Explicit connection string can avoid the overhead of trying multiple different providers during connection and some of them are not supported by your server/network.

(3) If the delay happens after the connection, you can use SQL profiler. But according to your description, I think your problem is at connection stage.

HTH.

Extranet Thick Client Connection

Hi,
I have a Windows Forms application that uses ADO.NET 1.1 to communicate with SQL Server 2K. I would like to start retailing my Windows app, allowing clients who are not in my domain or work-group to communicate with a database on MY SQL Server using Wind
ows Integrated Authentication. Can I get some guidance on exactly how this would be done please?
JT
Windows Authentication without a domain means you're using Workgroup
Security. This essentially requires you to duplicate nt user accounts and
passwords on both machines. This will work with Named Pipe connections.
It will not work with Sockets.
I'd recommend securing the traffic with SQL's protocol encryption. You'll
need a server certificate installed on the SQL Server.
276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
Server
http://support.microsoft.com/?id=276553
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Thanks Kevin - I appreciate it. How do you communicate with Named Pipes over the internet? My clients would be at sites far remote from my SQL Server(s). Would I have to have a VPN? Would exposing SQL Server as a Web Service be an option?
JT
"Kevin McDonnell [MSFT]" wrote:

> Windows Authentication without a domain means you're using Workgroup
> Security. This essentially requires you to duplicate nt user accounts and
> passwords on both machines. This will work with Named Pipe connections.
> It will not work with Sockets.
> I'd recommend securing the traffic with SQL's protocol encryption. You'll
> need a server certificate installed on the SQL Server.
> 276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
> Server
> http://support.microsoft.com/?id=276553
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||You would not use Named Pipes over the internet. The ports required for it
to work would make your
firewall insecure.
If you're remote clients are VPNing in, then I would think that they'd also
would be authenticating
against a DC. So, after they've done this they should be able to use
Windows Auth to SQL.
If you're clients are coming from an Extranet, do you have a 1 way Trust
between machines there and your other domain?
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Extranet Thick Client Connection

Hi,
I have a Windows Forms application that uses ADO.NET 1.1 to communicate with
SQL Server 2K. I would like to start retailing my Windows app, allowing cl
ients who are not in my domain or work-group to communicate with a database
on MY SQL Server using Wind
ows Integrated Authentication. Can I get some guidance on exactly how this
would be done please?
JTWindows Authentication without a domain means you're using Workgroup
Security. This essentially requires you to duplicate nt user accounts and
passwords on both machines. This will work with Named Pipe connections.
It will not work with Sockets.
I'd recommend securing the traffic with SQL's protocol encryption. You'll
need a server certificate installed on the SQL Server.
276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
Server
http://support.microsoft.com/?id=276553
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Kevin - I appreciate it. How do you communicate with Named Pipes ove
r the internet? My clients would be at sites far remote from my SQL Server(
s). Would I have to have a VPN? Would exposing SQL Server as a Web Service
be an option?
JT
"Kevin McDonnell [MSFT]" wrote:

> Windows Authentication without a domain means you're using Workgroup
> Security. This essentially requires you to duplicate nt user accounts and
> passwords on both machines. This will work with Named Pipe connections.
> It will not work with Sockets.
> I'd recommend securing the traffic with SQL's protocol encryption. You'll
> need a server certificate installed on the SQL Server.
> 276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
> Server
> http://support.microsoft.com/?id=276553
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||You would not use Named Pipes over the internet. The ports required for it
to work would make your
firewall insecure.
If you're remote clients are VPNing in, then I would think that they'd also
would be authenticating
against a DC. So, after they've done this they should be able to use
Windows Auth to SQL.
If you're clients are coming from an Extranet, do you have a 1 way Trust
between machines there and your other domain?
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.