SQL server connection: message

Showing posts with label message. Show all posts

Monday, March 19, 2012

Another Sql 2005 Express Installation Problem

I am receiving the following message when trying to install Sql Server 2005 Express: "An installation package for the product Microsoft Sql Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'. I have verified that the sqlncli.mis file is included in the file being extracted by the installer and I have redownloaded the installation program 3 times from the MSDN site in case the file was corrupt.

Any ideas?I was able to solve my own problem by copying the 'sqlncli.msi' file to another folder during the failed installation.

Then after the failed installation I ran the sqlncli.msi by itself and it installed the Sql Native Client on its own just fine.

Then I ran the installation again and it made it past this point fine and completed the rest of the installation successfully.

This was on a Win2000 Professional machine. I am leaving this post here just in case anyone else runs across this.|||

Thanks a lot man "Johansec".

Your solution worked for me.

Another Sql 2005 Express Installation Problem

Any ideas?I was able to solve my own problem by copying the 'sqlncli.msi' file to another folder during the failed installation.

Then after the failed installation I ran the sqlncli.msi by itself and it installed the Sql Native Client on its own just fine.

Then I ran the installation again and it made it past this point fine and completed the rest of the installation successfully.

This was on a Win2000 Professional machine. I am leaving this post here just in case anyone else runs across this.|||

Thanks a lot man "Johansec".

Your solution worked for me.

Sunday, March 11, 2012

Another profiler question

This is a multi-part message in MIME format.
--=_NextPart_000_006D_01C654BC.18062AC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The first time I posted it landed under someone else's thread & I wasn't = sure anyone would see it to help me out.
I have a database that's being restored on a monthly basis, but I think = this process is overkill.
The users are using a few tables or whatever to run reports using = Crystal Reports, and accessing tables via MS Access.
What do I profile for to 'see' everything that is being used in this = database so that I can restore only these objects as opposed to the = entire db?
I have only used profiler to do some query statement troubleshooting, = 'Stored Procedure Compelted', but other than that am not proficient with = profiler.
All suggestions are greatly appreciated!!!!
--=_NextPart_000_006D_01C654BC.18062AC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
The first time I posted it landed under = someone else's thread & I wasn't sure anyone would see it to help me = out.

I have a database that's being restored on a = monthly basis, but I think this process is overkill.

The users are using a few tables or whatever = to run reports using Crystal Reports, and accessing tables via MS = Access.

What do I profile for to 'see' everything = that is being used in this database so that I can restore only these objects as = opposed to the entire db?

I have only used profiler to do some query = statement troubleshooting, 'Stored Procedure Compelted', but other than that am = not proficient with profiler.

All suggestions are greatly appreciated!!!!

--=_NextPart_000_006D_01C654BC.18062AC0--How big is your database? If it's small, restoring the database for reporting
may not be a bad practice. Note that you can't just 'restore only these
objects' from the database backup file if you are using SQL Server native
restore.
Linchi
"Jude" wrote:
> The first time I posted it landed under someone else's thread & I wasn't sure anyone would see it to help me out.
> I have a database that's being restored on a monthly basis, but I think this process is overkill.
> The users are using a few tables or whatever to run reports using Crystal Reports, and accessing tables via MS Access.
> What do I profile for to 'see' everything that is being used in this database so that I can restore only these objects as opposed to the entire db?
> I have only used profiler to do some query statement troubleshooting, 'Stored Procedure Compelted', but other than that am not proficient with profiler.
> All suggestions are greatly appreciated!!!!
>|||Actually I am not using Sql Server Native backup software & I do have an
option of restoring single objects.
But to be perfectly honest I didn't want to debate the point, I want to
learn about using profiler to effectively capture this information and
suppose I was looking for a quick answer.
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:FAD6A024-8973-4AFC-8F28-75B5ADC2B618@.microsoft.com...
> How big is your database? If it's small, restoring the database for
> reporting
> may not be a bad practice. Note that you can't just 'restore only these
> objects' from the database backup file if you are using SQL Server native
> restore.
> Linchi
> "Jude" wrote:
>> The first time I posted it landed under someone else's thread & I wasn't
>> sure anyone would see it to help me out.
>> I have a database that's being restored on a monthly basis, but I think
>> this process is overkill.
>> The users are using a few tables or whatever to run reports using Crystal
>> Reports, and accessing tables via MS Access.
>> What do I profile for to 'see' everything that is being used in this
>> database so that I can restore only these objects as opposed to the
>> entire db?
>> I have only used profiler to do some query statement troubleshooting,
>> 'Stored Procedure Compelted', but other than that am not proficient with
>> profiler.
>> All suggestions are greatly appreciated!!!!
>>

Thursday, March 8, 2012

Another merge agent for the subscription is running

When trying to replicate I get the message "Another merge agent for the
subscription(s) is running."
Both publisher/distributor and subscriber are SQL2K SP3.
There is no orphan process for the agent in the sysprocesses table.
I monitored the sysprocesses while the agent is connecting: for few
seconds several processes added to the list with the host name of the
subscriber, all start and gone in the same time, and then I get the
message above.
Please help
Yes, the ActiveX is in use, but only it. No other agent for the
subscription is running.
The publication was created by hand with the wizard.
Rgds,
Orr
Paul Ibison wrote:
> It doesn't sound as though this applies, but have you
> used the ActiveX control or windows synchronization
> manager to initiate a pull when the merge agent was
> already running? Was your publication created by hand
> from scripts?
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
|||Problem solved!
The application that is using the ActiveX was started twice
automatically when computer booted.
Thanks,
Orr

Another distribution agents for the Subcription

sql2k sp3

Im getting a message on replication that has been running
for a while:

Another distribution agent for the subscription(s) is
running. NOTE: The step was retried the requested number
of times (10) without succeeding. The step failed.

Any ideas?

ThanksOriginally posted by dschuster
sql2k sp3

Im getting a message on replication that has been running
for a while:

Another distribution agent for the subscription(s) is
running. NOTE: The step was retried the requested number
of times (10) without succeeding. The step failed.

Any ideas?

Thanks

What this means is that another replication step is running while this step was executed. Check all the steps that are Running in Replication Monitor -> Publishers/Subscribers and check if any other steps are running. If they are then you will have either wait for them to be done or you can force them to stop. Once all the steps are stopped then you can run your replication step.

Hope this helps

Wednesday, March 7, 2012

Another cryptic message from SQL 2005 SSIS

It reminds me of the "opearation was successful the patient died" scenario.

Compare this to the SSIS Error message:

The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

SSIS package "myPubs.dtsx" finished: Failure.

Why can't they write meaningful messages?

YOu need enable the logging for SSIS packages in order to see what was that error : http://www.databasejournal.com/features/mssql/article.php/3562406 fyi.|||Did they fix this bug finally?|||

I forgot to indicate my blog entry for this:

http://hodentek.blogspot.com/2007/03/ssis-migration-fiasco.html

|||

I was actaully trying to find an answer for the question I posted:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1393552&SiteID=1

Please forgive.

|||Moved this thread from SQL Server Tools General to the SSIS forum.

You should know that your error likely has to do with the ProtectionLevel property of the package. Right click on the control flow and select properties. What is it set to?|||

Jayaram Krishnaswamy wrote:
Did they fix this bug finally?

What bug? I don't believe there is a bug here, rather I think there is a lack of understanding of how differently SSIS operates compared to DTS.|||

Reply was not helpful.

Tried all options (somewhat unprofessional, fortunately fewer options). The same result.

Details follow:

Protection Level of package:

DontSaveSensitive: failed

Warning: 0x80019002 at myPubs: The Execution method succeeded, but the number of errors raised (4) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "myPubs.dtsx" finished: Failure.

EncryptSensitiveWithPassowrd: failed

Provided a password for the package, myPubs.dtsx.

SSIS package "myPubs.dtsx" starting.
Error: 0xC002F325 at Copy SQL Server Objects, Transfer SQL Server Objects Task: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".
Task failed: Copy SQL Server Objects
Warning: 0x80019002 at myPubs: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "myPubs.dtsx" finished: Failure.

EncryptAllwithPassword:failed
failed
SSIS package "myPubs.dtsx" starting.
Error: 0xC002F325 at Copy SQL Server Objects, Transfer SQL Server Objects Task: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".
Task failed: Copy SQL Server Objects
Warning: 0x80019002 at myPubs: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "myPubs.dtsx" finished: Failure.

EncryptAllwithUserkey:failed (ola didn't ask for a key or anything, it must have assumed some default)

ServerStorage: failed
TITLE: Microsoft Visual Studio

Failure saving package.

ADDITIONAL INFORMATION:

Failed to apply package protection with error 0xC0014061 "The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the destination supports secure storage capability.". This error occurs when saving to Xml.
(myPubs)

BUTTONS:

Open for suggestions

|||Try EncryptSensitiveWithUserKey and then go back in and retype in your credentials for the connections. Make sure you check the save password box.|||

Jayaram Krishnaswamy wrote:

I forgot to indicate my blog entry for this:

http://hodentek.blogspot.com/2007/03/ssis-migration-fiasco.html

You haven't understood the inherent differences between SSIS and DTS. SSIS is a much more secure environment and will not allow you to store passwords with the same freedom as DTS did. Can I politely suggest that you familiarise yourself totally with this new tool before you start to blog about it and thus post inaccurate information. You are not helping the SSIS community by doing so.

-Jamie

|||If the number of people reporting this is large surely somebody should take the responsibility of putting the matter to rest. This is probably one of the problems with proprietary software.|||

Jayaram Krishnaswamy wrote:
If the number of people reporting this is large surely somebody should take the responsibility of putting the matter to rest. This is probably one of the problems with proprietary software.

REPORTING WHAT, *exactly*?

WHAT *IS* THE PROBLEM?|||

Jayaram Krishnaswamy wrote:
If the number of people reporting this is large surely somebody should take the responsibility of putting the matter to rest. This is probably one of the problems with proprietary software.

huh?

If SSIS is proprietary software then show me some software that ISN'T proprietary.

I haven't seen anyone else on this thread reporting any problem, only you. In fact, you haven't actually articulated a problem as far as I can see. In summary, what is the prolem that you speak of?

-Jamie

|||

Phil Brammer wrote:
Try EncryptSensitiveWithUserKey and then go back in and retype in your credentials for the connections. Make sure you check the save password box.

This did not help in my case.

Jayaram, have you resolved this problem finally?

|||

Dan Miniyarov wrote:

Phil Brammer wrote:
Try EncryptSensitiveWithUserKey and then go back in and retype in your credentials for the connections. Make sure you check the save password box.

This did not help in my case.
Jayaram, have you resolved this problem finally?

I don't know what that means. What exactly is your issue? What are you trying to achieve?

Another cryptic message from SQL 2005 SSIS

It reminds me of the "opearation was successful the patient died" scenario.

Compare this to the SSIS Error message:

SSIS package "myPubs.dtsx" finished: Failure.

Why can't they write meaningful messages?

YOu need enable the logging for SSIS packages in order to see what was that error : http://www.databasejournal.com/features/mssql/article.php/3562406 fyi.|||Did they fix this bug finally?|||

I forgot to indicate my blog entry for this:

http://hodentek.blogspot.com/2007/03/ssis-migration-fiasco.html

|||

I was actaully trying to find an answer for the question I posted:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1393552&SiteID=1

Please forgive.

|||Moved this thread from SQL Server Tools General to the SSIS forum.

You should know that your error likely has to do with the ProtectionLevel property of the package. Right click on the control flow and select properties. What is it set to?|||

Jayaram Krishnaswamy wrote:
Did they fix this bug finally?

What bug? I don't believe there is a bug here, rather I think there is a lack of understanding of how differently SSIS operates compared to DTS.|||

Reply was not helpful.

Tried all options (somewhat unprofessional, fortunately fewer options). The same result.

Details follow:

Protection Level of package:

DontSaveSensitive: failed

EncryptSensitiveWithPassowrd: failed

Provided a password for the package, myPubs.dtsx.

EncryptAllwithUserkey:failed (ola didn't ask for a key or anything, it must have assumed some default)

ServerStorage: failed
TITLE: Microsoft Visual Studio

Failure saving package.

ADDITIONAL INFORMATION:

BUTTONS:

Open for suggestions

|||Try EncryptSensitiveWithUserKey and then go back in and retype in your credentials for the connections. Make sure you check the save password box.|||

Jayaram Krishnaswamy wrote:
I forgot to indicate my blog entry for this:
http://hodentek.blogspot.com/2007/03/ssis-migration-fiasco.html

-Jamie

|||If the number of people reporting this is large surely somebody should take the responsibility of putting the matter to rest. This is probably one of the problems with proprietary software.|||

Jayaram Krishnaswamy wrote:
If the number of people reporting this is large surely somebody should take the responsibility of putting the matter to rest. This is probably one of the problems with proprietary software.

REPORTING WHAT, *exactly*?

WHAT *IS* THE PROBLEM?|||

Jayaram Krishnaswamy wrote:
If the number of people reporting this is large surely somebody should take the responsibility of putting the matter to rest. This is probably one of the problems with proprietary software.

huh?

If SSIS is proprietary software then show me some software that ISN'T proprietary.

I haven't seen anyone else on this thread reporting any problem, only you. In fact, you haven't actually articulated a problem as far as I can see. In summary, what is the prolem that you speak of?

-Jamie

|||

Phil Brammer wrote:
Try EncryptSensitiveWithUserKey and then go back in and retype in your credentials for the connections. Make sure you check the save password box.

This did not help in my case.

Jayaram, have you resolved this problem finally?|||

Dan Miniyarov wrote:
Phil Brammer wrote:
Try EncryptSensitiveWithUserKey and then go back in and retype in your credentials for the connections. Make sure you check the save password box.

This did not help in my case.
Jayaram, have you resolved this problem finally?

I don't know what that means. What exactly is your issue? What are you trying to achieve?

Another cryptic message from SQL 2005 SSIS

It reminds me of the "opearation was successful the patient died" scenario.

Compare this to the SSIS Error message:

SSIS package "myPubs.dtsx" finished: Failure.

Why can't they write meaningful messages?

YOu need enable the logging for SSIS packages in order to see what was that error : http://www.databasejournal.com/features/mssql/article.php/3562406 fyi.|||Did they fix this bug finally?|||

I forgot to indicate my blog entry for this:

http://hodentek.blogspot.com/2007/03/ssis-migration-fiasco.html

|||

I was actaully trying to find an answer for the question I posted:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1393552&SiteID=1

Please forgive.

|||Moved this thread from SQL Server Tools General to the SSIS forum.

You should know that your error likely has to do with the ProtectionLevel property of the package. Right click on the control flow and select properties. What is it set to?|||

Jayaram Krishnaswamy wrote:
Did they fix this bug finally?

What bug? I don't believe there is a bug here, rather I think there is a lack of understanding of how differently SSIS operates compared to DTS.|||

Reply was not helpful.

Tried all options (somewhat unprofessional, fortunately fewer options). The same result.

Details follow:

Protection Level of package:

DontSaveSensitive: failed

EncryptSensitiveWithPassowrd: failed

Provided a password for the package, myPubs.dtsx.

EncryptAllwithUserkey:failed (ola didn't ask for a key or anything, it must have assumed some default)

ServerStorage: failed
TITLE: Microsoft Visual Studio

Failure saving package.

ADDITIONAL INFORMATION:

BUTTONS:

Open for suggestions

|||Try EncryptSensitiveWithUserKey and then go back in and retype in your credentials for the connections. Make sure you check the save password box.|||

Jayaram Krishnaswamy wrote:

I forgot to indicate my blog entry for this:

http://hodentek.blogspot.com/2007/03/ssis-migration-fiasco.html

-Jamie

|||If the number of people reporting this is large surely somebody should take the responsibility of putting the matter to rest. This is probably one of the problems with proprietary software.|||

Jayaram Krishnaswamy wrote:
If the number of people reporting this is large surely somebody should take the responsibility of putting the matter to rest. This is probably one of the problems with proprietary software.

REPORTING WHAT, *exactly*?

WHAT *IS* THE PROBLEM?|||

Jayaram Krishnaswamy wrote:
If the number of people reporting this is large surely somebody should take the responsibility of putting the matter to rest. This is probably one of the problems with proprietary software.

huh?

If SSIS is proprietary software then show me some software that ISN'T proprietary.

I haven't seen anyone else on this thread reporting any problem, only you. In fact, you haven't actually articulated a problem as far as I can see. In summary, what is the prolem that you speak of?

-Jamie

|||

Phil Brammer wrote:
Try EncryptSensitiveWithUserKey and then go back in and retype in your credentials for the connections. Make sure you check the save password box.

This did not help in my case.

Jayaram, have you resolved this problem finally?

|||

Dan Miniyarov wrote:

Phil Brammer wrote:
Try EncryptSensitiveWithUserKey and then go back in and retype in your credentials for the connections. Make sure you check the save password box.

This did not help in my case.
Jayaram, have you resolved this problem finally?

I don't know what that means. What exactly is your issue? What are you trying to achieve?

Saturday, February 25, 2012

annoying SQL Server error message

Hi,
We have developped many applications, for a major customer, connected
to the same SQL Server database. Those apps have been programmed in VB6
and VB.NET. The SQL Server is located on a dual-processor server,
running Windows 2000 Server, with 3 gigs RAM. The apps are installed on
Windows 2000 and Windows XP/SP2 client.
And the Windows 2000 client PC's, there is no problem at all. But, on
the XPs, we have, this error message popup: "Unable to load SQL Server
OLEDB provider ressource DLL. The application cannot continue". Look
like it appears randomly.
The same application, when installed on a Win2000, don't have any
problem at all. Just the damn XP machines. We cannot change the OS of
these PC's (enterprise rules).
This error is a major problem because it stops the application until
you acknowledge the error. The app is used for realtime control of a
factory, so, you see the problem...
XP workstation uses MDAC 2.8 SP1 for Windows XP SP2
2000 uses MDAC 2.6 RTM
Apps has been compiled on a MDAC 2.8 SP1 Win XP SP2 computer
How can I fix this?
thanks a lot for your help, it's really appreciated.
1)Have you got the latest MDAC installation ?
2)Track down all instances of sqloledb.rll and sqloledb.dll . Make sure
they are the latest versions and match up
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
"Dominic30" <gagned@.videotron.ca> wrote in message
news:1142610474.169168.15240@.i40g2000cwc.googlegro ups.com...
> Hi,
> We have developped many applications, for a major customer, connected
> to the same SQL Server database. Those apps have been programmed in VB6
> and VB.NET. The SQL Server is located on a dual-processor server,
> running Windows 2000 Server, with 3 gigs RAM. The apps are installed on
> Windows 2000 and Windows XP/SP2 client.
> And the Windows 2000 client PC's, there is no problem at all. But, on
> the XPs, we have, this error message popup: "Unable to load SQL Server
> OLEDB provider ressource DLL. The application cannot continue". Look
> like it appears randomly.
> The same application, when installed on a Win2000, don't have any
> problem at all. Just the damn XP machines. We cannot change the OS of
> these PC's (enterprise rules).
> This error is a major problem because it stops the application until
> you acknowledge the error. The app is used for realtime control of a
> factory, so, you see the problem...
> XP workstation uses MDAC 2.8 SP1 for Windows XP SP2
> 2000 uses MDAC 2.6 RTM
> Apps has been compiled on a MDAC 2.8 SP1 Win XP SP2 computer
> How can I fix this?
> thanks a lot for your help, it's really appreciated.
>
|||1) Yeah, I've got the latest MDAC installation. Anyway, I can't
installed another MDAC version on the XP machines, the install failed.
2) These files match up yes. I've checked all the station and it's
looks fine.
any more idea?
by the way, thanks for the reply
|||In what path is the SQLOLEDB.RLL file ?
You mention that all the apps are using the same sql server. Is this though
Linked Servers?
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
"Dominic30" <gagned@.videotron.ca> wrote in message
news:1142613417.547606.39710@.z34g2000cwc.googlegro ups.com...
> 1) Yeah, I've got the latest MDAC installation. Anyway, I can't
> installed another MDAC version on the XP machines, the install failed.
> 2) These files match up yes. I've checked all the station and it's
> looks fine.
> any more idea?
> by the way, thanks for the reply
>

annoying SQL Server error message

Hi,
We have developped many applications, for a major customer, connected
to the same SQL Server database. Those apps have been programmed in VB6
and VB.NET. The SQL Server is located on a dual-processor server,
running Windows 2000 Server, with 3 gigs RAM. The apps are installed on
Windows 2000 and Windows XP/SP2 client.
And the Windows 2000 client PC's, there is no problem at all. But, on
the XPs, we have, this error message popup: "Unable to load SQL Server
OLEDB provider ressource DLL. The application cannot continue". Look
like it appears randomly.
The same application, when installed on a Win2000, don't have any
problem at all. Just the damn XP machines. We cannot change the OS of
these PC's (enterprise rules).
This error is a major problem because it stops the application until
you acknowledge the error. The app is used for realtime control of a
factory, so, you see the problem...
XP workstation uses MDAC 2.8 SP1 for Windows XP SP2
2000 uses MDAC 2.6 RTM
Apps has been compiled on a MDAC 2.8 SP1 Win XP SP2 computer
How can I fix this'
thanks a lot for your help, it's really appreciated.1)Have you got the latest MDAC installation ?
2)Track down all instances of sqloledb.rll and sqloledb.dll . Make sure
they are the latest versions and match up
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
"Dominic30" <gagned@.videotron.ca> wrote in message
news:1142610474.169168.15240@.i40g2000cwc.googlegroups.com...
> Hi,
> We have developped many applications, for a major customer, connected
> to the same SQL Server database. Those apps have been programmed in VB6
> and VB.NET. The SQL Server is located on a dual-processor server,
> running Windows 2000 Server, with 3 gigs RAM. The apps are installed on
> Windows 2000 and Windows XP/SP2 client.
> And the Windows 2000 client PC's, there is no problem at all. But, on
> the XPs, we have, this error message popup: "Unable to load SQL Server
> OLEDB provider ressource DLL. The application cannot continue". Look
> like it appears randomly.
> The same application, when installed on a Win2000, don't have any
> problem at all. Just the damn XP machines. We cannot change the OS of
> these PC's (enterprise rules).
> This error is a major problem because it stops the application until
> you acknowledge the error. The app is used for realtime control of a
> factory, so, you see the problem...
> XP workstation uses MDAC 2.8 SP1 for Windows XP SP2
> 2000 uses MDAC 2.6 RTM
> Apps has been compiled on a MDAC 2.8 SP1 Win XP SP2 computer
> How can I fix this'
> thanks a lot for your help, it's really appreciated.
>|||1) Yeah, I've got the latest MDAC installation. Anyway, I can't
installed another MDAC version on the XP machines, the install failed.
2) These files match up yes. I've checked all the station and it's
looks fine.
any more idea?
by the way, thanks for the reply|||In what path is the SQLOLEDB.RLL file ?
You mention that all the apps are using the same sql server. Is this though
Linked Servers?
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
"Dominic30" <gagned@.videotron.ca> wrote in message
news:1142613417.547606.39710@.z34g2000cwc.googlegroups.com...
> 1) Yeah, I've got the latest MDAC installation. Anyway, I can't
> installed another MDAC version on the XP machines, the install failed.
> 2) These files match up yes. I've checked all the station and it's
> looks fine.
> any more idea?
> by the way, thanks for the reply
>

annoying SQL Server error message

Hi,
We have developped many applications, for a major customer, connected
to the same SQL Server database. Those apps have been programmed in VB6
and VB.NET. The SQL Server is located on a dual-processor server,
running Windows 2000 Server, with 3 gigs RAM. The apps are installed on
Windows 2000 and Windows XP/SP2 client.
And the Windows 2000 client PC's, there is no problem at all. But, on
the XPs, we have, this error message popup: "Unable to load SQL Server
OLEDB provider ressource DLL. The application cannot continue". Look
like it appears randomly.
The same application, when installed on a Win2000, don't have any
problem at all. Just the damn XP machines. We cannot change the OS of
these PC's (enterprise rules).
This error is a major problem because it stops the application until
you acknowledge the error. The app is used for realtime control of a
factory, so, you see the problem...
XP workstation uses MDAC 2.8 SP1 for Windows XP SP2
2000 uses MDAC 2.6 RTM
Apps has been compiled on a MDAC 2.8 SP1 Win XP SP2 computer
How can I fix this'
thanks a lot for your help, it's really appreciated.1)Have you got the latest MDAC installation ?
2)Track down all instances of sqloledb.rll and sqloledb.dll . Make sure
they are the latest versions and match up
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
"Dominic30" <gagned@.videotron.ca> wrote in message
news:1142610474.169168.15240@.i40g2000cwc.googlegroups.com...
> Hi,
> We have developped many applications, for a major customer, connected
> to the same SQL Server database. Those apps have been programmed in VB6
> and VB.NET. The SQL Server is located on a dual-processor server,
> running Windows 2000 Server, with 3 gigs RAM. The apps are installed on
> Windows 2000 and Windows XP/SP2 client.
> And the Windows 2000 client PC's, there is no problem at all. But, on
> the XPs, we have, this error message popup: "Unable to load SQL Server
> OLEDB provider ressource DLL. The application cannot continue". Look
> like it appears randomly.
> The same application, when installed on a Win2000, don't have any
> problem at all. Just the damn XP machines. We cannot change the OS of
> these PC's (enterprise rules).
> This error is a major problem because it stops the application until
> you acknowledge the error. The app is used for realtime control of a
> factory, so, you see the problem...
> XP workstation uses MDAC 2.8 SP1 for Windows XP SP2
> 2000 uses MDAC 2.6 RTM
> Apps has been compiled on a MDAC 2.8 SP1 Win XP SP2 computer
> How can I fix this'
> thanks a lot for your help, it's really appreciated.
>|||1) Yeah, I've got the latest MDAC installation. Anyway, I can't
installed another MDAC version on the XP machines, the install failed.
2) These files match up yes. I've checked all the station and it's
looks fine.
any more idea?
by the way, thanks for the reply|||In what path is the SQLOLEDB.RLL file ?
You mention that all the apps are using the same sql server. Is this though
Linked Servers?
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
"Dominic30" <gagned@.videotron.ca> wrote in message
news:1142613417.547606.39710@.z34g2000cwc.googlegroups.com...
> 1) Yeah, I've got the latest MDAC installation. Anyway, I can't
> installed another MDAC version on the XP machines, the install failed.
> 2) These files match up yes. I've checked all the station and it's
> looks fine.
> any more idea?
> by the way, thanks for the reply
>

Annoying Error Message

Hello,

I recently migrated from 2000 to 2005 database. On the new server, I kept getting this type of error message when there is some sort of join involved and they are not complex join either.

Error - "A severe error occurred on the current command. The results, if any, should be discarded."

select A.Cookie1, A.Cookie2
into BookersLookers_Cookie
from BookersLookers_DataSet A
LEFT JOIN ActionSetup B on A.ActionID = B.ActionID
group by A.Cookie1, A.Cookie2

Is there something in the code where I could prevent this error from happening?

Any insight is appreciated,

-Lawrence

Moving to engine forum|||

Hi SQLChamp,

What is the build of your SQL server?

What is the exact error message you are getting?

Any errors in theerror log?

Jag

|||

Hello Jag Sandhu,

What is the build of your SQL server? 9.00.3042 (X64)

What is the exact error message you are getting? "A severe error occurred on the current command. The results, if any, should be discarded."

Any errors in theerror log? no error log set up

-Lawrence

|||

You encounter an old bug which should have been fixed if you're running sp2.

http://support.microsoft.com/default.aspx/kb/910416

The error log we're interested in is the sql log. You can get it by executing the following sproc.

exec sp_readerrorlog

Please post the result of "select @.@.version" while you're at it.

|||

I posted select @.@.version earlier - 9.00.3042 (X64)

I would find out any logs from sp_readerrorlog

If all else fails, I guess this is a big bug, and hopefully SP2 will fix it.

-Lawrence

|||

From your buildnumber it seems like you are running SP2 already.

Let us know what you get from error logs.

Jag

|||

Hello,

I received the following error message from sp_readerrorlop

2007-04-30 12:51:18.620 Server Error: 17310, Severity: 20, State: 1.

2007-04-30 12:51:18.620 Server A user request from the session with SPID 57 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.

|||

You should probably do what the message says.

Contact Product Support Services with the dump produced in the log directory.

Or possibly post the .mdmp file on Connect for analysis.

|||

I was wondering if anyone had a fix for this type of error/bug? Any hotfx or work-around?

Our IT Support contacted MS, but MS Production Support is not very responsive in this case. "Severe Error" still occurs in simple join. Any additional help would be much appreciated.

Sincerely,

-Lawrence

|||

SP1 works fine, so I would NOT recommend applying SP2.

-Lawrence

Annoying Error Message

Hello,

I recently migrated from 2000 to 2005 database. On the new server, I kept getting this type of error message when there is some sort of join involved and they are not complex join either.

Error - "A severe error occurred on the current command. The results, if any, should be discarded."

select A.Cookie1, A.Cookie2
into BookersLookers_Cookie
from BookersLookers_DataSet A
LEFT JOIN ActionSetup B on A.ActionID = B.ActionID
group by A.Cookie1, A.Cookie2

Is there something in the code where I could prevent this error from happening?

Any insight is appreciated,

-Lawrence

Moving to engine forum|||

Hi SQLChamp,

What is the build of your SQL server?

What is the exact error message you are getting?

Any errors in theerror log?

Jag

|||

Hello Jag Sandhu,

What is the build of your SQL server? 9.00.3042 (X64)

What is the exact error message you are getting? "A severe error occurred on the current command. The results, if any, should be discarded."

Any errors in theerror log? no error log set up

-Lawrence

|||

You encounter an old bug which should have been fixed if you're running sp2.

http://support.microsoft.com/default.aspx/kb/910416

The error log we're interested in is the sql log. You can get it by executing the following sproc.

exec sp_readerrorlog

Please post the result of "select @.@.version" while you're at it.

|||

I posted select @.@.version earlier - 9.00.3042 (X64)

I would find out any logs from sp_readerrorlog

If all else fails, I guess this is a big bug, and hopefully SP2 will fix it.

-Lawrence

|||

From your buildnumber it seems like you are running SP2 already.

Let us know what you get from error logs.

Jag

|||

Hello,

I received the following error message from sp_readerrorlop

2007-04-30 12:51:18.620 Server Error: 17310, Severity: 20, State: 1.

|||

You should probably do what the message says.

Contact Product Support Services with the dump produced in the log directory.

Or possibly post the .mdmp file on Connect for analysis.

|||

I was wondering if anyone had a fix for this type of error/bug? Any hotfx or work-around?

Our IT Support contacted MS, but MS Production Support is not very responsive in this case. "Severe Error" still occurs in simple join. Any additional help would be much appreciated.

Sincerely,

-Lawrence

|||

SP1 works fine, so I would NOT recommend applying SP2.

-Lawrence

Friday, February 24, 2012

And here is part of the installation log...

I get to the point of starting the services and receive the following message after about 4 minutes of trying to start. I tried in Mixed Mode and Windows Authentication Mode. Message:

TITLE: Microsoft SQL Server 2005 Setup

The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=29503&EvtType=sqlsetuplib%5cservice.cpp%40Do_sqlScript%40sqls%3a%3aService%3a%3aWaitForServiceState%40x41d

BUTTONS:

&Retry
Cancel

YOu need do have a look in the WIndows event log or in the log files of SQL Server mentioned. There is a problem starting the service, the message that you provided is just a generic one which doesn′t tell the specific error.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||I can find nothing useful in the Windows event log and I guess I do not understand where the sql server log files are.|||For me its located in here:

C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\LOG

Could be something different for you depending on your installation.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

here is the log contents of the last attempted installation and of course it timed out while trying to start the service:

2006-05-28 07:37:06.92 Server Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86)

Apr 14 2006 01:12:25

Express Edition with Advanced Services on Windows NT 5.1 (Build 2600: Service Pack 2)

2006-05-28 07:37:06.92 Server Server process ID is 4776.

2006-05-28 07:37:06.92 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.

2006-05-28 07:37:06.94 Server Registry startup parameters:

2006-05-28 07:37:06.94 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

2006-05-28 07:37:06.94 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

2006-05-28 07:37:06.94 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

2006-05-28 07:37:06.94 Server Command Line Startup Parameters:

2006-05-28 07:37:06.95 Server -m SqlSetup

2006-05-28 07:37:06.95 Server SqlSetup

2006-05-28 07:37:06.95 Server -Q

2006-05-28 07:37:06.95 Server -q SQL_Latin1_General_CP1_CI_AS

2006-05-28 07:37:06.95 Server -T 4022

2006-05-28 07:37:06.95 Server -T 3659

2006-05-28 07:37:06.95 Server -T 3610

2006-05-28 07:37:06.95 Server -T 4010

2006-05-28 07:37:06.98 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2006-05-28 07:37:06.98 Server Detected 1 CPUs. This is an informational message; no user action is required.

2006-05-28 07:40:49.72 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2006-05-28 07:40:50.88 Server Database Mirroring Transport is disabled in the endpoint configuration.

2006-05-28 07:59:24.50 Server Service control: stop before startup

|||

Thanks.....

Property(S): DatabaseReplRes.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:\Program Files\Common Files\Microsoft Shared\Database Replication\Resources\
Property(S): DatabaseReplRes1033.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:\Program Files\Common Files\Microsoft Shared\Database Replication\Resources\1033\
Property(S): SqlVerComBin.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = C:\Program Files\Microsoft SQL Server\90\COM\
Property(S): Ver.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = C:\Program Files\Microsoft SQL Server\90\
Property(S): SqlVerComBin.889BED4C_E3F4_4943_956C_6FFD882F721F = C:\Program Files\Microsoft SQL Server\90\COM\
Property(S): Ver.889BED4C_E3F4_4943_956C_6FFD882F721F = C:\Program Files\Microsoft SQL Server\90\
Property(S): SqlVerComBin.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:\Program Files\Microsoft SQL Server\90\COM\
Property(S): Ver.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:\Program Files\Microsoft SQL Server\90\
Property(S): SqlVerComBinRes.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:\Program Files\Microsoft SQL Server\90\COM\Resources\
Property(S): SqlVerComBinRes1033.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:\Program Files\Microsoft SQL Server\90\COM\Resources\1033\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer$SQLEXPRESS
Property(S): SqlActionManaged = 3
Property(S): SqlNamedInstance = 1
Property(S): SqlStateManaged = 2
Property(S): RSVirtualDirectoryManager = Reports$SQLEXPRESS
Property(S): SOURCEDIR = d:\69a81902561ca8c7a8df\Setup\
Property(S): SourcedirProduct = {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
Property(S): InstallNgenTicks = 110000
Property(S): SQLBROWSERSCMACCOUNT = NT AUTHORITY\NetworkService
Property(S): SQLSCMACCOUNT = NT AUTHORITY\NetworkService
Property(S): DebugClsid.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = {84AFA01D-0112-4F29-990C-7A3EECC00498}
Property(S): ProductToBeRegistered = 1
MSI (s) (EC:1C) [08:37:27:207]: Note: 1: 1708
MSI (s) (EC:1C) [08:37:27:207]: Product: Microsoft SQL Server 2005 Express Edition -- Installation failed.

MSI (s) (EC:1C) [08:37:27:227]: Cleaning up uninstalled install packages, if any exist
MSI (s) (EC:1C) [08:37:27:227]: MainEngineThread is returning 1603
MSI (s) (EC:5C) [08:37:27:337]: Destroying RemoteAPI object.
MSI (s) (EC:D8) [08:37:27:337]: Custom Action Manager thread ending.
=== Logging stopped: 5/28/2006 8:37:27 ===
MSI (c) (78:AC) [08:37:27:377]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (78:AC) [08:37:27:377]: MainEngineThread is returning 1603
=== Verbose logging stopped: 5/28/2006 8:37:27 ===

|||What service account are you using for the service. It could be that the service account used doesn′t have the appropiate permissions to start up SQL Server. Change that (e.g. to Local System) and see if a manual startup comes up successfull.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Thursday, February 16, 2012

Analysis Services started and then stopped, Event ID: 0xC1210000

I just installed SQL Server 2005 Developer Edition and SP1 and SP2. I cannot start Analysis Services. The message box states: The SQL Server Analysis Services (MSSQLSERVER) service on Local Computer started and then stopped. I looked in the log files located at: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Log and found these entries:

msmdsrv.log:

(6/15/2007 10:07:34 AM)
Message: The service cannot be started:
(Source: \\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Log\msmdsrv.log,
Type: 3, Category: 289, Event ID: 0xC1210000)
?(6/15/2007 10:10:26 AM) Message:
The service cannot be started:
(Source: \\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Log\msmdsrv.log,
Type: 3, Category: 289, Event ID: 0xC1210000)

During installation I did get an unhandled exception (I don't know what component caused the exception). I have found this in the SQLDUMPER_ERRORLOG.log file:

06/14/07 17:39:38, ERROR , msmdsrv.exe, Unable to open file C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\FlightRecorderCurrent.trc, error 2
06/14/07 17:39:38, ACTION, msmdsrv.exe, Watson Invoke: No

Any ideas how to get this service started?

I had the same problem as you discribed. Then I tried to reapply SP2. It works fine now.

I guess when you first applied SP2, analysis service was not installed and therefore the patch is not installed. Download the latest SP2 and try it again:

http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-8f0c-63fa18f26d3a&DisplayLang=en

good luck!

Monday, February 13, 2012

Analysis Services not Started!

Good Day!

I have installed SQL Server 2005

In services.msc SQL Server Analysis Services (MSSQLSERVER) can't be started.

Message: Service Started and then Stopped and

The service cannot be started: The following system error occurred: Only one usage of each socket address (protocol/network address/port) is normally permitted.

What is this?

Thanks...

Some application occupied AS TCP port. In case of default instance it would be 2383. Please run netstat or (even better) tcpmon to find out what this application is.|||

Wow.

It seems like SQL Analysis Services can't live with started SAP on the Machine.

What ports use Analysis Services?

|||

Default instance uses port 2383.

The redirector for named instances uses port 2382.

Ports for named instances can be manually overriden.

|||

Where can I change instance port for Analysis?

|||Server -> Properties -> Show All (advanced) properties -> Port|||

Mosha Pasumansky wrote:
Server -> Properties -> Show All (advanced) properties -> Port

Sorry for borring, I'm a novice.

Where is it? I'm going in Computer Managment -> SQL Server Configuration Manager -> SQL Server 2005 Services -> SQL Server Analysis Services ->Properties

But there nothing...

|||

You need to go to SQL Server Mgmt Studio> Connect to Analysis Services>Right Click on the server-> Hit Properties> Scroll down and check the box "Show Advanced(All) properties" and then you will see the property "Port"

Sunday, February 12, 2012

Analysis Services Connection problem

I can't connect to Analysis Services accroding execl
pivottable. The error message is "Unable to open
connection. Cannot connect to cube
file. '10.97.69.212',file may be in use." The TCP/IP is
well but the client is not a domain user.What is the
prolem? How to resolve it?Are you specifying an IP address instead of a computer name?
243093 FIX: Using an IP Address for OLAP Data Source Connection Property
Causes
http://support.microsoft.com/?id=243093
Are you going across domains? If so, you'll need to follow these
instructions:
280431 How to Enable Commerce Server 2000 OLAP Reports Over HTTPS with SQL
http://support.microsoft.com/?id=280431
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Thursday, February 9, 2012

Analysis Services 2005 OLE DB Provider Error

I try to open a SSAS Cube but I get a OLE DB error message below.

The same cube I can browse with the SQL Server Business Intelligence Development Studio.

Error message:

Microsoft OLE DB Provider for Analysis Services 2005 Microsoft OLE DB Provider for Analysis Services 2005 reported:

Errors in the OLE DB provider. Could not connect to the redirector. Ensure that the SQLBrowser service is running on the '<MY Server Name>' server. Errors in the OLE DB provider. An error occurred while named instance information was being retrieved from the SQLBrowser service on the '<MY Server Name>' server.

The SQL Browser is used when you are attempting to communicate with a named instance. What you are seeing is a known problem, fixed in SP1, where the SQL Browser needs communication with a domain controller to validate your access rights. This happens to me if I disconnect my laptop from the network and try an connect to a named instance on it. I've also seen it if the SQL Browser is running under a service account that isn't a machine administrator -- and third I've seen this if you are running under XP SP2 and the firewall is stopping your connectivity to the SQL Browser.

You have a few options: 1) make it the default instance -- that works without any problems, 2) always make sure a DC is available, 3) make sure the XP firewall is disabled on the SQL Browser port# (and the various instance port#s), 4) attempt to connect specifically to the port # for the instance (which bypasses the redirector) -- try using <server>:<port#> syntax for the server name.

Hope that helps.

_-_-_ Dave

|||

Thanks Dave,

I have check the options:

1. I have installed sql2005 with the default instance <MSSQLSERVER> that is not the problem

2. I'm connected to the DC

3. I have disabled the firewall, and that has changed the error message!!

The new message is:

Error reported by OLAP server.

Additional information:

Microsoft? OLE DB Provider for Analysis Services reported:

Cannot connect to the server '<MYSERVER>. The server is either not started or too busy.

But I can work with the SQL Server Business Intelligence Development Studio without any problem!!

|||

I have found the solution for the reported error message.

After reinstalling the "Workstation components" I can connect to the cubes in SSAS for a client Olap tool.

Thanks Dave for your support.

Regards,

Peter

|||I got the same error with the same symptoms but resolved the OLAP connection problem simply by reinstalling the OLAP provider for SQL Server 2005. The file name is SQLServer2005_ASOLEDB9.msi and it can be found on the microsoft downloads site.|||

Hi Dave,

Some questions for you about your options:

1. How do you make SQL Server 2005 the default instance if SQL Server 2000 is also installed on the same machine.
SQL Server 2000 can be removed if this is an option.
2. How can you confirm that the DC is available besides when you log into the server which is on the domain?
3. The sql server is on a windows 2003 server. The AD server is in another state and is accessed via a VPN. Could this be a problem?
4. How do you connect to the port # since when I use the Data Connection Wizard and use 10.1.1.1:1384 it comes back with the error:
"Transport Layer error."
If I use the instance name syntax -> 10.1.1.1\InstanceName - it works but then it uses the redirector which causes the main error.

So a couple of your solutions have some problems for me... is there any other way around them?

Thanks,
Andrew.

|||

>>1. How do you make SQL Server 2005 the default instance if SQL Server 2000 is also installed on the same machine.

There could be only a single default instance on the machine. And Analysis Services 2000 does not support named instances, so for AS 2005 be default instance you need to remove AS2000.

>>2. How can you confirm that the DC is available besides when you log into the server which is on the domain?

Not sure about this. You can try posting on windows networing newsgroup.

>>4. How do you connect to the port # since when I use the Data Connection Wizard and use 10.1.1.1:1384 it comes back with the error:
"Transport Layer error."
Make sure you've got port numeber correctly. By default named instance picks up a port number dynamically on every restart. You can force it to use fixed port by specifying Port server configuration property.

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

Analysis Services 2005 OLE DB Provider Error

I try to open a SSAS Cube but I get a OLE DB error message below.

The same cube I can browse with the SQL Server Business Intelligence Development Studio.

Error message:

Microsoft OLE DB Provider for Analysis Services 2005 Microsoft OLE DB Provider for Analysis Services 2005 reported:

Hope that helps.

_-_-_ Dave

|||

Thanks Dave,

I have check the options:

1. I have installed sql2005 with the default instance <MSSQLSERVER> that is not the problem

2. I'm connected to the DC

3. I have disabled the firewall, and that has changed the error message!!

The new message is:

Error reported by OLAP server.

Additional information:

Microsoft? OLE DB Provider for Analysis Services reported:

Cannot connect to the server '<MYSERVER>. The server is either not started or too busy.

But I can work with the SQL Server Business Intelligence Development Studio without any problem!!

|||

I have found the solution for the reported error message.

After reinstalling the "Workstation components" I can connect to the cubes in SSAS for a client Olap tool.

Thanks Dave for your support.

Regards,

Peter

Hi Dave,

Some questions for you about your options:

So a couple of your solutions have some problems for me... is there any other way around them?

Thanks,
Andrew.

|||

>>1. How do you make SQL Server 2005 the default instance if SQL Server 2000 is also installed on the same machine.

There could be only a single default instance on the machine. And Analysis Services 2000 does not support named instances, so for AS 2005 be default instance you need to remove AS2000.

>>2. How can you confirm that the DC is available besides when you log into the server which is on the domain?

Not sure about this. You can try posting on windows networing newsgroup.

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

Analysis Services 2005 OLE DB Provider Error

I try to open a SSAS Cube but I get a OLE DB error message below.

The same cube I can browse with the SQL Server Business Intelligence Development Studio.

Error message:

Microsoft OLE DB Provider for Analysis Services 2005 Microsoft OLE DB Provider for Analysis Services 2005 reported:

Hope that helps.

_-_-_ Dave

|||

Thanks Dave,

I have check the options:

1. I have installed sql2005 with the default instance <MSSQLSERVER> that is not the problem

2. I'm connected to the DC

3. I have disabled the firewall, and that has changed the error message!!

The new message is:

Error reported by OLAP server.

Additional information:

Microsoft? OLE DB Provider for Analysis Services reported:

Cannot connect to the server '<MYSERVER>. The server is either not started or too busy.

But I can work with the SQL Server Business Intelligence Development Studio without any problem!!

|||

I have found the solution for the reported error message.

After reinstalling the "Workstation components" I can connect to the cubes in SSAS for a client Olap tool.

Thanks Dave for your support.

Regards,

Peter

Hi Dave,

Some questions for you about your options:

So a couple of your solutions have some problems for me... is there any other way around them?

Thanks,
Andrew.

|||

>>1. How do you make SQL Server 2005 the default instance if SQL Server 2000 is also installed on the same machine.

There could be only a single default instance on the machine. And Analysis Services 2000 does not support named instances, so for AS 2005 be default instance you need to remove AS2000.

>>2. How can you confirm that the DC is available besides when you log into the server which is on the domain?

Not sure about this. You can try posting on windows networing newsgroup.

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

Monday, March 19, 2012

Another Sql 2005 Express Installation Problem

Another Sql 2005 Express Installation Problem

Sunday, March 11, 2012

Another profiler question

Thursday, March 8, 2012

Another merge agent for the subscription is running

Another distribution agents for the Subcription

Wednesday, March 7, 2012

Another cryptic message from SQL 2005 SSIS

Another cryptic message from SQL 2005 SSIS

Another cryptic message from SQL 2005 SSIS

Saturday, February 25, 2012

annoying SQL Server error message

annoying SQL Server error message

annoying SQL Server error message

Annoying Error Message

Annoying Error Message

Friday, February 24, 2012

And here is part of the installation log...

Thursday, February 16, 2012

Analysis Services started and then stopped, Event ID: 0xC1210000

Monday, February 13, 2012

Analysis Services not Started!

Sunday, February 12, 2012

Analysis Services Connection problem

Thursday, February 9, 2012

Analysis Services 2005 OLE DB Provider Error

Analysis Services 2005 OLE DB Provider Error

Analysis Services 2005 OLE DB Provider Error

SQL server connection

Blog Archive

About Me