Hi I installed the add-in for excel data mining but when i try to select a table, in the tab of analyze, dont have any properties. please help me.
carlos of southamerica
Did you select a cell within a table?
Do you see "Table Tools" above the ribbon?
Do you see "Analyze" and "Design" ribbons? (they are usually the last 2 ribbons)
If all answers are yes, what do you see in the Analyze ribbon?
You may have to make sure there are selected under the SSIS Control flow items. Right Click on Control Flow task tab - select choose item... - select SSIS Control flow tab - you should see the foreachfile and foreachitem controls - make sure they are selected.
Carl
|||thanks for your answer but I did check that
In the list, I only see the ForEach loop item, and that I checked.
It's when I use that control flow item that I do not get the choice for ForEachFile and ForeachItem in the Collections page.
|||Still could not solve this (annoying) problem (need ForEach File)
Can somebody please help?
|||It sounds like your installation has been corrupted. You have the For and ForEach Shapes in the toolbox, but when you drag the ForEach shape over you are missing 2 of the values in the drop-down for the type of enumerator. Is this correct? If so you may need to do a reinstall.|||thanks, I've installed SQL Standard edition this weekend (with lots of problems, had to reinstall windows, visual studio did not install) and since then I have the mentioned items.
just discovered another (very) big problem though, not one of my SSIS packages works, every time I want to edit the data flow, Visual studio crashes,
any experience with that?
|||That's weird. No errors come up? It just crashes?
I had an issue with very large packages sometimes crashing. It didn't really crash the IDE, but I couldn't save any packages. I would get an Out of Memory error. That mysteriously disappeared though.
Do you have SP1?
|||I copy my thread on that, works now, I had to delete all data sources and data source views, execute, edit in debug mode and stop debugging, very weird indeed.
Adress was different by package
I have CTP1 installed, did you install the Techn preview of SP2? Worth doing (and taking the risk)?
I used an evaluation version till last week.
Was working fine so I decided to buy a Standard License.
Installed during the weekend, I had many problems till I decided to reinstall completely Windows. I have installed SP1
Everything worked fine then, ONLY not one of my SSIS packages still works; I get following error when editing the data flow task
The thread 'Win32 Thread' (0x7e8) has exited with code 0 (0x0).
Unhandled exception at 0x54fc5e89 in devenv.exe: 0xC0000005: Access violation reading location 0x00000000.
Please help, this is a disaster otherwise
Seems to work if I delete datasources and data source views and execute first?
You may have to make sure there are selected under the SSIS Control flow items. Right Click on Control Flow task tab - select choose item... - select SSIS Control flow tab - you should see the foreachfile and foreachitem controls - make sure they are selected.
Carl
|||thanks for your answer but I did check that
In the list, I only see the ForEach loop item, and that I checked.
It's when I use that control flow item that I do not get the choice for ForEachFile and ForeachItem in the Collections page.
|||Still could not solve this (annoying) problem (need ForEach File)
Can somebody please help?
|||It sounds like your installation has been corrupted. You have the For and ForEach Shapes in the toolbox, but when you drag the ForEach shape over you are missing 2 of the values in the drop-down for the type of enumerator. Is this correct? If so you may need to do a reinstall.|||thanks, I've installed SQL Standard edition this weekend (with lots of problems, had to reinstall windows, visual studio did not install) and since then I have the mentioned items.
just discovered another (very) big problem though, not one of my SSIS packages works, every time I want to edit the data flow, Visual studio crashes,
any experience with that?
|||That's weird. No errors come up? It just crashes?
I had an issue with very large packages sometimes crashing. It didn't really crash the IDE, but I couldn't save any packages. I would get an Out of Memory error. That mysteriously disappeared though.
Do you have SP1?
|||I copy my thread on that, works now, I had to delete all data sources and data source views, execute, edit in debug mode and stop debugging, very weird indeed.
Adress was different by package
I have CTP1 installed, did you install the Techn preview of SP2? Worth doing (and taking the risk)?
I used an evaluation version till last week.
Was working fine so I decided to buy a Standard License.
Installed during the weekend, I had many problems till I decided to reinstall completely Windows. I have installed SP1
Everything worked fine then, ONLY not one of my SSIS packages still works; I get following error when editing the data flow task
The thread 'Win32 Thread' (0x7e8) has exited with code 0 (0x0).
Unhandled exception at 0x54fc5e89 in devenv.exe: 0xC0000005: Access violation reading location 0x00000000.
Please help, this is a disaster otherwise
Seems to work if I delete datasources and data source views and execute first?
You may have to make sure there are selected under the SSIS Control flow items. Right Click on Control Flow task tab - select choose item... - select SSIS Control flow tab - you should see the foreachfile and foreachitem controls - make sure they are selected.
Carl
|||thanks for your answer but I did check that
In the list, I only see the ForEach loop item, and that I checked.
It's when I use that control flow item that I do not get the choice for ForEachFile and ForeachItem in the Collections page.
|||Still could not solve this (annoying) problem (need ForEach File)
Can somebody please help?
|||It sounds like your installation has been corrupted. You have the For and ForEach Shapes in the toolbox, but when you drag the ForEach shape over you are missing 2 of the values in the drop-down for the type of enumerator. Is this correct? If so you may need to do a reinstall.|||thanks, I've installed SQL Standard edition this weekend (with lots of problems, had to reinstall windows, visual studio did not install) and since then I have the mentioned items.
just discovered another (very) big problem though, not one of my SSIS packages works, every time I want to edit the data flow, Visual studio crashes,
any experience with that?
|||That's weird. No errors come up? It just crashes?
I had an issue with very large packages sometimes crashing. It didn't really crash the IDE, but I couldn't save any packages. I would get an Out of Memory error. That mysteriously disappeared though.
Do you have SP1?
|||I copy my thread on that, works now, I had to delete all data sources and data source views, execute, edit in debug mode and stop debugging, very weird indeed.
Adress was different by package
I have CTP1 installed, did you install the Techn preview of SP2? Worth doing (and taking the risk)?
I used an evaluation version till last week.
Was working fine so I decided to buy a Standard License.
Installed during the weekend, I had many problems till I decided to reinstall completely Windows. I have installed SP1
Everything worked fine then, ONLY not one of my SSIS packages still works; I get following error when editing the data flow task
The thread 'Win32 Thread' (0x7e8) has exited with code 0 (0x0).
Unhandled exception at 0x54fc5e89 in devenv.exe: 0xC0000005: Access violation reading location 0x00000000.
Please help, this is a disaster otherwise
Seems to work if I delete datasources and data source views and execute first?
Hi All,
I have a SSL certificate installed on my SQL Server 2005. There is a default certificate as well which was created by the database itself.
I have configured the database to use my own certificate and have also set the ForceEncryption to Yes on the server.
Now, I am expecting that if my ASP.NET code on a different machine tries to connect to the database without having the root certificate installed on client's certificate store, I should get an error. But, I am not getting an error.
But, I do get the following error when I set Encrypt = Yes
"ERROR: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.)"
and, If I set Encrypt=No, I do not get any error again.
My understanding was that if server forces encryption then client should definitely have the root certificate. Is that incorrect understanding?
Also, I want to know about what will happen if ForceEncryption = No on the server and Encrypt = Yes in the connection string.
Could you please help me understand the results of various options like this?
Additionally, with the server still Forcing Encryption, if I do install the root and intermediate root on my client then I get the following error with Encrypt = Yes.
"ERROR: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.)"
The Encrypt = No setting again does not give any error.
Thanks and Regards,
-Ajay Kumar Suri
Hi Ajay,
The validation of the server's certificate will only occur if encryption is forced on the client-side. Take a look at this posting for more info: http://blogs.msdn.com/dataaccess/archive/2005/08/05/448401.aspx
Il-Sung.
|||Hi,
Thanks very much for your reply.
Could you please verify if my understanding now is correct for SQL Server 2005.
Server : Encryption On (Self Signed Certificate)
Client : Encryption off or not specified.
The channel is encrypted.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate not installed on client.
The channel is encrypted using the Self Signed SQL Server 2005 certificate instead.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate is installed on client.
The channel is encrypted using the server SSL certificate.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified or client has the root certificate.
Server : Encryption Off.
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified. This would use the self created certificate from the server.
Server : Encryption Off.
Client : Encryption Off.
No encryption.
I hope I have understood it correctly.
Please advise.
Best Regards,
-Ajay Kumar Suri
|||Hi Ajay,
Not quite. I've added my comments in blue. The key thing to understand is that client will only try to validate the server's certificate if encryption is requested from the client side. Otherwise, no certificate validation is performed so there's no need to use Trust Server Certificate, even for a self-signed cert.
Server : Encryption On (Self Signed Certificate)
Client : Encryption off or not specified.
The channel is encrypted.
> Correct.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate not installed on client.
The channel is encrypted using the Self Signed SQL Server 2005 certificate instead.
> Incorrect. The channel is encrypted using the provisioned certficiate, not the self-signed cert.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate is installed on client.
The channel is encrypted using the server SSL certificate.
> Correct.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified or client has the root certificate.
> Correct.
Server : Encryption Off.
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified. This would use the self created certificate from the server.
> Depends if the server has a proper certificate provisioned or not. If not, then a self-signed cert would be used and you are correct that Trust Server Certificate must be specified.
Server : Encryption Off.
Client : Encryption Off.
No encryption.
> Correct, although the login packet will always be encrypted.
Hope this clears things up.
Il-Sung.
|||Hi Sung,
Thanks very much for your comments.
It does clear a lot of things for me.
Best Regards,
-Ajay Kumar Suri
Hi All,
I have a SSL certificate installed on my SQL Server 2005. There is a default certificate as well which was created by the database itself.
I have configured the database to use my own certificate and have also set the ForceEncryption to Yes on the server.
Now, I am expecting that if my ASP.NET code on a different machine tries to connect to the database without having the root certificate installed on client's certificate store, I should get an error. But, I am not getting an error.
But, I do get the following error when I set Encrypt = Yes
"ERROR: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.)"
and, If I set Encrypt=No, I do not get any error again.
My understanding was that if server forces encryption then client should definitely have the root certificate. Is that incorrect understanding?
Also, I want to know about what will happen if ForceEncryption = No on the server and Encrypt = Yes in the connection string.
Could you please help me understand the results of various options like this?
Additionally, with the server still Forcing Encryption, if I do install the root and intermediate root on my client then I get the following error with Encrypt = Yes.
"ERROR: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.)"
The Encrypt = No setting again does not give any error.
Thanks and Regards,
-Ajay Kumar Suri
Hi Ajay,
The validation of the server's certificate will only occur if encryption is forced on the client-side. Take a look at this posting for more info: http://blogs.msdn.com/dataaccess/archive/2005/08/05/448401.aspx
Il-Sung.
|||Hi,
Thanks very much for your reply.
Could you please verify if my understanding now is correct for SQL Server 2005.
Server : Encryption On (Self Signed Certificate)
Client : Encryption off or not specified.
The channel is encrypted.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate not installed on client.
The channel is encrypted using the Self Signed SQL Server 2005 certificate instead.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate is installed on client.
The channel is encrypted using the server SSL certificate.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified or client has the root certificate.
Server : Encryption Off.
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified. This would use the self created certificate from the server.
Server : Encryption Off.
Client : Encryption Off.
No encryption.
I hope I have understood it correctly.
Please advise.
Best Regards,
-Ajay Kumar Suri
|||Hi Ajay,
Not quite. I've added my comments in blue. The key thing to understand is that client will only try to validate the server's certificate if encryption is requested from the client side. Otherwise, no certificate validation is performed so there's no need to use Trust Server Certificate, even for a self-signed cert.
Server : Encryption On (Self Signed Certificate)
Client : Encryption off or not specified.
The channel is encrypted.
> Correct.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate not installed on client.
The channel is encrypted using the Self Signed SQL Server 2005 certificate instead.
> Incorrect. The channel is encrypted using the provisioned certficiate, not the self-signed cert.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate is installed on client.
The channel is encrypted using the server SSL certificate.
> Correct.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified or client has the root certificate.
> Correct.
Server : Encryption Off.
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified. This would use the self created certificate from the server.
> Depends if the server has a proper certificate provisioned or not. If not, then a self-signed cert would be used and you are correct that Trust Server Certificate must be specified.
Server : Encryption Off.
Client : Encryption Off.
No encryption.
> Correct, although the login packet will always be encrypted.
Hope this clears things up.
Il-Sung.
|||Hi Sung,
Thanks very much for your comments.
It does clear a lot of things for me.
Best Regards,
-Ajay Kumar Suri
Hi All,
I have a SSL certificate installed on my SQL Server 2005. There is a default certificate as well which was created by the database itself.
I have configured the database to use my own certificate and have also set the ForceEncryption to Yes on the server.
Now, I am expecting that if my ASP.NET code on a different machine tries to connect to the database without having the root certificate installed on client's certificate store, I should get an error. But, I am not getting an error.
But, I do get the following error when I set Encrypt = Yes
"ERROR: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.)"
and, If I set Encrypt=No, I do not get any error again.
My understanding was that if server forces encryption then client should definitely have the root certificate. Is that incorrect understanding?
Also, I want to know about what will happen if ForceEncryption = No on the server and Encrypt = Yes in the connection string.
Could you please help me understand the results of various options like this?
Additionally, with the server still Forcing Encryption, if I do install the root and intermediate root on my client then I get the following error with Encrypt = Yes.
"ERROR: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.)"
The Encrypt = No setting again does not give any error.
Thanks and Regards,
-Ajay Kumar Suri
Hi Ajay,
The validation of the server's certificate will only occur if encryption is forced on the client-side. Take a look at this posting for more info: http://blogs.msdn.com/dataaccess/archive/2005/08/05/448401.aspx
Il-Sung.
|||Hi,
Thanks very much for your reply.
Could you please verify if my understanding now is correct for SQL Server 2005.
Server : Encryption On (Self Signed Certificate)
Client : Encryption off or not specified.
The channel is encrypted.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate not installed on client.
The channel is encrypted using the Self Signed SQL Server 2005 certificate instead.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate is installed on client.
The channel is encrypted using the server SSL certificate.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified or client has the root certificate.
Server : Encryption Off.
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified. This would use the self created certificate from the server.
Server : Encryption Off.
Client : Encryption Off.
No encryption.
I hope I have understood it correctly.
Please advise.
Best Regards,
-Ajay Kumar Suri
|||Hi Ajay,
Not quite. I've added my comments in blue. The key thing to understand is that client will only try to validate the server's certificate if encryption is requested from the client side. Otherwise, no certificate validation is performed so there's no need to use Trust Server Certificate, even for a self-signed cert.
Server : Encryption On (Self Signed Certificate)
Client : Encryption off or not specified.
The channel is encrypted.
> Correct.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate not installed on client.
The channel is encrypted using the Self Signed SQL Server 2005 certificate instead.
> Incorrect. The channel is encrypted using the provisioned certficiate, not the self-signed cert.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate is installed on client.
The channel is encrypted using the server SSL certificate.
> Correct.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified or client has the root certificate.
> Correct.
Server : Encryption Off.
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified. This would use the self created certificate from the server.
> Depends if the server has a proper certificate provisioned or not. If not, then a self-signed cert would be used and you are correct that Trust Server Certificate must be specified.
Server : Encryption Off.
Client : Encryption Off.
No encryption.
> Correct, although the login packet will always be encrypted.
Hope this clears things up.
Il-Sung.
|||Hi Sung,
Thanks very much for your comments.
It does clear a lot of things for me.
Best Regards,
-Ajay Kumar Suri
Hi All,
I have a SSL certificate installed on my SQL Server 2005. There is a default certificate as well which was created by the database itself.
I have configured the database to use my own certificate and have also set the ForceEncryption to Yes on the server.
Now, I am expecting that if my ASP.NET code on a different machine tries to connect to the database without having the root certificate installed on client's certificate store, I should get an error. But, I am not getting an error.
But, I do get the following error when I set Encrypt = Yes
"ERROR: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.)"
and, If I set Encrypt=No, I do not get any error again.
My understanding was that if server forces encryption then client should definitely have the root certificate. Is that incorrect understanding?
Also, I want to know about what will happen if ForceEncryption = No on the server and Encrypt = Yes in the connection string.
Could you please help me understand the results of various options like this?
Additionally, with the server still Forcing Encryption, if I do install the root and intermediate root on my client then I get the following error with Encrypt = Yes.
"ERROR: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.)"
The Encrypt = No setting again does not give any error.
Thanks and Regards,
-Ajay Kumar Suri
Hi Ajay,
The validation of the server's certificate will only occur if encryption is forced on the client-side. Take a look at this posting for more info: http://blogs.msdn.com/dataaccess/archive/2005/08/05/448401.aspx
Il-Sung.
|||Hi,
Thanks very much for your reply.
Could you please verify if my understanding now is correct for SQL Server 2005.
Server : Encryption On (Self Signed Certificate)
Client : Encryption off or not specified.
The channel is encrypted.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate not installed on client.
The channel is encrypted using the Self Signed SQL Server 2005 certificate instead.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate is installed on client.
The channel is encrypted using the server SSL certificate.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified or client has the root certificate.
Server : Encryption Off.
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified. This would use the self created certificate from the server.
Server : Encryption Off.
Client : Encryption Off.
No encryption.
I hope I have understood it correctly.
Please advise.
Best Regards,
-Ajay Kumar Suri
|||Hi Ajay,
Not quite. I've added my comments in blue. The key thing to understand is that client will only try to validate the server's certificate if encryption is requested from the client side. Otherwise, no certificate validation is performed so there's no need to use Trust Server Certificate, even for a self-signed cert.
Server : Encryption On (Self Signed Certificate)
Client : Encryption off or not specified.
The channel is encrypted.
> Correct.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate not installed on client.
The channel is encrypted using the Self Signed SQL Server 2005 certificate instead.
> Incorrect. The channel is encrypted using the provisioned certficiate, not the self-signed cert.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption off or not specified. Root Certificate is installed on client.
The channel is encrypted using the server SSL certificate.
> Correct.
Server : Encryption On (Certificate Issued by a Trusted Authority)
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified or client has the root certificate.
> Correct.
Server : Encryption Off.
Client : Encryption On.
Will result in problem unless Trust Server Certificate is specified. This would use the self created certificate from the server.
> Depends if the server has a proper certificate provisioned or not. If not, then a self-signed cert would be used and you are correct that Trust Server Certificate must be specified.
Server : Encryption Off.
Client : Encryption Off.
No encryption.
> Correct, although the login packet will always be encrypted.
Hope this clears things up.
Il-Sung.
|||Hi Sung,
Thanks very much for your comments.
It does clear a lot of things for me.
Best Regards,
-Ajay Kumar Suri
Is it possible to force the SLQ 2005 Client Components to be installed into a diffrent location other than the default location?
What I'm trying to do is run the setup command though the command line to create an unattended client installation with all the client componets to a diffrent location that
Thanks, Any information or examples would be great!
There is a way to specify client component location is setup or on the command line but it can only be used for the first time SQL Server 2005 is installed on a machine. Once there is any product or instance of SQL Server 2005 on the machine this location cannot be changed. To specify the location on the command line you can use INSTALLSQLSHAREDDIR.
Note: there are still some components going under Program Files\Microsoft SQL Server\90 which location cannot be changed. But most of the client components is installed to INSTALLSQLSHAREDDIR.
For example:
setup.exe INSTALLSQLSHAREDDIR=D:\SQLTools ADDLOCAL=Client_Components,Connectivity,SQL_Tools90,SQL_WarehouseDevWorkbench /qb
ADDLOCAL lists all features you want to install. See template.ini in the same location as setup.exe for whole list of features.
