Error loading package

Hi there all...

We've just started using SSIS packages, and everything seems to be going ok.

I've recently set up a couple of jobs which just run an SSIS package every 5 minutes to collect data.
These run fine 90% of the time, but intermittantly produce an error.

When using a SSIS task in the job it simply reported
"Could not load Package."

I have changed these to use DTExec as I heard it gave more verbose execution results, and now I get an error like
"Executed as user: NZ\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:00 a.m. Could not load package "\MSDB\RadiusBilling\Get_RADIUS_AuthLog" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 8:25:00 a.m. Finished: 8:25:00 a.m. Elapsed: 0.047 seconds. Process Exit Code 5. The step failed."

So far I have not been able to find anyone else with similar errors.
Whenever the package executes it seems to run fine, so this seems to be an error just getting the package to execute in the first place, and as I said it only happens internittantly.

The packages talk to a SQL2005 server using windows authentication (which I assume is inherited from the SQLAgent service user), as well as a MySQL server through an ODBC connection.
The package is saved in the MSDB SSIS Package Store and uses the "Rely on Server for Security" option

Does anyone know why this is happening and how I can fix it?

disenfranchised wrote:

Hi there all...

We've just started using SSIS packages, and everything seems to be going ok.

I've recently set up a couple of jobs which just run an SSIS package every 5 minutes to collect data.
These run fine 90% of the time, but intermittantly produce an error.

When using a SSIS task in the job it simply reported
"Could not load Package."

I have changed these to use DTExec as I heard it gave more verbose execution results, and now I get an error like
"Executed as user: NZ\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:00 a.m. Could not load package "\MSDB\RadiusBilling\Get_RADIUS_AuthLog" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 8:25:00 a.m. Finished: 8:25:00 a.m. Elapsed: 0.047 seconds. Process Exit Code 5. The step failed."

So far I have not been able to find anyone else with similar errors.
Whenever the package executes it seems to run fine, so this seems to be an error just getting the package to execute in the first place, and as I said it only happens internittantly.

The packages talk to a SQL2005 server using windows authentication (which I assume is inherited from the SQLAgent service user), as well as a MySQL server through an ODBC connection.
The package is saved in the MSDB SSIS Package Store and uses the "Rely on Server for Security" option

Does anyone know why this is happening and how I can fix it?

So you say it fails intermittently? Well that's weird.

Its failing because it cannot validate one of its external data sources. The fact that its intermittent leads me to suggest that there is some outside influence that is causing this. network connectivity perhaps? I'm just speculating here.

-Jamie

|||

I have suspected that it might be something to do with the permissions on the domain account that the SQLAgent runs as.

Something like the account was getting locked perhaps.

However if that was the case I'd expect to see 5-6 failures as the job runs every 5 minutes, and the domain keeps accounts locked for 30 minutes. We only ever seem to get isolated failures, but about 6 times per day (which out of 288 executions isn't to bad)

|||

Hi

I have the same problem with my SSIS packages.

I'm still developing the package so it isn't finished yet. But on each step I put it into production to see, how it behaves.

In adtition to you, I noticed, that this error occurs more often, when the package is stored in MSDB store. Previously I have had packages stored in SQL's FileSystem store and error occurs maybe twice or three times per week. Now it occurs several times per day.

I use the domain user and id in Administators group on the server.

I execute the package on the server where the inserting database is.

I execute the package every minute.

BR

ZigaP

|||Again, it sounds like an intermittent connectivity issue.|||

I think the network connectivity is not an issue.

It cannot be, because I run packages on the server where the database is.

what about this: if I replace the name of the server with "(local)"... can this solve the problem?

|||My company develops SSIS components.
No matter what you think or what you are told, I can tell you that most parts of SSIS only run about 90% of the time when you execute packages from the 'Business Intelligence Development Studio' (VS2005 really)
We actually have a problem right now because we do not have any test cases which will run 100% of the time if you let them run for a day.
Most things seem to work if you keep testing to less than an hour, but anymore and you will eventually hit a failure.

Oddly, the problem only occurs at the package level. We have not seen a package or flow that dies in the middle, or in different places, or anything variable.
It either runs to success, dies upon startup (by any means, scheduled, manual, debug), or just plain does the wrong thing. Once a given package shows a particular problem, the problem is the same every time that package fails, and there is usually only one problem.

It is known to us and some big customers that you need to shut down dev studio and reload your project to get things to work again.

The size and/or complexity of the work does not seem to matter either.
We have simple flows with one src and one dest that moves 10000 rows, all the way to massive, multi-pronged flows with multiple sources, lookups, and millions of records.
They all eventually fail. Once you get the first failure, all others on that package will be of the same nature.

Its odd.
|||

FarmerChet wrote:

My company develops SSIS components.
No matter what you think or what you are told, I can tell you that most parts of SSIS only run about 90% of the time when you execute packages from the 'Business Intelligence Development Studio' (VS2005 really)
We actually have a problem right now because we do not have any test cases which will run 100% of the time if you let them run for a day.
Most things seem to work if you keep testing to less than an hour, but anymore and you will eventually hit a failure.

Oddly, the problem only occurs at the package level. We have not seen a package or flow that dies in the middle, or in different places, or anything variable.
It either runs to success, dies upon startup (by any means, scheduled, manual, debug), or just plain does the wrong thing. Once a given package shows a particular problem, the problem is the same every time that package fails, and there is usually only one problem.

It is known to us and some big customers that you need to shut down dev studio and reload your project to get things to work again.

The size and/or complexity of the work does not seem to matter either.
We have simple flows with one src and one dest that moves 10000 rows, all the way to massive, multi-pronged flows with multiple sources, lookups, and millions of records.
They all eventually fail. Once you get the first failure, all others on that package will be of the same nature.

Its odd.

I've not observed this in my packages. So are you here with a question, or just posting your experience? There are so many things that influence package execution, and until you are sure you have a perfect environment, I wouldn't take your post with too much credit.|||

Hm... After my last post error occured only once.

I didn't do anything from my last post. Also admins on server didn't do anything...

Is server has to get used to these packages to run well?

BR
ZigaP

Error loading package

Hi there all...

We've just started using SSIS packages, and everything seems to be going ok.

I've recently set up a couple of jobs which just run an SSIS package every 5 minutes to collect data.
These run fine 90% of the time, but intermittantly produce an error.

When using a SSIS task in the job it simply reported
"Could not load Package."

I have changed these to use DTExec as I heard it gave more verbose execution results, and now I get an error like
"Executed as user: NZ\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:00 a.m. Could not load package "\MSDB\RadiusBilling\Get_RADIUS_AuthLog" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 8:25:00 a.m. Finished: 8:25:00 a.m. Elapsed: 0.047 seconds. Process Exit Code 5. The step failed."

So far I have not been able to find anyone else with similar errors.
Whenever the package executes it seems to run fine, so this seems to be an error just getting the package to execute in the first place, and as I said it only happens internittantly.

The packages talk to a SQL2005 server using windows authentication (which I assume is inherited from the SQLAgent service user), as well as a MySQL server through an ODBC connection.
The package is saved in the MSDB SSIS Package Store and uses the "Rely on Server for Security" option

Does anyone know why this is happening and how I can fix it?

disenfranchised wrote:

Hi there all...

We've just started using SSIS packages, and everything seems to be going ok.

I've recently set up a couple of jobs which just run an SSIS package every 5 minutes to collect data.
These run fine 90% of the time, but intermittantly produce an error.

When using a SSIS task in the job it simply reported
"Could not load Package."

I have changed these to use DTExec as I heard it gave more verbose execution results, and now I get an error like
"Executed as user: NZ\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:00 a.m. Could not load package "\MSDB\RadiusBilling\Get_RADIUS_AuthLog" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 8:25:00 a.m. Finished: 8:25:00 a.m. Elapsed: 0.047 seconds. Process Exit Code 5. The step failed."

So far I have not been able to find anyone else with similar errors.
Whenever the package executes it seems to run fine, so this seems to be an error just getting the package to execute in the first place, and as I said it only happens internittantly.

The packages talk to a SQL2005 server using windows authentication (which I assume is inherited from the SQLAgent service user), as well as a MySQL server through an ODBC connection.
The package is saved in the MSDB SSIS Package Store and uses the "Rely on Server for Security" option

Does anyone know why this is happening and how I can fix it?

So you say it fails intermittently? Well that's weird.

Its failing because it cannot validate one of its external data sources. The fact that its intermittent leads me to suggest that there is some outside influence that is causing this. network connectivity perhaps? I'm just speculating here.

-Jamie

|||

I have suspected that it might be something to do with the permissions on the domain account that the SQLAgent runs as.

Something like the account was getting locked perhaps.

However if that was the case I'd expect to see 5-6 failures as the job runs every 5 minutes, and the domain keeps accounts locked for 30 minutes. We only ever seem to get isolated failures, but about 6 times per day (which out of 288 executions isn't to bad)

|||

Hi

I have the same problem with my SSIS packages.

I'm still developing the package so it isn't finished yet. But on each step I put it into production to see, how it behaves.

In adtition to you, I noticed, that this error occurs more often, when the package is stored in MSDB store. Previously I have had packages stored in SQL's FileSystem store and error occurs maybe twice or three times per week. Now it occurs several times per day.

I use the domain user and id in Administators group on the server.

I execute the package on the server where the inserting database is.

I execute the package every minute.

BR

ZigaP

|||Again, it sounds like an intermittent connectivity issue.|||

I think the network connectivity is not an issue.

It cannot be, because I run packages on the server where the database is.

what about this: if I replace the name of the server with "(local)"... can this solve the problem?

|||My company develops SSIS components.
No matter what you think or what you are told, I can tell you that most parts of SSIS only run about 90% of the time when you execute packages from the 'Business Intelligence Development Studio' (VS2005 really)
We actually have a problem right now because we do not have any test cases which will run 100% of the time if you let them run for a day.
Most things seem to work if you keep testing to less than an hour, but anymore and you will eventually hit a failure.

Oddly, the problem only occurs at the package level. We have not seen a package or flow that dies in the middle, or in different places, or anything variable.
It either runs to success, dies upon startup (by any means, scheduled, manual, debug), or just plain does the wrong thing. Once a given package shows a particular problem, the problem is the same every time that package fails, and there is usually only one problem.

It is known to us and some big customers that you need to shut down dev studio and reload your project to get things to work again.

The size and/or complexity of the work does not seem to matter either.
We have simple flows with one src and one dest that moves 10000 rows, all the way to massive, multi-pronged flows with multiple sources, lookups, and millions of records.
They all eventually fail. Once you get the first failure, all others on that package will be of the same nature.

Its odd.|||

FarmerChet wrote:

My company develops SSIS components.
No matter what you think or what you are told, I can tell you that most parts of SSIS only run about 90% of the time when you execute packages from the 'Business Intelligence Development Studio' (VS2005 really)
We actually have a problem right now because we do not have any test cases which will run 100% of the time if you let them run for a day.
Most things seem to work if you keep testing to less than an hour, but anymore and you will eventually hit a failure.

Oddly, the problem only occurs at the package level. We have not seen a package or flow that dies in the middle, or in different places, or anything variable.
It either runs to success, dies upon startup (by any means, scheduled, manual, debug), or just plain does the wrong thing. Once a given package shows a particular problem, the problem is the same every time that package fails, and there is usually only one problem.

It is known to us and some big customers that you need to shut down dev studio and reload your project to get things to work again.

The size and/or complexity of the work does not seem to matter either.
We have simple flows with one src and one dest that moves 10000 rows, all the way to massive, multi-pronged flows with multiple sources, lookups, and millions of records.
They all eventually fail. Once you get the first failure, all others on that package will be of the same nature.

Its odd.

I've not observed this in my packages. So are you here with a question, or just posting your experience? There are so many things that influence package execution, and until you are sure you have a perfect environment, I wouldn't take your post with too much credit.|||

Hm... After my last post error occured only once.

I didn't do anything from my last post. Also admins on server didn't do anything...

Is server has to get used to these packages to run well?

BR
ZigaP

Error loading package

Hi there all...

We've just started using SSIS packages, and everything seems to be going ok.

I've recently set up a couple of jobs which just run an SSIS package every 5 minutes to collect data.
These run fine 90% of the time, but intermittantly produce an error.

When using a SSIS task in the job it simply reported
"Could not load Package."

I have changed these to use DTExec as I heard it gave more verbose execution results, and now I get an error like
"Executed as user: NZ\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:00 a.m. Could not load package "\MSDB\RadiusBilling\Get_RADIUS_AuthLog" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 8:25:00 a.m. Finished: 8:25:00 a.m. Elapsed: 0.047 seconds. Process Exit Code 5. The step failed."

So far I have not been able to find anyone else with similar errors.
Whenever the package executes it seems to run fine, so this seems to be an error just getting the package to execute in the first place, and as I said it only happens internittantly.

The packages talk to a SQL2005 server using windows authentication (which I assume is inherited from the SQLAgent service user), as well as a MySQL server through an ODBC connection.
The package is saved in the MSDB SSIS Package Store and uses the "Rely on Server for Security" option

Does anyone know why this is happening and how I can fix it?

disenfranchised wrote:

Hi there all...

We've just started using SSIS packages, and everything seems to be going ok.

I've recently set up a couple of jobs which just run an SSIS package every 5 minutes to collect data.
These run fine 90% of the time, but intermittantly produce an error.

When using a SSIS task in the job it simply reported
"Could not load Package."

I have changed these to use DTExec as I heard it gave more verbose execution results, and now I get an error like
"Executed as user: NZ\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:00 a.m. Could not load package "\MSDB\RadiusBilling\Get_RADIUS_AuthLog" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 8:25:00 a.m. Finished: 8:25:00 a.m. Elapsed: 0.047 seconds. Process Exit Code 5. The step failed."

So far I have not been able to find anyone else with similar errors.
Whenever the package executes it seems to run fine, so this seems to be an error just getting the package to execute in the first place, and as I said it only happens internittantly.

The packages talk to a SQL2005 server using windows authentication (which I assume is inherited from the SQLAgent service user), as well as a MySQL server through an ODBC connection.
The package is saved in the MSDB SSIS Package Store and uses the "Rely on Server for Security" option

Does anyone know why this is happening and how I can fix it?

So you say it fails intermittently? Well that's weird.

Its failing because it cannot validate one of its external data sources. The fact that its intermittent leads me to suggest that there is some outside influence that is causing this. network connectivity perhaps? I'm just speculating here.

-Jamie

|||

I have suspected that it might be something to do with the permissions on the domain account that the SQLAgent runs as.

Something like the account was getting locked perhaps.

However if that was the case I'd expect to see 5-6 failures as the job runs every 5 minutes, and the domain keeps accounts locked for 30 minutes. We only ever seem to get isolated failures, but about 6 times per day (which out of 288 executions isn't to bad)

|||

Hi

I have the same problem with my SSIS packages.

I'm still developing the package so it isn't finished yet. But on each step I put it into production to see, how it behaves.

In adtition to you, I noticed, that this error occurs more often, when the package is stored in MSDB store. Previously I have had packages stored in SQL's FileSystem store and error occurs maybe twice or three times per week. Now it occurs several times per day.

I use the domain user and id in Administators group on the server.

I execute the package on the server where the inserting database is.

I execute the package every minute.

BR

ZigaP

|||Again, it sounds like an intermittent connectivity issue.|||

I think the network connectivity is not an issue.

It cannot be, because I run packages on the server where the database is.

what about this: if I replace the name of the server with "(local)"... can this solve the problem?

|||My company develops SSIS components.
No matter what you think or what you are told, I can tell you that most parts of SSIS only run about 90% of the time when you execute packages from the 'Business Intelligence Development Studio' (VS2005 really)
We actually have a problem right now because we do not have any test cases which will run 100% of the time if you let them run for a day.
Most things seem to work if you keep testing to less than an hour, but anymore and you will eventually hit a failure.

Oddly, the problem only occurs at the package level. We have not seen a package or flow that dies in the middle, or in different places, or anything variable.
It either runs to success, dies upon startup (by any means, scheduled, manual, debug), or just plain does the wrong thing. Once a given package shows a particular problem, the problem is the same every time that package fails, and there is usually only one problem.

It is known to us and some big customers that you need to shut down dev studio and reload your project to get things to work again.

The size and/or complexity of the work does not seem to matter either.
We have simple flows with one src and one dest that moves 10000 rows, all the way to massive, multi-pronged flows with multiple sources, lookups, and millions of records.
They all eventually fail. Once you get the first failure, all others on that package will be of the same nature.

Its odd.
|||

FarmerChet wrote:

My company develops SSIS components.
No matter what you think or what you are told, I can tell you that most parts of SSIS only run about 90% of the time when you execute packages from the 'Business Intelligence Development Studio' (VS2005 really)
We actually have a problem right now because we do not have any test cases which will run 100% of the time if you let them run for a day.
Most things seem to work if you keep testing to less than an hour, but anymore and you will eventually hit a failure.

Oddly, the problem only occurs at the package level. We have not seen a package or flow that dies in the middle, or in different places, or anything variable.
It either runs to success, dies upon startup (by any means, scheduled, manual, debug), or just plain does the wrong thing. Once a given package shows a particular problem, the problem is the same every time that package fails, and there is usually only one problem.

It is known to us and some big customers that you need to shut down dev studio and reload your project to get things to work again.

The size and/or complexity of the work does not seem to matter either.
We have simple flows with one src and one dest that moves 10000 rows, all the way to massive, multi-pronged flows with multiple sources, lookups, and millions of records.
They all eventually fail. Once you get the first failure, all others on that package will be of the same nature.

Its odd.

I've not observed this in my packages. So are you here with a question, or just posting your experience? There are so many things that influence package execution, and until you are sure you have a perfect environment, I wouldn't take your post with too much credit.|||

Hm... After my last post error occured only once.

I didn't do anything from my last post. Also admins on server didn't do anything...

Is server has to get used to these packages to run well?

BR
ZigaP

sql

Error linked server query after installing SP4 on SQL 2000

Hello
SQL 2000 SP3a run fine with an linked server query like
select * from openquery( linkedOlapServer, .. here is the MDX ...')
After installing SP4 build 2039 this query fails with error:
Server: Msg 7302, Level 16, State 1, Line 1
Could not create an instance of OLE DB provider 'MSOLAP'.
OLE DB error trace [Non-interface error: CoCreate of DSO for MSOLAP
returned 0x80040154].
Appreciate hints from experience on which hot fix do I need to install?
Nic
Does changing the "AllowInProcess" to something non zero fix this problem?
http://msdn2.microsoft.com/en-us/library/ms190918.aspx
In Object Explorer, right-click the provider name and select Properties. The
following table describes the available provider options...
thanks,
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Nic" <Nic@.discussions.microsoft.com> wrote in message
news:E4A1CCBC-331D-4C70-B83C-F1AFE5CFAA62@.microsoft.com...
> Hello
> SQL 2000 SP3a run fine with an linked server query like
> select * from openquery( linkedOlapServer, .. here is the MDX ...')
> After installing SP4 build 2039 this query fails with error:
> Server: Msg 7302, Level 16, State 1, Line 1
> Could not create an instance of OLE DB provider 'MSOLAP'.
> OLE DB error trace [Non-interface error: CoCreate of DSO for MSOLAP
> returned 0x80040154].
> Appreciate hints from experience on which hot fix do I need to install?
> Nic
>

Error installing SQL Server 2005 Upgrade Advisor

I'm getting a Windows Installer error when attempting to run the Upgrade Advisor setup package (SQLUASetup.exe). The error message reads:

"This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service."

The machine is running Windows 2000 sp4. Both the .net framework v2 and Windows Installer 3.0 have been installed.

Any suggestions?

You need to be running Windows Installer 3.1. You can find it here:

http://support.microsoft.com/?id=893803

|||

I'm also having problems installing the Upgrade Advisor on a W2K server running SQL Server 2000. .net Framework 2.0 is installed as is Windows Installer 3.1.

I'm getting the follwing error message: "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755."

Any ideas what might be the problem here ?

|||

You need to install Windows 2003 SP1, .NET frameworks 2.0 before installing Upgrade Advisor

You can refer http://msdn2.microsoft.com/en-us/library/ms144256.aspx

If you are still seeing install errors, you gather verbose log and post it in this newsgroup. To create verbose log:

Ex: msiexec /i SQLUASetup.msi /l*v e:\temp\verbose.log

Thanks

Sethu Srinivasan

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.

Error installing SQL Server 2005 Upgrade Advisor

I'm getting a Windows Installer error when attempting to run the Upgrade Advisor setup package (SQLUASetup.exe). The error message reads:

"This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service."

The machine is running Windows 2000 sp4. Both the .net framework v2 and Windows Installer 3.0 have been installed.

Any suggestions?

You need to be running Windows Installer 3.1. You can find it here:

http://support.microsoft.com/?id=893803

|||

I'm also having problems installing the Upgrade Advisor on a W2K server running SQL Server 2000. .net Framework 2.0 is installed as is Windows Installer 3.1.

I'm getting the follwing error message: "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755."

Any ideas what might be the problem here ?

|||

You need to install Windows 2003 SP1, .NET frameworks 2.0 before installing Upgrade Advisor

You can refer http://msdn2.microsoft.com/en-us/library/ms144256.aspx

If you are still seeing install errors, you gather verbose log and post it in this newsgroup. To create verbose log:

Ex: msiexec /i SQLUASetup.msi /l*v e:\temp\verbose.log

Thanks

Sethu Srinivasan

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.

Error Installing Reporting Services

I attempt to run the Reporting Services installation and
get and on the screen right after the license agreement, I
get a message that says just "Error!" and I cannot
continue. Is there a log file somewhere I can look at -
nothing was installed so no directory exists on the hard
disk. I am running Windows 2000, .NET 1.1 framework, and
SQL Server 2000 Development with latest service pack.Here is the contents of a file I found in the temp
directory that appears to have an error at the bottom:
Microsoft SQL Server 2000 Reporting Services Setup
beginning at Mon Sep 13 09:50:33 2004
<Func Name='UpdateComponents'>
SCU_SetupMgr::InitComponents()
<Func Name='WindowsInstallerComp::Init'>
.
.
.
QuietMode=false
Unattended=false
WorkDir=H:
}}
{n:\rosetta\dev\src\everettsetup\sqlcu\dll\scusetupmgr.cpp:
292}
<Func Name='SqlSetupFilesComp::Install'>
SqlSetupFilesComp WNetGetUniversalName() returned : (1201)
{n:\rosetta\dev\src\everettsetup\sqlcu\dll\customcomps.cpp:
449}
SCU_SetupMgr::svc() caught exception: SqlSetupFilesComp
WNetGetUniversalName() returned : (1201)
{n:\rosetta\dev\src\everettsetup\sqlcu\dll\customcomps.cpp:
449}. SetupMgr: state=ERROR, cancel_state=0, is_done=0,
ActionRequired=1, NeedReboot=0, custom_props={AutoStart=true
HandleReboots=false
ModuleDir=H:
QuietMode=false
Unattended=false
WorkDir=H:
}}
{n:\rosetta\dev\src\everettsetup\sqlcu\dll\scusetupmgr.cpp:
428}
ScuProgressDlg::SetupFinished()
ScuProgressDlg::DialogProc() installation done... waiting
for setup mgr
<EndFunc Name='UpdateComponents' Return='1602'
GetLastError='1400'>

Error in the PROCEDURE....

Hi,
i m trying to run a procedure...but everytime i run it...it gives me some error as:
-
Msg 468, Level 16, State 9, Procedure FIN_INFO__Get_Cash_Payments_Info, Line 46

Cannot resolve the collation conflict between "Cyrillic_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
--

Whats the meaning of "Cyrillic_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS"
How can i change it?
if someone has some idea then please let me know...that will b great help to me...
thnks,
regards.

"Cyrillic_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" are the collations of the columns being compared. Here is an example:

create table col (col1 varchar(10) collate Cyrillic_General_CI_AS,

col2 varchar(10) collate SQL_Latin1_General_CP1_CI_AS)

select * from col

where col1 = col2

Results:

Msg 468, Level 16, State 9, Line 1

Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Cyrillic_General_CI_AS" in the equal to operation.
But if you explicitly convert the collation like in the following, the query will work:

select * from col

where col1 = col2 collate SQL_Latin1_General_CP1_CI_AS

More information can be found at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_da-db_7ory.asp

collate SQL_Latin1_General_CP1_CI_AS

|||Thanks for the reply...so that means that in the whole procedure i have to make this COLLATE command u suggested....for all the columns?ok..i will try it....n i hope it will work...thnks a lot once again
regards...|||You only need to use the COLLATE command it the collation of the columns can not be implicitly compared. If you need to do this all over, you might evaulate if you can change the column type to a more compatible collation.

Peter|||Hi,
i tried all the ways to use COLLATE...but still the same error...can you please go through the code and tell me...where exactly i have to use COLLATE...i will really appreciate any help...

ALTER procedure [dbo].[Get_Payments]

(

@.p_Personal_Account numeric(15,0), -- Personal_Account_Attributes.Personal_Account%type,

@.p_Quantity int, -- number := NULL,

@.p_Date_From datetime, -- date := NULL,

@.p_Date_To datetime -- date := SYSDATE,

)

as

begin

begin try

select @.p_Quantity = null

select @.p_Date_From = null

select @.p_Date_To = getdate()

IF (@.p_Quantity IS NULL)

select PD.Payment_Document_Id ,

PD.Document_Number collate SQL_Latin1_General_CP1_CI_AS,

(select isnull(sum(FT.Amount),0)

from Financial_Transaction FT

where FT.Personal_Account = @.p_Personal_Account

and FT.Payment_Document_id = PD.Payment_Document_Id collate SQL_Latin1_General_CP1_CI_AS

and FT.Operation_Type not in(select OL.Operation_Type

from Operation_Type_Group OG, Operation_Type_Group_Link OL

where OG.Group_Code = dbo.fnGetConstant('Collection_Constants', 'g_Sum_Differences_Group')

and OL.Operation_Type_Group_id = OG.Operation_Type_Group_id collate SQL_Latin1_General_CP1_CI_AS) ) Document_Amount,

round((select isnull(sum(FT.Amount),0)

from Financial_Transaction FT

where FT.Personal_Account = @.p_Personal_Account

and FT.Payment_Document_id = PD.Payment_Document_Id

and FT.Operation_Type not in(select OL.Operation_Type

from Operation_Type_Group OG, Operation_Type_Group_Link OL

where OG.Group_Code = dbo.fnGetConstant('Collection_Constants', 'g_Sum_Differences_Group')

and OL.Operation_Type_Group_id = OG.Operation_Type_Group_id)) * ER.Rate_Value / ER.Rate_Amount, convert(int, dbo.fnGetConstant('Collection_Constants', 'g_Round_Size'))) Internal_Amount,

PD.Currency_Code collate SQL_Latin1_General_CP1_CI_AS,

(select CR.Currency_Symbol

from Currency CR

where CR.Currency_Code = PD.Currency_Code collate SQL_Latin1_General_CP1_CI_AS) Currency_Symbol,

case

when PD.Spec_Detail_Table_Code = dbo.fnGetConstant('Collection_Constants', 'g_Spec_Detail_Table_EP')

then (select min(F.Date_Of_Transaction)

from Financial_Transaction F

where F.Personal_Account = @.p_Personal_Account

and F.Payment_Document_id = PD.Payment_Document_Id)

else PD.Date_of_Payment

end Date_of_Payment,

case

when PD.Spec_Detail_Table_Code = dbo.fnGetConstant('Collection_Constants', 'g_Spec_Detail_Table_EP')

then PD.Date_Of_Payment

else PD.Date_of_Collection

end Date_of_Collection,

(select min(FT.Date_of_Transaction)

from Financial_Transaction FT

where FT.Payment_Document_Id = PD.Payment_Document_Id collate SQL_Latin1_General_CP1_CI_AS

and FT.Personal_Account = @.p_Personal_Account) Date_Of_Transaction,

PD.Pay_Form,

(select PF.Pay_Form_Name

from Pay_Form PF

where PF.Pay_Form = PD.Pay_Form collate SQL_Latin1_General_CP1_CI_AS) Pay_Form_Name,

case

when PD.Spec_Detail_Table_Code = dbo.fnGetConstant('Collection_Constants', 'g_Spec_Detail_Table_EP')

then (select EPC_Serial_Number

from EPC_Payment EP

where EP.Payment_Document_Id = PD.Payment_Document_id collate SQL_Latin1_General_CP1_CI_AS)

else PD.Pay_Form_Number

end Pay_Form_Number,

PD.Customer_Data,

PD.Commentary,

PD.Spec_Detail_Table_Code,

(select PP.Payment_Place_Type

from Payment_Packet PP

where PD.Pay_Packet_id = PP.Pay_Packet_id) Payment_Place_Type,

(select PPT.Payment_Place_Type_Name

from Payment_Place_Type PPT

where PPT.Payment_Place_Type = (select PP.Payment_Place_Type

from Payment_Packet PP

where PD.Pay_Packet_id = PP.Pay_Packet_id)) Payment_Place_Type_Name,

PD.Date_of_Change,

PD.User_id_of_Change ,

(select ER1.Rate_Value/ER1.Rate_Amount

from Exchange_Rate_List ER1

where PD.Date_Of_Collection between ER1.Start_Date and isnull(ER1.End_Date, dbo.fnGetConstant('Collection_Constants', 'g_Max_Date'))

and ER1.From_Currency_Code = dbo.fnGetConstant('Collection_Constants', 'g_Currency_Code_Internal')

and ER1.To_Currency_Code = dbo.fnGetConstant('Collection_Constants', 'g_Currency_Code_National')

and ER1.Exchange_List_Type = dbo.fnGetConstant('Collection_Constants', 'g_Exchange_List_Type')) Course

from Payment_Document PD, Exchange_Rate_List ER

where PD.Payment_Document_id in (select F.Payment_Document_id

from Financial_Transaction F

where F.Personal_Account = @.p_Personal_Account

and F.Date_Of_Transaction between isnull(@.p_Date_From, dbo.fnGetConstant('Collection_Constants', 'g_Min_Date'))

and isnull(@.p_Date_To, dbo.fnGetConstant('Collection_Constants', 'g_Max_Date')))

and (select min(F.Date_of_Transaction)

from Financial_Transaction F

where F.Personal_Account = @.p_Personal_Account

and F.Payment_Document_id = PD.Payment_Document_id) between isnull(@.p_Date_From, dbo.fnGetConstant('Collection_Constants', 'g_Min_Date'))

and isnull(@.p_Date_To, dbo.fnGetConstant('Collection_Constants', 'g_Max_Date'))

and ER.From_Currency_Code = PD.Currency_Code

and ER.To_Currency_Code = dbo.fnGetConstant('Collection_Constants', 'g_Currency_Code_Internal')

and ER.Exchange_List_Type = dbo.fnGetConstant('Collection_Constants', 'g_Exchange_List_Type')

and PD.Date_Of_Collection between ER.Start_Date and isnull(ER.End_Date, dbo.fnGetConstant('Collection_Constants', 'g_Max_Date'))

order by Date_of_Payment desc;

THANKS IN ADVANCE....PLEASEEEEEEEEEE CHANGE THIS CODE N TEL ME WHERE I HAVE TO WRITE THIS collate....coz the changes i made..they show the same error as b4
Regards,
Shuchi.

|||Without access to database it would be hard to tell exactly where to add "collate". As a general rule, any place we you are comparing columns that have different collations many need this keyword. I see in your code you have collate in the selected columns, this is not necessary. When you get an error compiling, just click on the error and it should take you to the offending statement.

Peter

Error in SQL server 2000

Hi

I just installed SQL Server 2000 EVAL ver, in my Win XP Pro machine and the installtion was succesful though I get the following error once I run the code.

What does this mean ? What should I do here ?

----------------------
[SqlException: Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) +472
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +311
System.Data.SqlClient.SqlConnection.Open() +383
ASP.DropDownList_aspx.Page_Load() +61
System.Web.Util.ArglessEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +10
System.Web.UI.Control.OnLoad(EventArgs e) +55
System.Web.UI.Control.LoadRecursive() +27
System.Web.UI.Page.ProcessRequestMain() +731you need to add a user to the users list. if you xpand the your database in sql serve xplorer under users you need to add the machinename\ASPNET user account to grant access to the tables.

hth|||Hi Ndinakar,

Thanks for your help though I have the same, it gives the errors again.

I do run SQL 2000 Evaluation Version in Win XP Professional which is in home use.
(NOT connected into a Server or a Domain)

TIA
dan|||you prbly have an incorrect connection string. check this site for some sample connection strings :http://www.connectionstrings.com

hth|||naw, you didn't put a strong sa password, and it's looking for nt security.|||Hi

Thanks for both of you for the great help.
This is my code and the error message is pasted down. Further my ID and password is mentioned as in the SQL Server.

Further I am very new to ASP.net and just try to study the examples of ASP.net UNLEASHED published by SAMS.

<%@. Page Language="VB" %>
<%@. import Namespace="System.Data" %>
<%@. import Namespace="System.Data.SqlClient" %>
<script runat="server"
"Data Source=Aron1;Initial Catalog=pubs;User Id=sa;Password=tkpkkalu"

Dim conPubs As SqlConnection

Sub Page_Load
Dim dtrAuthors As SqlDataReader

dtrAuthors = GetAuthors()
While dtrAuthors.Read
lblAuthors.Text &= "<li>"
lblAuthors.Text &= dtrAuthors( "au_lname" )
End While
dtrAuthors.Close()
lblAuthors.Text &= "

---

Connection is:" & conPubs.State.ToString()
End Sub

Function GetAuthors() As SqlDataReader
Dim cmdAuthors As SqlCommand

conPubs = New SqlConnection( "Server=localhost;UID=sa;PWD=secret;database=pubs" )
cmdAuthors = New SqlCommand( "select * from Authors", conPubs )
conPubs.Open()
Return cmdAuthors.ExecuteReader( CommandBehavior.CloseConnection )
End Function

</script>
<html>
<head>
<title>SqlCloseConnection.aspx</title>
</head>
<body>
<asp:Label id="lblAuthors" runat="Server"></asp:Label>
</body>
</html
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: BC30035: Syntax error.

Source Error:

Line 5:
Line 6:
Line 7: "Data Source=Aron1;Initial Catalog=pubs;User Id=sa;Password=tkpkkalu"
Line 8:
Line 9:

Source File: C:\Inetpub\wwwroot\SqlCloseConnection.aspx Line: 7|||are we missing something between these lines ?

<script runat="server"
"Data Source=Aron1;Initial Catalog=pubs;User Id=sa;Password=tkpkkalu"
Dim conPubs As SqlConnection

change the above lines to

<script runat="server">
Dim conPubs As SqlConnection
conPubs.connectionstring="Data Source=Aron1;Initial Catalog=pubs;User Id=sa;Password=tkpkkalu"

also you are missing parameters for the page_load sub.

sub page_load (Sender as Object, e as EventArgs)

hth

Error in reporting services

hi,

i am facing a problem in reporting services of Sql server 2005

i am trying to run the "third party tool"(Reports of proclarity) in sql server 2005

and i am getting the following error

An error has occurred during report processing.
Cannot create a connection to data source 'Employees_'.
Cannot connect to the server 'SYSTEM100'. The server is either not started or too busy.
Property name was not recognized, 'MDX Missing Member Mode'

regards

lalitha

This is a bit of a guess, since I don't really know much about how Proclarity works with Reporting Services, but given that 'MDX Missing Member Mode' is a valid connection string property that only appeared with AS2005 are you perhaps trying to connect to Analysis Services using an older version of the OLEDB for OLAP Provider? You should be using MSOLAP.3; if you don't have it installed, you can download it here:

http://www.microsoft.com/downloads/details.aspx?familyid=DF0BA5AA-B4BD-4705-AA0A-B477BA72A9CB&displaylang=en

Chris

|||

Hi Lalitha,

Check the connection string of your report (click the "Properties" tab and then select "Data Source" from the list on the left). Your connection string probably looks something like this:

Data Source=localhost;Initial Catalog=Adventure Works DW Standard Edition;Provider=MSOLAP;MDX Compatibility=2;MDX Missing Member Mode=Error

You need to change the "Provider" portion of the connection string from "MSOLAP" to "MSOLAP.3" so your connection string now looks something like this:

Data Source=localhost;Initial Catalog=Adventure Works DW Standard Edition;Provider=MSOLAP.3;MDX Compatibility=2;MDX Missing Member Mode=Error

Hope this helps,

Joe Hayes

Error in reporting services

hi,

i am facing a problem in reporting services of Sql server 2005

i am trying to run the "third party tool"(Reports of proclarity) in sql server 2005

and i am getting the following error

An error has occurred during report processing.
Cannot create a connection to data source 'Employees_'.
Cannot connect to the server 'SYSTEM100'. The server is either not started or too busy.
Property name was not recognized, 'MDX Missing Member Mode'

regards

lalitha

This is a bit of a guess, since I don't really know much about how Proclarity works with Reporting Services, but given that 'MDX Missing Member Mode' is a valid connection string property that only appeared with AS2005 are you perhaps trying to connect to Analysis Services using an older version of the OLEDB for OLAP Provider? You should be using MSOLAP.3; if you don't have it installed, you can download it here:

http://www.microsoft.com/downloads/details.aspx?familyid=DF0BA5AA-B4BD-4705-AA0A-B477BA72A9CB&displaylang=en

Chris

|||

Hi Lalitha,

Check the connection string of your report (click the "Properties" tab and then select "Data Source" from the list on the left). Your connection string probably looks something like this:

Data Source=localhost;Initial Catalog=Adventure Works DW Standard Edition;Provider=MSOLAP;MDX Compatibility=2;MDX Missing Member Mode=Error

You need to change the "Provider" portion of the connection string from "MSOLAP" to "MSOLAP.3" so your connection string now looks something like this:

Data Source=localhost;Initial Catalog=Adventure Works DW Standard Edition;Provider=MSOLAP.3;MDX Compatibility=2;MDX Missing Member Mode=Error

Hope this helps,

Joe Hayes

Error in Mcafee MSDE

Hi Everyone,
i have a problem in Mcafee MSDE , it doesent run & give me the error in the
Event Log
"This SQL Server has been optimized for 8 concurrent queries. This limit has
been exceeded by 1 queries and performance may be adversely affected."
event id 17055
Any Idea About This error?
Thx in Adv.
Thats the effect of the query governor which slows allows only 8 simultanly
queries per server based on the restrictions of the msde.
"MSDE includes a
Governor Workloads that kicks in when 8 of more concurrent workloads
activities (batches that include the operations as described in
http://msdn.microsoft.com/library/?u...r_sa2_0ciq.asp
?frame=true)
are executed and slows all of them down, but more workloads are supported
and only slowed down...
"
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Mariame" <mariame_waguih@.hotmail.com> schrieb im Newsbeitrag
news:u$vix1nZFHA.3132@.TK2MSFTNGP09.phx.gbl...
> Hi Everyone,
> i have a problem in Mcafee MSDE , it doesent run & give me the error in
> the Event Log
> "This SQL Server has been optimized for 8 concurrent queries. This limit
> has been exceeded by 1 queries and performance may be adversely affected."
> event id 17055
> Any Idea About This error?
> Thx in Adv.
>

Error in Mcafee MSDE

Hi Everyone,
i have a problem in Mcafee MSDE , it doesent run & give me the error in the
Event Log
"This SQL Server has been optimized for 8 concurrent queries. This limit has
been exceeded by 1 queries and performance may be adversely affected."
event id 17055
Any Idea About This error'
Thx in Adv.Thats the effect of the query governor which slows allows only 8 simultanly
queries per server based on the restrictions of the msde.
"MSDE includes a
Governor Workloads that kicks in when 8 of more concurrent workloads
activities (batches that include the operations as described in
[url]http://msdn.microsoft.com/library/?url=/library/en-us/architec/8_ar_sa2_0ciq.asp[/
url]
?frame=true)
are executed and slows all of them down, but more workloads are supported
and only slowed down...
"
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Mariame" <mariame_waguih@.hotmail.com> schrieb im Newsbeitrag
news:u$vix1nZFHA.3132@.TK2MSFTNGP09.phx.gbl...
> Hi Everyone,
> i have a problem in Mcafee MSDE , it doesent run & give me the error in
> the Event Log
> "This SQL Server has been optimized for 8 concurrent queries. This limit
> has been exceeded by 1 queries and performance may be adversely affected."
> event id 17055
> Any Idea About This error'
> Thx in Adv.
>

Error in Mcafee MSDE

Hi Everyone,
i have a problem in Mcafee MSDE , it doesent run & give me the error in the
Event Log
"This SQL Server has been optimized for 8 concurrent queries. This limit has
been exceeded by 1 queries and performance may be adversely affected."
event id 17055
Any Idea About This error'
Thx in Adv.Thats the effect of the query governor which slows allows only 8 simultanly
queries per server based on the restrictions of the msde.
"MSDE includes a
Governor Workloads that kicks in when 8 of more concurrent workloads
activities (batches that include the operations as described in
http://msdn.microsoft.com/library/?url=/library/en-us/architec/8_ar_sa2_0ciq.asp
?frame=true)
are executed and slows all of them down, but more workloads are supported
and only slowed down...
"
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Mariame" <mariame_waguih@.hotmail.com> schrieb im Newsbeitrag
news:u$vix1nZFHA.3132@.TK2MSFTNGP09.phx.gbl...
> Hi Everyone,
> i have a problem in Mcafee MSDE , it doesent run & give me the error in
> the Event Log
> "This SQL Server has been optimized for 8 concurrent queries. This limit
> has been exceeded by 1 queries and performance may be adversely affected."
> event id 17055
> Any Idea About This error'
> Thx in Adv.
>

Error in first run of the snapshot agent (Error: 170)

Hi All
I am getting the following error from the snapshot agent, while first
setting up transactional queued replication.
"Line 1: Incorrect syntax near '000'.
(Source: distribution (Data source); Error number: 170)
"
I have read the KB articles saying I should install SP3 and the problem will
go away. I have installed SP3 on both publisher/distributor & single test
subscriber, on specially prepared clean installations of SQL2000.
Here is the end of the detailed logfile produced by the repl agent:
"Inserted constraint creation command for article 'EventBookingstatus' into
the distribution database.
*** [Publication:'I-junction_Support-Central_Live'] Total snapshot
generation time excluding publication setup: 439271 (ms) ***
SourceTypeId = 5
SourceName = distribution
ErrorCode = 170
ErrorText = Line 1: Incorrect syntax near '000'.
Line 1: Incorrect syntax near '000'.
Disconnecting from Publisher 'IJUNC-LUDD'
"
What should I try next?
I am happy to provide the sql to create the db & the replication if it helps.
Many thanks
Vaughn
Hi Vaughn,
I have the vague suspicion that you are hitting the issue described in
KB834453 (just search on microsoft.com) which is fixed as a QFE after sp3.
If you can include more of the output from the snapshot agent or a trace of
the failing command then I can tell with greater certainty. In any case, I
think it is worthwhile for you to contact Microsoft support to try out the
fix.
-Raymond
This posting is provided "as is" with no warranties and confers no rights.
"Vaughn Cleminson" <Vaughn Cleminson@.discussions.microsoft.com> wrote in
message news:EC3169EF-6EC5-4BF1-B43C-C51403DAA06C@.microsoft.com...
> Hi All
> I am getting the following error from the snapshot agent, while first
> setting up transactional queued replication.
> "Line 1: Incorrect syntax near '000'.
> (Source: distribution (Data source); Error number: 170)
> "
> I have read the KB articles saying I should install SP3 and the problem
will
> go away. I have installed SP3 on both publisher/distributor & single test
> subscriber, on specially prepared clean installations of SQL2000.
> Here is the end of the detailed logfile produced by the repl agent:
> "Inserted constraint creation command for article 'EventBookingstatus'
into
> the distribution database.
> *** [Publication:'I-junction_Support-Central_Live'] Total snapshot
> generation time excluding publication setup: 439271 (ms) ***
> SourceTypeId = 5
> SourceName = distribution
> ErrorCode = 170
> ErrorText = Line 1: Incorrect syntax near '000'.
> Line 1: Incorrect syntax near '000'.
> Disconnecting from Publisher 'IJUNC-LUDD'
> "
> What should I try next?
> I am happy to provide the sql to create the db & the replication if it
helps.
> Many thanks
> Vaughn
|||Hi
Thanks for the reply.
I'll check the db for reserved words and silly characters.
How to I trace the failing command, please?
The full snapshot logfile is too long to post.
Is there a specific bit that will help?
Vaughn
|||Hi Riaymond.
The KB you suggest says:
SYMPTOMS
When the Snapshot Agent runs after you make schema changes to the underlying
tables of a publication, the Snapshot Agent may fail.
This is the first time I am running the agent, after creating the
publication. I haven't changed the tables since making the publication and
setting up the areticles.
Does the KB still apply?
Vaughn
|||Hi Vaughn,
You can definitely see the error even if this is the first time you run the
snapshot agent. Making schema\publication changes simply gives the random
flavors described in the KB. To tack down the problematic command, you
should start a SQL Profiler trace with the statement starting\batch
startng\RPC starting events enabled before running the snapshot agent. The
problematic command should starts with sp_MSadd_repl_error if my guess is
correct but you may need to back track a few entries in the profiler trace
before you can find it.
-Raymond
This posting is provided "as is" with no warranties and confers no rights.
"Vaughn Cleminson" <VaughnCleminson@.discussions.microsoft.com> wrote in
message news:D8229CB1-A616-4ABB-BF09-787A280C413C@.microsoft.com...
> Hi Riaymond.
> The KB you suggest says:
> SYMPTOMS
> When the Snapshot Agent runs after you make schema changes to the
underlying
> tables of a publication, the Snapshot Agent may fail.
> This is the first time I am running the agent, after creating the
> publication. I haven't changed the tables since making the publication and
> setting up the areticles.
> Does the KB still apply?
> Vaughn
|||Hi Raymond.
Man, you clearly know your stuff.
Here is the error line from profiler, and the error reported:
What do you suggest I try next?
line:
exec sp_MSadd_repl_command @.publisher_id = 0, @.publisher_db =
N'I-junction_Support-Central_Live', @.type = -2147483639, @.article_id = 63,
@.xact_id = 0x000000000000, @.xact_seqno = 0x00001c490000012802b900000001,
@.command_id = 1111, @.partial_command = 0, @.command =
0x6900660020002800400040006d006900630072006f007300 6f0066007400760065007200730069006f006e0020003e003d 00200030007800300038003000300030003200430030002900 200062006500670069006e0020006500780065006300200073 0070005f00610064006400730079006e006300740072006900 67006
70065007200730020004e00270045006d00610069006c00520 075006c006500450078006500630075007400610062006c006 50027002c0020004e0027006e0075006c006c0027002c00200 04e00270049004a0055004e0043002d004c005500440044002 7002c0020004e00270049002d006a0075006e0063007400690 06f00
6e005f0053007500700070006f00720074002d00430065006e 007400720061006c005f004c0069007600650027002c002000 4e00270049002d006a0075006e006300740069006f006e005f 0053007500700070006f00720074002d00430065006e007400 720061006c005f004c0069007600650027002c0020004e0027 00730
070005f004d005300730079006e0063005f0069006e0073005 f0045006d00610069006c00520075006c00650045007800650 0630075007400610062006c0065005f00310027002c0020004 e002700730070005f004d005300730079006e0063005f00750 0700064005f0045006d00610069006c00520075006c0065004 50078
006500630075007400610062006c0065005f00310027002c00 20004e002700730070005f004d005300730079006e0063005f 00640065006c005f0045006d00610069006c00520075006c00 6500450078006500630075007400610062006c0065005f0031 0027002c0020004e002700730070005f004d00530063006600 74005
f0049002d006a0075006e006300740069006f006e005f00530 07500700070006f00720074002d00430065006e00740072006 1006c005f004c006900760065005f0045006d00610069006c0 0520075006c006500450078006500630075007400610062006 c00650027002c0020004e002700640062006f0027002c00200 04e00
27005000720069006d006100720079004b006500790027002c 0020004e0027006e0075006c006c0027002c0020004e002700 6e0075006c006c0027002c00200030007800300031002c0020 0031002c0031002c004e00270049004a0055004e0043002d00 4c0055004400440027002c0020003200200065006e00640020 00
e006?????6?6
error:
exec sp_MSadd_snapshot_history @.agent_id = 5, @.runstatus = 6, @.comments =
N'Line 1: Incorrect syntax near ''e006''.', @.delivered_transactions = 1,
@.delivered_commands = 0, @.log_error = 1,
|||Hi Vaughn,
The only thing to do now is to contact Microsoft Product\Customer Support
with the information below and ask for the QFE fix described in KB834453;
there should be no charge for this. Or, you can try to work around the
problem by using either a longer (or shorter) article name for article id#63
(just drop and recreate the article).
-Raymond
This posting is provided "as is" with no warranties and confers no rights.
"Vaughn Cleminson" <VaughnCleminson@.discussions.microsoft.com> wrote in
message news:549EC277-0623-4DC5-992F-8780FA613ADF@.microsoft.com...
> Hi Raymond.
> Man, you clearly know your stuff.
> Here is the error line from profiler, and the error reported:
> What do you suggest I try next?
> line:
> exec sp_MSadd_repl_command @.publisher_id = 0, @.publisher_db =
> N'I-junction_Support-Central_Live', @.type = -2147483639, @.article_id = 63,
> @.xact_id = 0x000000000000, @.xact_seqno = 0x00001c490000012802b900000001,
> @.command_id = 1111, @.partial_command = 0, @.command =
>
0x6900660020002800400040006d006900630072006f007300 6f006600740076006500720073
0069006f006e0020003e003d00200030007800300038003000 30003000320043003000290020
0062006500670069006e002000650078006500630020007300 70005f00610064006400730079
006e0063007400720069006700670065007200730020004e00 270045006d00610069006c0052
0075006c006500450078006500630075007400610062006c00 650027002c0020004e0027006e
0075006c006c0027002c0020004e00270049004a0055004e00 43002d004c0055004400440027
002c0020004e00270049002d006a0075006e00630074006900 6f006e005f0053007500700070
006f00720074002d00430065006e007400720061006c005f00 4c0069007600650027002c0020
004e00270049002d006a0075006e006300740069006f006e00 5f0053007500700070006f0072
0074002d00430065006e007400720061006c005f004c006900 7600650027002c0020004e0027
00730070005f004d005300730079006e0063005f0069006e00 73005f0045006d00610069006c
00520075006c00650045007800650063007500740061006200 6c0065005f00310027002c0020
004e002700730070005f004d005300730079006e0063005f00 7500700064005f0045006d0061
0069006c00520075006c006500450078006500630075007400 610062006c0065005f00310027
002c0020004e002700730070005f004d005300730079006e00 63005f00640065006c005f0045
006d00610069006c00520075006c0065004500780065006300 75007400610062006c0065005f
00310027002c0020004e002700730070005f004d0053006300 660074005f0049002d006a0075
006e006300740069006f006e005f0053007500700070006f00 720074002d00430065006e0074
00720061006c005f004c006900760065005f0045006d006100 69006c00520075006c00650045
0078006500630075007400610062006c00650027002c002000 4e002700640062006f0027002c
0020004e0027005000720069006d006100720079004b006500 790027002c0020004e0027006e
0075006c006c0027002c0020004e0027006e0075006c006c00 27002c00200030007800300031
002c00200031002c0031002c004e00270049004a0055004e00 43002d004c0055004400440027
002c0020003200200065006e0064002000
> e006?Y6Y6
> error:
> exec sp_MSadd_snapshot_history @.agent_id = 5, @.runstatus = 6, @.comments =
> N'Line 1: Incorrect syntax near ''e006''.', @.delivered_transactions = 1,
> @.delivered_commands = 0, @.log_error = 1,

Error in dbcc From Osql

Hi,
i get this error when i run Dbcc on one of my production server database
From Osql Utility.
Msg 1934, Level 16, State 1, Server JorSRv3, Line 1
DBCC failed because the following SET options have incorrect settings:
'QUOTED_IDENTIFIER, ARITHABORT'.NULL
But when i run Dbcc from QA Utility i dont get any error and the Dbbc Gives
me CHECKDB found 0 allocation errors and 0 consistency errors in database I
tried to set
SET ARITHABORT Off
SET QUOTED_IDENTIFIER Off in my osql comand but still i get the same error
ThanksHi,
> SET ARITHABORT Off
> SET QUOTED_IDENTIFIER Off in my osql comand but still i get the same error
TRY
SET ARITHABORT ON
SET QUOTED_IDENTIFIER ON
--
SHINICHI YONEDA MXL04371@.nifty.ne.jp
Microsoft Most Valuable Professional
MVP for SQL Server 2002-2005
"dines" <dines@.discussions.microsoft.com> wrote in message
news:CDB35652-383C-4A62-953B-2386CAA5A8BF@.microsoft.com...
> Hi,
> i get this error when i run Dbcc on one of my production server database
> From Osql Utility.
> Msg 1934, Level 16, State 1, Server JorSRv3, Line 1
> DBCC failed because the following SET options have incorrect settings:
> 'QUOTED_IDENTIFIER, ARITHABORT'.NULL
> But when i run Dbcc from QA Utility i dont get any error and the Dbbc
Gives
> me CHECKDB found 0 allocation errors and 0 consistency errors in database
I
> tried to set
> SET ARITHABORT Off
> SET QUOTED_IDENTIFIER Off in my osql comand but still i get the same error
> Thanks
>|||Hi,
I tried that too but still i get the same error
Msg 1934, Level 16, State 1, Server JorSRv3, Line 1
DBCC failed because the following SET options have incorrect settings:
'QUOTED_IDENTIFIER, ARITHABORT'.NULL
thanks
"Shinichi Yoneda" wrote:
> Hi,
> > SET ARITHABORT Off
> > SET QUOTED_IDENTIFIER Off in my osql comand but still i get the same error
> TRY
> SET ARITHABORT ON
> SET QUOTED_IDENTIFIER ON
> --
> SHINICHI YONEDA MXL04371@.nifty.ne.jp
> Microsoft Most Valuable Professional
> MVP for SQL Server 2002-2005
> "dines" <dines@.discussions.microsoft.com> wrote in message
> news:CDB35652-383C-4A62-953B-2386CAA5A8BF@.microsoft.com...
> > Hi,
> >
> > i get this error when i run Dbcc on one of my production server database
> > From Osql Utility.
> >
> > Msg 1934, Level 16, State 1, Server JorSRv3, Line 1
> > DBCC failed because the following SET options have incorrect settings:
> > 'QUOTED_IDENTIFIER, ARITHABORT'.NULL
> >
> > But when i run Dbcc from QA Utility i dont get any error and the Dbbc
> Gives
> > me CHECKDB found 0 allocation errors and 0 consistency errors in database
> I
> > tried to set
> > SET ARITHABORT Off
> > SET QUOTED_IDENTIFIER Off in my osql comand but still i get the same error
> >
> > Thanks
> >
>

Error in dbcc From Osql

Hi,
i get this error when i run Dbcc on one of my production server database
From Osql Utility.
Msg 1934, Level 16, State 1, Server JorSRv3, Line 1
DBCC failed because the following SET options have incorrect settings:
'QUOTED_IDENTIFIER, ARITHABORT'.NULL
But when i run Dbcc from QA Utility i dont get any error and the Dbbc Gives
me CHECKDB found 0 allocation errors and 0 consistency errors in database I
tried to set
SET ARITHABORT Off
SET QUOTED_IDENTIFIER Off in my osql comand but still i get the same error
Thanks
Hi,

> SET ARITHABORT Off
> SET QUOTED_IDENTIFIER Off in my osql comand but still i get the same error
TRY
SET ARITHABORT ON
SET QUOTED_IDENTIFIER ON
SHINICHI YONEDA MXL04371@.nifty.ne.jp
Microsoft Most Valuable Professional
MVP for SQL Server 2002-2005
"dines" <dines@.discussions.microsoft.com> wrote in message
news:CDB35652-383C-4A62-953B-2386CAA5A8BF@.microsoft.com...
> Hi,
> i get this error when i run Dbcc on one of my production server database
> From Osql Utility.
> Msg 1934, Level 16, State 1, Server JorSRv3, Line 1
> DBCC failed because the following SET options have incorrect settings:
> 'QUOTED_IDENTIFIER, ARITHABORT'.NULL
> But when i run Dbcc from QA Utility i dont get any error and the Dbbc
Gives
> me CHECKDB found 0 allocation errors and 0 consistency errors in database
I
> tried to set
> SET ARITHABORT Off
> SET QUOTED_IDENTIFIER Off in my osql comand but still i get the same error
> Thanks
>
|||Hi,
I tried that too but still i get the same error
Msg 1934, Level 16, State 1, Server JorSRv3, Line 1
DBCC failed because the following SET options have incorrect settings:
'QUOTED_IDENTIFIER, ARITHABORT'.NULL
thanks
"Shinichi Yoneda" wrote:

> Hi,
> TRY
> SET ARITHABORT ON
> SET QUOTED_IDENTIFIER ON
> --
> SHINICHI YONEDA MXL04371@.nifty.ne.jp
> Microsoft Most Valuable Professional
> MVP for SQL Server 2002-2005
> "dines" <dines@.discussions.microsoft.com> wrote in message
> news:CDB35652-383C-4A62-953B-2386CAA5A8BF@.microsoft.com...
> Gives
> I
>
|||Try to execute the following statement in both QA and with OSQL:
DBCC USEROPTIONS
Then compare the two. This command will tell you the current settings under each API. QA sets many environment values quite differently than other APIs.
Sincerely,
Anthony Thomas

"dines" <dines@.discussions.microsoft.com> wrote in message news:5A9AE886-FA9B-440E-8A38-CCF3AF110083@.microsoft.com...
Hi,
I tried that too but still i get the same error
Msg 1934, Level 16, State 1, Server JorSRv3, Line 1
DBCC failed because the following SET options have incorrect settings:
'QUOTED_IDENTIFIER, ARITHABORT'.NULL
thanks
"Shinichi Yoneda" wrote:

> Hi,
>
> TRY
> SET ARITHABORT ON
> SET QUOTED_IDENTIFIER ON
>
> --
> SHINICHI YONEDA MXL04371@.nifty.ne.jp
> Microsoft Most Valuable Professional
> MVP for SQL Server 2002-2005
>
> "dines" <dines@.discussions.microsoft.com> wrote in message
> news:CDB35652-383C-4A62-953B-2386CAA5A8BF@.microsoft.com...
> Gives
> I
>
>

Error in dbcc From Osql

Hi,
i get this error when i run Dbcc on one of my production server database
From Osql Utility.
Msg 1934, Level 16, State 1, Server JorSRv3, Line 1
DBCC failed because the following SET options have incorrect settings:
'QUOTED_IDENTIFIER, ARITHABORT'.NULL
But when i run Dbcc from QA Utility i dont get any error and the Dbbc Gives
me CHECKDB found 0 allocation errors and 0 consistency errors in database I
tried to set
SET ARITHABORT Off
SET QUOTED_IDENTIFIER Off in my osql comand but still i get the same error
ThanksHi,

> SET ARITHABORT Off
> SET QUOTED_IDENTIFIER Off in my osql comand but still i get the same error
TRY
SET ARITHABORT ON
SET QUOTED_IDENTIFIER ON
SHINICHI YONEDA MXL04371@.nifty.ne.jp
Microsoft Most Valuable Professional
MVP for SQL Server 2002-2005
"dines" <dines@.discussions.microsoft.com> wrote in message
news:CDB35652-383C-4A62-953B-2386CAA5A8BF@.microsoft.com...
> Hi,
> i get this error when i run Dbcc on one of my production server database
> From Osql Utility.
> Msg 1934, Level 16, State 1, Server JorSRv3, Line 1
> DBCC failed because the following SET options have incorrect settings:
> 'QUOTED_IDENTIFIER, ARITHABORT'.NULL
> But when i run Dbcc from QA Utility i dont get any error and the Dbbc
Gives
> me CHECKDB found 0 allocation errors and 0 consistency errors in database
I
> tried to set
> SET ARITHABORT Off
> SET QUOTED_IDENTIFIER Off in my osql comand but still i get the same error
> Thanks
>|||Hi,
I tried that too but still i get the same error
Msg 1934, Level 16, State 1, Server JorSRv3, Line 1
DBCC failed because the following SET options have incorrect settings:
'QUOTED_IDENTIFIER, ARITHABORT'.NULL
thanks
"Shinichi Yoneda" wrote:

> Hi,
>
> TRY
> SET ARITHABORT ON
> SET QUOTED_IDENTIFIER ON
> --
> SHINICHI YONEDA MXL04371@.nifty.ne.jp
> Microsoft Most Valuable Professional
> MVP for SQL Server 2002-2005
> "dines" <dines@.discussions.microsoft.com> wrote in message
> news:CDB35652-383C-4A62-953B-2386CAA5A8BF@.microsoft.com...
> Gives
> I
>|||Try to execute the following statement in both QA and with OSQL:
DBCC USEROPTIONS
Then compare the two. This command will tell you the current settings under
each API. QA sets many environment values quite differently than other API
s.
Sincerely,
Anthony Thomas
--
"dines" <dines@.discussions.microsoft.com> wrote in message news:5A9AE886-F
A9B-440E-8A38-CCF3AF110083@.microsoft.com...
Hi,
I tried that too but still i get the same error
Msg 1934, Level 16, State 1, Server JorSRv3, Line 1
DBCC failed because the following SET options have incorrect settings:
'QUOTED_IDENTIFIER, ARITHABORT'.NULL
thanks
"Shinichi Yoneda" wrote:

> Hi,
>
> TRY
> SET ARITHABORT ON
> SET QUOTED_IDENTIFIER ON
>
> --
> SHINICHI YONEDA MXL04371@.nifty.ne.jp
> Microsoft Most Valuable Professional
> MVP for SQL Server 2002-2005
>
> "dines" <dines@.discussions.microsoft.com> wrote in message
> news:CDB35652-383C-4A62-953B-2386CAA5A8BF@.microsoft.com...
> Gives
> I
>
>

Error in blobman.cpp

I have just recently begun to experience a rather odd problem with a query
that has worked fine in the past. Now when I run it I get the following
error.
Server: Msg 3624, Level 20, State 1, Line 1
Location: blobman.cpp:2564
Expression: outBufLen >= inBufLen + OVERHEAD
SPID: 64
Process ID: 1240
Connection Broken.
Has anyone seen this error before? Is there any solution. I have been told
that there is a potential memory leak with the SQL Server 2000 by one of the
gentlemen monitoring our SQL Server. He says that he watches the memory for
the program slowly expand over the course of time until it forces a reboot
of the server machine. Could this be related?
Any help would be greatly appreciated.
Regards,
Daniel Hobert
Can you post your query with required information to repro it? Also check
the errorlog to see if you can find anything relevant to this error message.
It is possible that it could be a bug, however I have read about similar
errors occurring when using ALTER table ALTER column on text/image columns
which is not supported in SQL Server.
Anith
|||It's a simple select query, actually I've done a bit more research and it
appears as if this is the result of some corrupted indexes within the table
in question. I tried using dbcc checktable with the repair_all option but
it seems like the issues are such that I am going to have to do a repair and
risk losing some of the data in the table.
Thanks for the help,
Daniel
"Anith Sen" <anith@.bizdatasolutions.com> wrote in message
news:uLJWTvgiEHA.396@.TK2MSFTNGP12.phx.gbl...
> Can you post your query with required information to repro it? Also check
> the errorlog to see if you can find anything relevant to this error
message.
> It is possible that it could be a bug, however I have read about similar
> errors occurring when using ALTER table ALTER column on text/image columns
> which is not supported in SQL Server.
> --
> Anith
>
|||actually, it was the repair_rebuild option that I used and that didn't do
the trick. It seems like I'm going to have to use the
repair_allow_data_loss option and just hope that too much data wasn't lost.
- Daniel
"Daniel Hobert" <daniel@.cyberspacehq.com> wrote in message
news:412ba505$0$8088$a1866201@.newsreader.dsl.net.. .
> It's a simple select query, actually I've done a bit more research and it
> appears as if this is the result of some corrupted indexes within the
table
> in question. I tried using dbcc checktable with the repair_all option but
> it seems like the issues are such that I am going to have to do a repair
and[vbcol=seagreen]
> risk losing some of the data in the table.
> Thanks for the help,
> Daniel
> "Anith Sen" <anith@.bizdatasolutions.com> wrote in message
> news:uLJWTvgiEHA.396@.TK2MSFTNGP12.phx.gbl...
check[vbcol=seagreen]
> message.
columns
>
|||Have you run DBCC CHECKDB? If that is clean, then this is probably a bug.
Are you running SQL2000 SP3? It might help.
Wei Xiao
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Daniel Hobert" <daniel@.cyberspacehq.com> wrote in message
news:412b878a$0$65562$a1866201@.newsreader.dsl.net. ..
> I have just recently begun to experience a rather odd problem with a query
> that has worked fine in the past. Now when I run it I get the following
> error.
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: blobman.cpp:2564
> Expression: outBufLen >= inBufLen + OVERHEAD
> SPID: 64
> Process ID: 1240
> Connection Broken.
> Has anyone seen this error before? Is there any solution. I have been
told
> that there is a potential memory leak with the SQL Server 2000 by one of
the
> gentlemen monitoring our SQL Server. He says that he watches the memory
for
> the program slowly expand over the course of time until it forces a reboot
> of the server machine. Could this be related?
> Any help would be greatly appreciated.
> Regards,
> Daniel Hobert
>

Error in blobman.cpp

I have just recently begun to experience a rather odd problem with a query
that has worked fine in the past. Now when I run it I get the following
error.
Server: Msg 3624, Level 20, State 1, Line 1
Location: blobman.cpp:2564
Expression: outBufLen >= inBufLen + OVERHEAD
SPID: 64
Process ID: 1240
Connection Broken.
Has anyone seen this error before? Is there any solution. I have been told
that there is a potential memory leak with the SQL Server 2000 by one of the
gentlemen monitoring our SQL Server. He says that he watches the memory for
the program slowly expand over the course of time until it forces a reboot
of the server machine. Could this be related?
Any help would be greatly appreciated.
Regards,
Daniel HobertCan you post your query with required information to repro it? Also check
the errorlog to see if you can find anything relevant to this error message.
It is possible that it could be a bug, however I have read about similar
errors occurring when using ALTER table ALTER column on text/image columns
which is not supported in SQL Server.
Anith|||It's a simple select query, actually I've done a bit more research and it
appears as if this is the result of some corrupted indexes within the table
in question. I tried using dbcc checktable with the repair_all option but
it seems like the issues are such that I am going to have to do a repair and
risk losing some of the data in the table.
Thanks for the help,
Daniel
"Anith Sen" <anith@.bizdatasolutions.com> wrote in message
news:uLJWTvgiEHA.396@.TK2MSFTNGP12.phx.gbl...
> Can you post your query with required information to repro it? Also check
> the errorlog to see if you can find anything relevant to this error
message.
> It is possible that it could be a bug, however I have read about similar
> errors occurring when using ALTER table ALTER column on text/image columns
> which is not supported in SQL Server.
> --
> Anith
>|||actually, it was the repair_rebuild option that I used and that didn't do
the trick. It seems like I'm going to have to use the
repair_allow_data_loss option and just hope that too much data wasn't lost.
- Daniel
"Daniel Hobert" <daniel@.cyberspacehq.com> wrote in message
news:412ba505$0$8088$a1866201@.newsreader
.dsl.net...
> It's a simple select query, actually I've done a bit more research and it
> appears as if this is the result of some corrupted indexes within the
table
> in question. I tried using dbcc checktable with the repair_all option but
> it seems like the issues are such that I am going to have to do a repair
and
> risk losing some of the data in the table.
> Thanks for the help,
> Daniel
> "Anith Sen" <anith@.bizdatasolutions.com> wrote in message
> news:uLJWTvgiEHA.396@.TK2MSFTNGP12.phx.gbl...
check[vbcol=seagreen]
> message.
columns[vbcol=seagreen]
>|||Have you run DBCC CHECKDB? If that is clean, then this is probably a bug.
Are you running SQL2000 SP3? It might help.
Wei Xiao
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Daniel Hobert" <daniel@.cyberspacehq.com> wrote in message
news:412b878a$0$65562$a1866201@.newsreade
r.dsl.net...
> I have just recently begun to experience a rather odd problem with a query
> that has worked fine in the past. Now when I run it I get the following
> error.
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: blobman.cpp:2564
> Expression: outBufLen >= inBufLen + OVERHEAD
> SPID: 64
> Process ID: 1240
> Connection Broken.
> Has anyone seen this error before? Is there any solution. I have been
told
> that there is a potential memory leak with the SQL Server 2000 by one of
the
> gentlemen monitoring our SQL Server. He says that he watches the memory
for
> the program slowly expand over the course of time until it forces a reboot
> of the server machine. Could this be related?
> Any help would be greatly appreciated.
> Regards,
> Daniel Hobert
>