Showing posts with label back. Show all posts
Showing posts with label back. Show all posts

Tuesday, March 27, 2012

Cannot Edit Jobs

Two days back we have installed SP2 on SQLServer2005 Active/Active Cluster which result in failure.

Only Database Services and Analysis Services where not updated and rest of the services got updated.

After a restart , the behaviour of SQLServer is helarious.

We got into lot of problem so we opened support from Microsoft.

One of the problem i forgot to mentioed to Microsoft was on editing the Job i cannot see anything inside,all the entries where empty closing the job window and opening it again i got all my entries back but on editing i got the below mentioned Error.

Error:

Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error:c001f011(Microsoft.SqlServer.ManagedDTS)

If anyone faced the same problem and got any resolution please let me know.

Anyhelp will be appriciated.

Solved the Error.

In one of the artical i read tht after installation of SP2 few of the DLL left unregistered.

Registered the DTS.DLL and it work like charm.

"C:\Program Files\Microsoft SQL Server\90\DTS\Binn>regsvr32 dts.dll"

Hope this help to others.

sql

cannot drop transactional subscription

My publisher server crashed and will not be coming back. I have to turn one
of the subscribing servers into the new publisher, but it still thinks it's
subscriber to the publisher that crashed.
Documentation says you can only drop the subscriptions from the publisher?
Now what?
JD,
running sp_removedbreplication should remove any remaining references.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Why do you say the subscriber cum publisher still thinks it is the
subscriber? What is the error message you are getting?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"JD" <JD@.discussions.microsoft.com> wrote in message
news:66F31D84-0CEA-49C0-8A5D-970821275954@.microsoft.com...
> My publisher server crashed and will not be coming back. I have to turn
one
> of the subscribing servers into the new publisher, but it still thinks
it's
> subscriber to the publisher that crashed.
> Documentation says you can only drop the subscriptions from the
publisher?
> Now what?
sql

Sunday, March 11, 2012

Cannot create ADO connection to DB anymore...

I rebuilt my machine a few weeks back - re-installed the developer version...

The app in question can see all it's tables in the SQL back end via ODBC and
everything looks normal via Enterprise Manager, but I can no longer create
an ADO Connection.

Source code is unchanged, what's changed is the PC rebuild and consequent
re-installatin of SQL Server developer version.

I suspect it's something to do with the provider (at least that's the only thing
I can see in the .Connect string that's not verifiably correct...)

The error looks like this after I trap and format it:

--------------------
12/30/03 21:34:30v0.71 Userid: UPQC on SAG
Proc: basADO: ADO_ConnectionCreate
-2147467259: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does
not exist or access denied.
Errors encountered when trying to connect:
'''[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied.

----Connect String:
Provider=SQLOLEDB.1;SERVER=SAG;DATABASE=TRETS;UID= Trets;PWD=trets
--------------------

Can anybody see anything obvious to look for?

I'm thinking I need to know how to verify/validate the presence of provider
"SQLOLEDB.1"... But how?
--
PeteCresswellHi

Maybe it's a SID type problem! Have you tried a trusted connection?

John

"(Pete Cresswell)" <x@.y.z> wrote in message
news:lkd4vv89m3cdb5fnlt4rt661c47sb56jdv@.4ax.com...
> I rebuilt my machine a few weeks back - re-installed the developer
version...
> The app in question can see all it's tables in the SQL back end via ODBC
and
> everything looks normal via Enterprise Manager, but I can no longer create
> an ADO Connection.
> Source code is unchanged, what's changed is the PC rebuild and consequent
> re-installatin of SQL Server developer version.
> I suspect it's something to do with the provider (at least that's the only
thing
> I can see in the .Connect string that's not verifiably correct...)
> The error looks like this after I trap and format it:
> --------------------
> 12/30/03 21:34:30v0.71 Userid: UPQC on SAG
> Proc: basADO: ADO_ConnectionCreate
> -2147467259: [DBNETLIB][ConnectionOpen (Connect()).]SQL
Server does
> not exist or access denied.
> Errors encountered when trying to connect:
> '''[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist
or
> access denied.
> ----Connect String:
> Provider=SQLOLEDB.1;SERVER=SAG;DATABASE=TRETS;UID= Trets;PWD=trets
> --------------------
>
> Can anybody see anything obvious to look for?
> I'm thinking I need to know how to verify/validate the presence of
provider
> "SQLOLEDB.1"... But how?
> --
> PeteCresswell

Thursday, March 8, 2012

Cannot create a connection to data source 'dataSource1'.

I am getting this error from Report Builder
Cannot create a connection to data source 'dataSource1'.
Back end SQL 2000
Credentials stored securely in the report server
Login and password of the SQL login
The weird thing is pointing to another db on the same server works fine
--
Peter
Peter.freeborn@.halliburton.comHope you have created Report model, If not use report model to access reports
from builder.
If you have already created it check the datasource "test connection" in the
report model project.
If you are accessing directly from builder using "open report server file",
dont do it cause it will ask for datasource which you cannt include. So
create a model and then access.
Amarnath
"Peter" wrote:
> I am getting this error from Report Builder
> Cannot create a connection to data source 'dataSource1'.
> Back end SQL 2000
> Credentials stored securely in the report server
> Login and password of the SQL login
> The weird thing is pointing to another db on the same server works fine
>
> --
> Peter
> Peter.freeborn@.halliburton.com|||I've struck this problem, I did some digging around and it seems that this is
a problem with kerberos security. Basically if you store the credentials in
the report server then the report server can pass the credentials fine,
however on a remote server it can't unless you've set up kerberos and use
windows security.
Thats my understanding of the problem, however the error message doesn't
really lead you in that direction.
HTH
"Peter" wrote:
> I am getting this error from Report Builder
> Cannot create a connection to data source 'dataSource1'.
> Back end SQL 2000
> Credentials stored securely in the report server
> Login and password of the SQL login
> The weird thing is pointing to another db on the same server works fine
>
> --
> Peter
> Peter.freeborn@.halliburton.com

Cannot create a connection to data source

When I log onto my test report services 2005 I can run this report fine after deploying it using IE on the reportserver. However when I go back to my own PC, I get this error when trying to access the report from my PC browser:

  • An error has occurred during report processing.
  • Cannot create a connection to data source 'MBNATEST'.
  • For more information about this error navigate to the report server on the local server machine, or enable remote errorsnevermind, figured it out myself:

    In Report Manager

    1) Click on Properties
    2) Click on Data Sources
    3) Make your Data Source Shared

  •