Showing posts with label engine. Show all posts
Showing posts with label engine. Show all posts

Thursday, March 22, 2012

a connection could not be made to the data source

I am trying to process a cube still it failed since "Errors in the high-level relational engine. A connection could not be made to the data source with the DataSource of "MY-DATASOURCE", Name of "MY-DATASOURCE").

The sql instance is running on the same machine in where I am working the solution. Can someone provide some hints on what to do to resolve this issue?

By looking at the "AdventuresWorks" sample the main difference that I have in my solution is that I have an instance and the AW sample is pointing to the default instance using the "localhost" reference only. My datasource connection is refered as "MyHost\MySqlInstance"...
I used the wong impersonation settings! I changed those and now I am processing the cube.

Sunday, March 11, 2012

8114 error w/db maintenance plan

Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
can initially set up, but when I go back into and hit OK, I get the following
error:
Error 8114: Error converting data type into to tinyint.
This happens whether I make any changes or not. The job fails with the
basic sqlmaint.exe error:
Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
(Error 22029). The step failed.
Also, when I try to set the amount of time after which to purge backup
files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
I saw this same issue on some other websites, but no one had an answer. Any
advice? Thanks.
I can't remember what the 8114 error is but the unpopulated
days, weeks, months on the backups was sometimes related to
a missing registry value for the backup directory.
On a default instance, you would add a new string value to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer
The new string value is BackupDirectory
The data value for this is the path to your backup
directory. The default would be
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP
-Sue
On Mon, 27 Jun 2005 11:50:03 -0700, MEB
<MEB@.discussions.microsoft.com> wrote:

>Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
>can initially set up, but when I go back into and hit OK, I get the following
>error:
>Error 8114: Error converting data type into to tinyint.
>This happens whether I make any changes or not. The job fails with the
>basic sqlmaint.exe error:
>Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
>(Error 22029). The step failed.
>Also, when I try to set the amount of time after which to purge backup
>files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
>I saw this same issue on some other websites, but no one had an answer. Any
>advice? Thanks.

8114 error w/db maintenance plan

Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
can initially set up, but when I go back into and hit OK, I get the following
error:
Error 8114: Error converting data type into to tinyint.
This happens whether I make any changes or not. The job fails with the
basic sqlmaint.exe error:
Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
(Error 22029). The step failed.
Also, when I try to set the amount of time after which to purge backup
files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
I saw this same issue on some other websites, but no one had an answer. Any
advice? Thanks.I can't remember what the 8114 error is but the unpopulated
days, weeks, months on the backups was sometimes related to
a missing registry value for the backup directory.
On a default instance, you would add a new string value to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer
The new string value is BackupDirectory
The data value for this is the path to your backup
directory. The default would be
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP
-Sue
On Mon, 27 Jun 2005 11:50:03 -0700, MEB
<MEB@.discussions.microsoft.com> wrote:
>Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
>can initially set up, but when I go back into and hit OK, I get the following
>error:
>Error 8114: Error converting data type into to tinyint.
>This happens whether I make any changes or not. The job fails with the
>basic sqlmaint.exe error:
>Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42000]
>(Error 22029). The step failed.
>Also, when I try to set the amount of time after which to purge backup
>files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
>I saw this same issue on some other websites, but no one had an answer. Any
>advice? Thanks.

8114 error w/db maintenance plan

Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
can initially set up, but when I go back into and hit OK, I get the followin
g
error:
Error 8114: Error converting data type into to tinyint.
This happens whether I make any changes or not. The job fails with the
basic sqlmaint.exe error:
Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 420
00]
(Error 22029). The step failed.
Also, when I try to set the amount of time after which to purge backup
files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
I saw this same issue on some other websites, but no one had an answer. Any
advice? Thanks.I can't remember what the 8114 error is but the unpopulated
days, weeks, months on the backups was sometimes related to
a missing registry value for the backup directory.
On a default instance, you would add a new string value to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer
The new string value is BackupDirectory
The data value for this is the path to your backup
directory. The default would be
C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP
-Sue
On Mon, 27 Jun 2005 11:50:03 -0700, MEB
<MEB@.discussions.microsoft.com> wrote:

>Running SQL Desktop Engine 2000, sp3. I have a db maintenance plan that I
>can initially set up, but when I go back into and hit OK, I get the followi
ng
>error:
>Error 8114: Error converting data type into to tinyint.
>This happens whether I make any changes or not. The job fails with the
>basic sqlmaint.exe error:
>Executed as user: NT AUTHORITY/SYSTEM. sqlmaint.exe failed [SQLSTATE 42
000]
>(Error 22029). The step failed.
>Also, when I try to set the amount of time after which to purge backup
>files, the field is blank/unpopulated. It should be 'days', 'weeks', etc.
>I saw this same issue on some other websites, but no one had an answer. An
y
>advice? Thanks.

Friday, February 24, 2012

64 bit cluster cannot connect using dtutil

Hi,

I have a 64 bit Itanium SQL Cluster that I'm trying to set up. The database engine seems fine, but I'm trying to install some SSIS packages using dtUtil and I keep getting a connection error. The error is as follows

"Login timeout expired

An error has occured while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default seetings SQL Server does not allow remote connections.

Named Pipes Provider: Could not open a connection to SQL Server [2}. (Microsoft SQL Native Client)"

Also, in Management studio, I can make a connection to my SSIS Server, but when I go down to the MSDB folder to look at packages I get the same connection error.

I think I was able to deploy a package using the Deployment Manifest created by VS, but I'm not sure because I can't see the package in Mgt Studio.

It almost seems like it may be related to the cluster. I'm connected in to one of the Servers using Terminal Services. But I am trying to connect to the Cluster name in Mgt Studio.

Any thoughts/ideas/Solutions greatly appreciated.

Thanks.

Andy

Another note, I was able to get the dtUtil working by using the argument /DestS, which is the destination server, and specifying the cluster name. However, I still have the issue that I can't actually use Management Studio to view these packages, I still get the above error. I'm able to run my packages using SQL Server Agent, and when I go to create a job that calls an ssis package, I'm able to see the list of packages installed on the cluster?!?! Very weird.

My main issue is I can't use Management studio to Manage my packages. Help!

Andy

|||

I found the problem. Because of the cluster, the MsDtsSrvr.ini.xml file had a "." for the servername (I found this from another post that was due to 2 instances on a machine. I had to change the "." to our cluster name and now it works fine.

|||

Hi,

Question for you - in your case Ingration Service runs under cluster? In my case I installed IS on 2 nodes separately, runs as a service and when I changed MsDtsSrvr.ini.xml to PC/node name, restart service it did not work. But when I changed in ini names of folder itself it presents on IS management studio.

Thanks

64 bit cluster cannot connect using dtutil

Hi,

I have a 64 bit Itanium SQL Cluster that I'm trying to set up. The database engine seems fine, but I'm trying to install some SSIS packages using dtUtil and I keep getting a connection error. The error is as follows

"Login timeout expired

An error has occured while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default seetings SQL Server does not allow remote connections.

Named Pipes Provider: Could not open a connection to SQL Server [2}. (Microsoft SQL Native Client)"

Also, in Management studio, I can make a connection to my SSIS Server, but when I go down to the MSDB folder to look at packages I get the same connection error.

I think I was able to deploy a package using the Deployment Manifest created by VS, but I'm not sure because I can't see the package in Mgt Studio.

It almost seems like it may be related to the cluster. I'm connected in to one of the Servers using Terminal Services. But I am trying to connect to the Cluster name in Mgt Studio.

Any thoughts/ideas/Solutions greatly appreciated.

Thanks.

Andy

Another note, I was able to get the dtUtil working by using the argument /DestS, which is the destination server, and specifying the cluster name. However, I still have the issue that I can't actually use Management Studio to view these packages, I still get the above error. I'm able to run my packages using SQL Server Agent, and when I go to create a job that calls an ssis package, I'm able to see the list of packages installed on the cluster?!?! Very weird.

My main issue is I can't use Management studio to Manage my packages. Help!

Andy

|||

I found the problem. Because of the cluster, the MsDtsSrvr.ini.xml file had a "." for the servername (I found this from another post that was due to 2 instances on a machine. I had to change the "." to our cluster name and now it works fine.

|||

Hi,

Question for you - in your case Ingration Service runs under cluster? In my case I installed IS on 2 nodes separately, runs as a service and when I changed MsDtsSrvr.ini.xml to PC/node name, restart service it did not work. But when I changed in ini names of folder itself it presents on IS management studio.

Thanks

Saturday, February 11, 2012

4 CPU's on app server, can I buy only 1 license?

On a the db server, you can configure the db engine to only use 1 CPU
and therefore only have to purchase 1 SQL Server license. But on my app
server that has 4 CPU's, can I configure RS 2000 to only take advantage
of 1 of those CPU's and therefore only have to purchase 1 license for
the app server? How do I configure this on the app server side?On Jan 17, 1:21 pm, "Dave" <macleary2...@.yahoo.com> wrote:
> On a the db server, you can configure the db engine to only use 1 CPU
> and therefore only have to purchase 1 SQL Server license. But on my app
> server that has 4 CPU's, can I configure RS 2000 to only take advantage
> of 1 of those CPU's and therefore only have to purchase 1 license for
> the app server? How do I configure this on the app server side?
bumped. Anyone have an answer to this? Also, can this be done in RS
2005 and/or RS 2000? Or neither? Thanks.|||Hello,
If you have licensing per processor on application server you have to
purchase licenses
for all processors that are used by operating system on this server.
Microsoft says:
"Per-processor licensing. Required for extranet or Internet deployments.
Requires a single license for each CPU in the operating system instance
running Reporting Services. "
You can't set Reporting Services to use only one processor and purchase only
one per-processor license whereas operating systems uses all 4 processors.
In this situation Reporting Services might use only one CPU directly but
indirectly might use all 4 processors.
So that licenses for all processors are required.
Best Regards,
Radoslaw Lebkowski
Uzytkownik "Dave" <macleary2000@.yahoo.com> napisal w wiadomosci
news:1170951737.216688.228680@.m58g2000cwm.googlegroups.com...
> On Jan 17, 1:21 pm, "Dave" <macleary2...@.yahoo.com> wrote:
>> On a the db server, you can configure the db engine to only use 1 CPU
>> and therefore only have to purchase 1 SQL Server license. But on my app
>> server that has 4 CPU's, can I configure RS 2000 to only take advantage
>> of 1 of those CPU's and therefore only have to purchase 1 license for
>> the app server? How do I configure this on the app server side?
> bumped. Anyone have an answer to this? Also, can this be done in RS
> 2005 and/or RS 2000? Or neither? Thanks.
>