Showing posts with label errors. Show all posts
Showing posts with label errors. Show all posts

Monday, March 19, 2012

[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed

Hi,
Anyone seeing these errors before?
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
[sqsrvres] printODBCError: sqlstate = 01000; native error = 2746; message =
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
[sqsrvres] printODBCError: sqlstate = 08S01; native error = b; message =
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
[sqsrvres] OnlineThread: QP is not online.
active/active sql2k cluster with sp3a plus MS03-031 hotfix. I have seen
these errors couple of times before. I have searched on newsgroup and did not
find any answer. Really appreciate if anyone can help.
thanks in advance.
David
These are generated when the cluster service fails to connect to SQL Server
during its check of the resource. Some error occurred to affect the
connection.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks Rand for the reply.
I did not see any sql error in the sql log. In system log, there is no sign
of failover. I think i might need to setup performance monitor to trap the
resource usage if it happens next time.
thanks
David
"Rand Boyd [MSFT]" wrote:

> These are generated when the cluster service fails to connect to SQL Server
> during its check of the resource. Some error occurred to affect the
> connection.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||There probably will not be any error in the SQL errorlog. It could be a
transient error. Teh cluister serveice will try several times before it
will fail the resource.
Ranf
This posting is provided "as is" with no warranties and confers no rights.

[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed

Hi,
Anyone seeing these errors before?
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
[sqsrvres] printODBCError: sqlstate = 01000; native error = 2746; messag
e =
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (rec
v()).
[sqsrvres] printODBCError: sqlstate = 08S01; native error = b; message =
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network err
or.
[sqsrvres] OnlineThread: QP is not online.
active/active sql2k cluster with sp3a plus MS03-031 hotfix. I have seen
these errors couple of times before. I have searched on newsgroup and did no
t
find any answer. Really appreciate if anyone can help.
thanks in advance.
DavidThese are generated when the cluster service fails to connect to SQL Server
during its check of the resource. Some error occurred to affect the
connection.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thanks Rand for the reply.
I did not see any sql error in the sql log. In system log, there is no sign
of failover. I think i might need to setup performance monitor to trap the
resource usage if it happens next time.
thanks
David
"Rand Boyd [MSFT]" wrote:

> These are generated when the cluster service fails to connect to SQL Serve
r
> during its check of the resource. Some error occurred to affect the
> connection.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>|||There probably will not be any error in the SQL errorlog. It could be a
transient error. Teh cluister serveice will try several times before it
will fail the resource.
Ranf
This posting is provided "as is" with no warranties and confers no rights.

[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed

Hi,
Anyone seeing these errors before?
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
[sqsrvres] printODBCError: sqlstate = 01000; native error = 2746; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
[sqsrvres] printODBCError: sqlstate = 08S01; native error = b; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
[sqsrvres] OnlineThread: QP is not online.
active/active sql2k cluster with sp3a plus MS03-031 hotfix. I have seen
these errors couple of times before. I have searched on newsgroup and did not
find any answer. Really appreciate if anyone can help.
thanks in advance.
DavidThese are generated when the cluster service fails to connect to SQL Server
during its check of the resource. Some error occurred to affect the
connection.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thanks Rand for the reply.
I did not see any sql error in the sql log. In system log, there is no sign
of failover. I think i might need to setup performance monitor to trap the
resource usage if it happens next time.
thanks
David
"Rand Boyd [MSFT]" wrote:
> These are generated when the cluster service fails to connect to SQL Server
> during its check of the resource. Some error occurred to affect the
> connection.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>|||There probably will not be any error in the SQL errorlog. It could be a
transient error. Teh cluister serveice will try several times before it
will fail the resource.
Ranf
This posting is provided "as is" with no warranties and confers no rights.

Tuesday, March 6, 2012

[Microsoft][ODBC Text Driver] error

Hello,
I am trying to import test file into a SQL Server 2000 database. If I
run the dts package manually I do not receive any errors. However when
I try and attempt to run the same package with dtsrun I receive the
following error.
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled
correctly and that you are connected to the server on which the file
resides
The path of the file is set correctly in the ODBC connection. Any
insight or assistance would be imprecated.
ThanksOn Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> Hello,
> I am trying to import test file into a SQL Server 2000 database. If I
> run the dts package manually I do not receive any errors. However when
> I try and attempt to run the same package with dtsrun I receive the
> following error.
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled
> correctly and that you are connected to the server on which the file
> resides
> The path of the file is set correctly in the ODBC connection. Any
> insight or assistance would be imprecated.
> Thanks
Hi
Are you running DTSRun from a command prompt?
Why are you using a DSN?
Have you tried creating the package using the Import Wizard?
John|||On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
> > Hello,
> > I am trying to import test file into a SQL Server 2000 database. If I
> > run the dts package manually I do not receive any errors. However when
> > I try and attempt to run the same package with dtsrun I receive the
> > following error.
> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > valid path. Make sure that the path name is spelled
> > correctly and that you are connected to the server on which the file
> > resides
> > The path of the file is set correctly in the ODBC connection. Any
> > insight or assistance would be imprecated.
> > Thanks
> Hi
> Are you running DTSRun from a command prompt?
> Why are you using a DSN?
> Have you tried creating the package using the Import Wizard?
> John
I am trying to run the schedule the package from using .xp_cmdshell
and DTSRun , The package will run if execute it from Enterprise Manager|||On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
> > On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > Hello,
> > > I am trying to import test file into a SQL Server 2000 database. If I
> > > run the dts package manually I do not receive any errors. However when
> > > I try and attempt to run the same package with dtsrun I receive the
> > > following error.
> > > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > > valid path. Make sure that the path name is spelled
> > > correctly and that you are connected to the server on which the file
> > > resides
> > > The path of the file is set correctly in the ODBC connection. Any
> > > insight or assistance would be imprecated.
> > > Thanks
> > Hi
> > Are you running DTSRun from a command prompt?
> > Why are you using a DSN?
> > Have you tried creating the package using the Import Wizard?
> > John
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> - Show quoted text -
Hi
If you manually run the command from a command prompt does it work?
If xp_cmdshell is running from a job, then make sure service accounts
have access to the directory/file.
John|||On Jun 11, 1:30 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
> > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > > Hello,
> > > > I am trying to import test file into a SQL Server 2000 database. If I
> > > > run the dts package manually I do not receive any errors. However when
> > > > I try and attempt to run the same package with dtsrun I receive the
> > > > following error.
> > > > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > > > valid path. Make sure that the path name is spelled
> > > > correctly and that you are connected to the server on which the file
> > > > resides
> > > > The path of the file is set correctly in the ODBC connection. Any
> > > > insight or assistance would be imprecated.
> > > > Thanks
> > > Hi
> > > Are you running DTSRun from a command prompt?
> > > Why are you using a DSN?
> > > Have you tried creating the package using the Import Wizard?
> > > John
> > I am trying to run the schedule the package from using .xp_cmdshell
> > and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> > - Show quoted text -
> Hi
> If you manually run the command from a command prompt does it work?
> If xp_cmdshell is running from a job, then make sure service accounts
> have access to the directory/file.
> John
Thanks, If I manually run the command from the command prompt it does
work, however if I try and run using xp_cmdshell I receive the error.
Both SQLAgent and MSSQL services have access to the directory/file|||When you are running it from EM, the package will use your logon to
determine the right and security to access a file but this will not be the
case when running it from a service (xp_cmdshell, DTS_Run or any other
service like SQL-Agent).
Also, if you are not using a UNC pathway but a drive letter (such as C:\);
many of these drive letters will be unknown to system accounts and other
accounts other than your own login. If you have used a driver letter, you
should replace with its full UNC name.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
<mtatlow@.gmail.com> wrote in message
news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>>
>> > Hello,
>> > I am trying to import test file into a SQL Server 2000 database. If I
>> > run the dts package manually I do not receive any errors. However when
>> > I try and attempt to run the same package with dtsrun I receive the
>> > following error.
>> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
>> > valid path. Make sure that the path name is spelled
>> > correctly and that you are connected to the server on which the file
>> > resides
>> > The path of the file is set correctly in the ODBC connection. Any
>> > insight or assistance would be imprecated.
>> > Thanks
>> Hi
>> Are you running DTSRun from a command prompt?
>> Why are you using a DSN?
>> Have you tried creating the package using the Import Wizard?
>> John
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager
>|||On Jun 11, 9:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 11, 1:30 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
> > On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > > On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > > > Hello,
> > > > > I am trying to import test file into a SQL Server 2000 database. If I
> > > > > run the dts package manually I do not receive any errors. However when
> > > > > I try and attempt to run the same package with dtsrun I receive the
> > > > > following error.
> > > > > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > > > > valid path. Make sure that the path name is spelled
> > > > > correctly and that you are connected to the server on which the file
> > > > > resides
> > > > > The path of the file is set correctly in the ODBC connection. Any
> > > > > insight or assistance would be imprecated.
> > > > > Thanks
> > > > Hi
> > > > Are you running DTSRun from a command prompt?
> > > > Why are you using a DSN?
> > > > Have you tried creating the package using the Import Wizard?
> > > > John
> > > I am trying to run the schedule the package from using .xp_cmdshell
> > > and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> > > - Show quoted text -
> > Hi
> > If you manually run the command from a command prompt does it work?
> > If xp_cmdshell is running from a job, then make sure service accounts
> > have access to the directory/file.
> > John
> Thanks, If I manually run the command from the command prompt it does
> work, however if I try and run using xp_cmdshell I receive the error.
> Both SQLAgent and MSSQL services have access to the directory/file- Hide quoted text -
> - Show quoted text -
Hi
You don't say what the service accounts are. The LOCALSYSTEM will not
have access to network resources, so it would have to be a domain
account. Try logging in as this account and run the package from the
command prompt.
John|||I am using a domain account that has access to the file. I am using
the [ODBC Text Driver] which does not allow you to use a UNC in the
pathway.
On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
blanks, no spam please)> wrote:
> When you are running it from EM, the package will use your logon to
> determine the right and security to access a file but this will not be the
> case when running it from a service (xp_cmdshell, DTS_Run or any other
> service like SQL-Agent).
> Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> many of these drive letters will be unknown to system accounts and other
> accounts other than your own login. If you have used a driver letter, you
> should replace with its full UNC name.
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
> <mtat...@.gmail.com> wrote in message
> news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> >> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> >> > Hello,
> >> > I am trying to import test file into a SQL Server 2000 database. If I
> >> > run the dts package manually I do not receive any errors. However when
> >> > I try and attempt to run the same package with dtsrun I receive the
> >> > following error.
> >> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> >> > valid path. Make sure that the path name is spelled
> >> > correctly and that you are connected to the server on which the file
> >> > resides
> >> > The path of the file is set correctly in the ODBC connection. Any
> >> > insight or assistance would be imprecated.
> >> > Thanks
> >> Hi
> >> Are you running DTSRun from a command prompt?
> >> Why are you using a DSN?
> >> Have you tried creating the package using the Import Wizard?
> >> John
> > I am trying to run the schedule the package from using .xp_cmdshell
> > and DTSRun , The package will run if execute it from Enterprise Manager|||On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> I am using a domain account that has access to the file. I am using
> the [ODBC Text Driver] which does not allow you to use a UNC in the
> pathway.
> On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> blanks, no spam please)> wrote:
>
> > When you are running it from EM, the package will use your logon to
> > determine the right and security to access a file but this will not be the
> > case when running it from a service (xp_cmdshell, DTS_Run or any other
> > service like SQL-Agent).
> > Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> > many of these drive letters will be unknown to system accounts and other
> > accounts other than your own login. If you have used a driver letter, you
> > should replace with its full UNC name.
> > --
> > Sylvain Lafontaine, ing.
> > MVP - Technologies Virtual-PC
> > E-mail: sylvain aei ca (fill the blanks, no spam please)
> > <mtat...@.gmail.com> wrote in message
> >news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> > > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > >> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > >> > Hello,
> > >> > I am trying to import test file into a SQL Server 2000 database. If I
> > >> > run the dts package manually I do not receive any errors. However when
> > >> > I try and attempt to run the same package with dtsrun I receive the
> > >> > following error.
> > >> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > >> > valid path. Make sure that the path name is spelled
> > >> > correctly and that you are connected to the server on which the file
> > >> > resides
> > >> > The path of the file is set correctly in the ODBC connection. Any
> > >> > insight or assistance would be imprecated.
> > >> > Thanks
> > >> Hi
> > >> Are you running DTSRun from a command prompt?
> > >> Why are you using a DSN?
> > >> Have you tried creating the package using the Import Wizard?
> > >> John
> > > I am trying to run the schedule the package from using .xp_cmdshell
> > > and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> - Show quoted text -
Hi
So logging in as this account, you can run the job/package
sucessfully? Have you used the /L command to log output to a file?
John|||On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
> > I am using a domain account that has access to the file. I am using
> > the [ODBC Text Driver] which does not allow you to use a UNC in the
> > pathway.
> > On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> > blanks, no spam please)> wrote:
> > > When you are running it from EM, the package will use your logon to
> > > determine the right and security to access a file but this will not be the
> > > case when running it from a service (xp_cmdshell, DTS_Run or any other
> > > service like SQL-Agent).
> > > Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> > > many of these drive letters will be unknown to system accounts and other
> > > accounts other than your own login. If you have used a driver letter, you
> > > should replace with its full UNC name.
> > > --
> > > Sylvain Lafontaine, ing.
> > > MVP - Technologies Virtual-PC
> > > E-mail: sylvain aei ca (fill the blanks, no spam please)
> > > <mtat...@.gmail.com> wrote in message
> > >news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> > > > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > >> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > >> > Hello,
> > > >> > I am trying to import test file into a SQL Server 2000 database. If I
> > > >> > run the dts package manually I do not receive any errors. However when
> > > >> > I try and attempt to run the same package with dtsrun I receive the
> > > >> > following error.
> > > >> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> > > >> > valid path. Make sure that the path name is spelled
> > > >> > correctly and that you are connected to the server on which the file
> > > >> > resides
> > > >> > The path of the file is set correctly in the ODBC connection. Any
> > > >> > insight or assistance would be imprecated.
> > > >> > Thanks
> > > >> Hi
> > > >> Are you running DTSRun from a command prompt?
> > > >> Why are you using a DSN?
> > > >> Have you tried creating the package using the Import Wizard?
> > > >> John
> > > > I am trying to run the schedule the package from using .xp_cmdshell
> > > > and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> > - Show quoted text -
> Hi
> So logging in as this account, you can run the job/package
> sucessfully? Have you used the /L command to log output to a file?
> John
This is the output that I get when I use xp_cmdshell
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSDataPumpTask_1
DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259
(80004005)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
Error Detail Records:
Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
DTSRun: Package execution complete.
NULL
this is the output when I run from the cmd prompt
The execution of the following DTS Package succeeded:
Package Name: test
Package Description: (null)
Package ID: {28220C92-CA63-4664-B356-2155FC002749}
Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
Executed On: SERVERNAME
Executed By: username
Execution Started: 6/12/2007 9:31:01 AM
Execution Completed: 6/12/2007 9:31:01 AM
Total Execution Time: 0.64 seconds
Package Steps execution information:
Step 'DTSStep_DTSDataPumpTask_1' succeeded
Step Execution Started: 6/12/2007 9:31:01 AM
Step Execution Completed: 6/12/2007 9:31:01 AM
Total Step Execution Time: 0.593 seconds
Progress count in Step: 1672
****************************************************************************************************|||On Jun 12, 2:37 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
> > On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> > > I am using a domain account that has access to the file. I am using
> > > the [ODBC Text Driver] which does not allow you to use a UNC in the
> > > pathway.
> > > On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> > > blanks, no spam please)> wrote:
> > > > When you are running it from EM, the package will use your logon to
> > > > determine the right and security to access a file but this will not= be the
> > > > case when running it from a service (xp_cmdshell, DTS_Run or any ot=her
> > > > service like SQL-Agent).
> > > > Also, if you are not using a UNC pathway but a drive letter (such a=s C:\);
> > > > many of these drive letters will be unknown to system accounts and =other
> > > > accounts other than your own login. If you have used a driver lett=er, you
> > > > should replace with its full UNC name.
> > > > --
> > > > Sylvain Lafontaine, ing.
> > > > MVP - Technologies Virtual-PC
> > > > E-mail: sylvain aei ca (fill the blanks, no spam please)
> > > > <mtat...@.gmail.com> wrote in message
> > > >news:1181582401.465253.261890@.w5g2000hsg.googlegroups.com...
> > > > > On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > > > >> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrot=e:
> > > > >> > Hello,
> > > > >> > I am trying to import test file into a SQL Server 2000 databas=e=2E If I
> > > > >> > run the dts package manually I do not receive any errors. Howe=ver when
> > > > >> > I try and attempt to run the same package with dtsrun I receiv=e the
> > > > >> > following error.
> > > > >> > Error string: [Microsoft][ODBC Text Driver] '(unknown)' is no=t a
> > > > >> > valid path. Make sure that the path name is spelled
> > > > >> > correctly and that you are connected to the server on which th=e file
> > > > >> > resides
> > > > >> > The path of the file is set correctly in the ODBC connection. =Any
> > > > >> > insight or assistance would be imprecated.
> > > > >> > Thanks
> > > > >> Hi
> > > > >> Are you running DTSRun from a command prompt?
> > > > >> Why are you using a DSN?
> > > > >> Have you tried creating the package using the Import Wizard?
> > > > >> John
> > > > > I am trying to run the schedule the package from using .xp_cmdsh=ell
> > > > > and DTSRun , The package will run if execute it from Enterprise M=anager- Hide quoted text -
> > > - Show quoted text -
> > Hi
> > So logging in as this account, you can run the job/package
> > sucessfully? Have you used the /L command to log output to a file?
> > John
> This is the output that I get when I use xp_cmdshell
> DTSRun: Loading...
> DTSRun: Executing...
> DTSRun OnStart: DTSStep_DTSDataPumpTask_1
> DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error =3D -2147467259
> (80004005)
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled correctly and
> that you are connected to the server on which the file resides.
> Error source: Microsoft OLE DB Provider for ODBC Drivers
> Help file:
> Help context: 0
> Error Detail Records:
> Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled correctly and
> that you are connected to the server on which the file resides.
> Error source: Microsoft OLE DB Provider for ODBC Drivers
> Help file:
> Help context: 0
> DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
> DTSRun: Package execution complete.
> NULL
> this is the output when I run from the cmd prompt
> The execution of the following DTS Package succeeded:
> Package Name: test
> Package Description: (null)
> Package ID: {28220C92-CA63-4664-B356-2155FC002749}
> Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
> Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
> Executed On: SERVERNAME
> Executed By: username
> Execution Started: 6/12/2007 9:31:01 AM
> Execution Completed: 6/12/2007 9:31:01 AM
> Total Execution Time: 0.64 seconds
> Package Steps execution information:
> Step 'DTSStep_DTSDataPumpTask_1' succeeded
> Step Execution Started: 6/12/2007 9:31:01 AM
> Step Execution Completed: 6/12/2007 9:31:01 AM
> Total Step Execution Time: 0.593 seconds
> Progress count in Step: 1672
> *************************************************************************=**=AD*************************- Hide quoted text -
> - Show quoted text -
Although you are not using ASP this article gives reasons for this
error number http://support.microsoft.com/kb/306518 especially
http://support.microsoft.com/kb/306269
John

[Microsoft][ODBC Text Driver] error

Hello,
I am trying to import test file into a SQL Server 2000 database. If I
run the dts package manually I do not receive any errors. However when
I try and attempt to run the same package with dtsrun I receive the
following error.
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled
correctly and that you are connected to the server on which the file
resides
The path of the file is set correctly in the ODBC connection. Any
insight or assistance would be imprecated.
Thanks
On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> Hello,
> I am trying to import test file into a SQL Server 2000 database. If I
> run the dts package manually I do not receive any errors. However when
> I try and attempt to run the same package with dtsrun I receive the
> following error.
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled
> correctly and that you are connected to the server on which the file
> resides
> The path of the file is set correctly in the ODBC connection. Any
> insight or assistance would be imprecated.
> Thanks
Hi
Are you running DTSRun from a command prompt?
Why are you using a DSN?
Have you tried creating the package using the Import Wizard?
John
|||On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 11, 3:16 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
>
>
>
> Hi
> Are you running DTSRun from a command prompt?
> Why are you using a DSN?
> Have you tried creating the package using the Import Wizard?
> John
I am trying to run the schedule the package from using .xp_cmdshell
and DTSRun , The package will run if execute it from Enterprise Manager
|||On Jun 11, 6:20 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
>
>
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager- Hide quoted text -
> - Show quoted text -
Hi
If you manually run the command from a command prompt does it work?
If xp_cmdshell is running from a job, then make sure service accounts
have access to the directory/file.
John
|||When you are running it from EM, the package will use your logon to
determine the right and security to access a file but this will not be the
case when running it from a service (xp_cmdshell, DTS_Run or any other
service like SQL-Agent).
Also, if you are not using a UNC pathway but a drive letter (such as C:\);
many of these drive letters will be unknown to system accounts and other
accounts other than your own login. If you have used a driver letter, you
should replace with its full UNC name.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
<mtatlow@.gmail.com> wrote in message
news:1181582401.465253.261890@.w5g2000hsg.googlegro ups.com...
> On Jun 11, 1:08 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> I am trying to run the schedule the package from using .xp_cmdshell
> and DTSRun , The package will run if execute it from Enterprise Manager
>
|||I am using a domain account that has access to the file. I am using
the [ODBC Text Driver] which does not allow you to use a UNC in the
pathway.
On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
blanks, no spam please)> wrote:[vbcol=seagreen]
> When you are running it from EM, the package will use your logon to
> determine the right and security to access a file but this will not be the
> case when running it from a service (xp_cmdshell, DTS_Run or any other
> service like SQL-Agent).
> Also, if you are not using a UNC pathway but a drive letter (such as C:\);
> many of these drive letters will be unknown to system accounts and other
> accounts other than your own login. If you have used a driver letter, you
> should replace with its full UNC name.
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
> <mtat...@.gmail.com> wrote in message
> news:1181582401.465253.261890@.w5g2000hsg.googlegro ups.com...
>
>
>
>
>
>
|||On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> I am using a domain account that has access to the file. I am using
> the [ODBC Text Driver] which does not allow you to use a UNC in the
> pathway.
> On Jun 11, 5:36 pm, "Sylvain Lafontaine" <sylvain aei ca (fill the
> blanks, no spam please)> wrote:
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
Hi
So logging in as this account, you can run the job/package
sucessfully? Have you used the /L command to log output to a file?
John
|||On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> On Jun 12, 12:58 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
> Hi
> So logging in as this account, you can run the job/package
> sucessfully? Have you used the /L command to log output to a file?
> John
This is the output that I get when I use xp_cmdshell
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSDataPumpTask_1
DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259
(80004005)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
Error Detail Records:
Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
DTSRun: Package execution complete.
NULL
this is the output when I run from the cmd prompt
The execution of the following DTS Package succeeded:
Package Name: test
Package Description: (null)
Package ID: {28220C92-CA63-4664-B356-2155FC002749}
Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
Executed On: SERVERNAME
Executed By: username
Execution Started: 6/12/2007 9:31:01 AM
Execution Completed: 6/12/2007 9:31:01 AM
Total Execution Time: 0.64 seconds
Package Steps execution information:
Step 'DTSStep_DTSDataPumpTask_1' succeeded
Step Execution Started: 6/12/2007 9:31:01 AM
Step Execution Completed: 6/12/2007 9:31:01 AM
Total Step Execution Time: 0.593 seconds
Progress count in Step: 1672
************************************************** **************************************************
|||On Jun 12, 2:37 pm, "mtat...@.gmail.com" <mtat...@.gmail.com> wrote:
> On Jun 12, 9:05 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> This is the output that I get when I use xp_cmdshell
> DTSRun: Loading...
> DTSRun: Executing...
> DTSRun OnStart: DTSStep_DTSDataPumpTask_1
> DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259
> (80004005)
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled correctly and
> that you are connected to the server on which the file resides.
> Error source: Microsoft OLE DB Provider for ODBC Drivers
> Help file:
> Help context: 0
> Error Detail Records:
> Error: -2147467259 (80004005); Provider Error: 1023 (3FF)
> Error string: [Microsoft][ODBC Text Driver] '(unknown)' is not a
> valid path. Make sure that the path name is spelled correctly and
> that you are connected to the server on which the file resides.
> Error source: Microsoft OLE DB Provider for ODBC Drivers
> Help file:
> Help context: 0
> DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
> DTSRun: Package execution complete.
> NULL
> this is the output when I run from the cmd prompt
> The execution of the following DTS Package succeeded:
> Package Name: test
> Package Description: (null)
> Package ID: {28220C92-CA63-4664-B356-2155FC002749}
> Package Version: {D70556AF-1AE9-4175-83C7-B623FC755314}
> Package Execution Lineage: {5DD5E480-8567-43F2-BBAA-7F9F9C9E994D}
> Executed On: SERVERNAME
> Executed By: username
> Execution Started: 6/12/2007 9:31:01 AM
> Execution Completed: 6/12/2007 9:31:01 AM
> Total Execution Time: 0.64 seconds
> Package Steps execution information:
> Step 'DTSStep_DTSDataPumpTask_1' succeeded
> Step Execution Started: 6/12/2007 9:31:01 AM
> Step Execution Completed: 6/12/2007 9:31:01 AM
> Total Step Execution Time: 0.593 seconds
> Progress count in Step: 1672
> ************************************************** *************************X************************ *- Hide quoted text -
> - Show quoted text -
Although you are not using ASP this article gives reasons for this
error number http://support.microsoft.com/kb/306518 especially
http://support.microsoft.com/kb/306269
John

[Microsoft][ODBC SQL Server Driver]Timeout expired

Hi,
Our web applications are using COM objects to call sps in
SQL server. We are getting a lot of timeout errors. If
you know why this happens and any fixes pls let me know.
The error looks like following:
[Microsoft][ODBC SQL Server Driver]Timeout expiredhi
I also face to that prob.At last i found the solution for the "timeout
expired" problem. what we
have to do is, we have to edit two windows files calld
,"c:\winnt\system32\drives\ect\hosts.txt"
and "c:\winnt\system32\drives\ect\Lhosts.txt"
we should enter sql server IP and name like this
169.192.2.100 sqlserverName
in both files
Thanks,
indika
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

Sunday, February 19, 2012

[DBNETLIB][ConnectionWrite (send()).] errors

We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.

Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.

Does anyone have any ideas ?

Hi Brian,

I'm having similar issues with my system (new HP server running Win 2003 & SQL 2005 with VB App running on XP Clients, MDAC 2.81). Seems to affect certain PC's, doesn't affect a version of the VB 6 App running locally on the server, or one of the Clients that continually polls the server once per minute, 24/7.

The error handling in the VB App actually writes a log of the error to a SQL Table, which suggests that the connection error occurs, and by the time the user confirms the msgbox prompt the connection comes back up, allowing the log to be written...

I've tried disabling connection pooling in the ADO connection string & the SynAttackProtect REG setting change as discussed at http://www.eggheadcafe.com/ng/microsoft.public.sqlserver.connect/post22689813.asp

Both to no avail....

Was wondering if you'd found a resolution yet?

Best regards

Keith
|||

For your issue, I would try to follow the article http://support.microsoft.com/default.aspx?scid=kb;en-us;899599 to add the registry key. Maybe that will fix your problem. If not, please provide more information on the infrastructure to help us narrow the issue.

HTH

|||umm - our problem appeared to hardware - Dell announced urgent driver updates for the cards in our server, but that didn't entirley solve the problem although it is better. The the support desk for hte application we are using then recomended switching the server to use both TCP/IP and Named Pipes and then adjusting the client config appropriatly. this seems to have resolved our issue

[DBNETLIB][ConnectionWrite (send()).] errors

We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.

Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.

Does anyone have any ideas ?

Hi Brian,

I'm having similar issues with my system (new HP server running Win 2003 & SQL 2005 with VB App running on XP Clients, MDAC 2.81). Seems to affect certain PC's, doesn't affect a version of the VB 6 App running locally on the server, or one of the Clients that continually polls the server once per minute, 24/7.

The error handling in the VB App actually writes a log of the error to a SQL Table, which suggests that the connection error occurs, and by the time the user confirms the msgbox prompt the connection comes back up, allowing the log to be written...

I've tried disabling connection pooling in the ADO connection string & the SynAttackProtect REG setting change as discussed at http://www.eggheadcafe.com/ng/microsoft.public.sqlserver.connect/post22689813.asp

Both to no avail....

Was wondering if you'd found a resolution yet?

Best regards

Keith
|||

For your issue, I would try to follow the article http://support.microsoft.com/default.aspx?scid=kb;en-us;899599 to add the registry key. Maybe that will fix your problem. If not, please provide more information on the infrastructure to help us narrow the issue.

HTH

|||umm - our problem appeared to hardware - Dell announced urgent driver updates for the cards in our server, but that didn't entirley solve the problem although it is better. The the support desk for hte application we are using then recomended switching the server to use both TCP/IP and Named Pipes and then adjusting the client config appropriatly. this seems to have resolved our issue

Thursday, February 16, 2012

[cross-column & cross-row consistency]Transaction Consistency In Sql server 2005 sp2.

(The previous edition of this post has some written errors
which can make what I say unclear .Now those written errors are correctd.)

[cross-column & cross-row consistency]
Transaction Consistency In Sql server 2005 sp2.

How are cross-column and cross-row consistency in SQL SERVER 2000/2005?

Now there is a table named T,and its structure is as follow:
T(value , twice_value),
which means [twice_value] is twice of [value].
I filled it with some rows ,then it looks as follow:
--
value |twice_value
--
1 |2
32 |64
78 |156
--
Then I run the statement:
-
Update T
set
[value] = [value] * 2 ,
[twice_value] = [twice_value] * 2
--(In the previous edition of this post ,here the " * 2 " was fogetten)
-
At this point , towpuzzles arise into my brain:
[1].Is there some isolation leve in which
[VALUES 1] can be read possibly in some cases?

[VALUES 1]
--
value |twice_value
--
1 |2
64 |128
78 |156
--
(Note: every row is consistent,
but the table[64|128] is not consistent against the above "upate".)

[2].Is there some isolation leve in which
[VALUED 2] can be read possibly in some cases?

[VALUED 2]
--
value |twice_value
--
2 |2
32 |64
78 |156
--
(Note:the first row[2|2] it self is not consistent)

What I can make sure is that
[VALUED 1] can be read possibly in some cases when
Table T is updated by the following statement.
-
Update T
set
[value] = [value] * 2 ,
[twice_value] = [twice_value] * 2
--(In the previous edition of this post ,here the " * 2 " was fogetten)
where [value] = 32
Update T
set
[value] = [value] * 2 ,
[twice_value] = [twice_value] * 2
--(In the previous edition of this post ,here the " * 2 " was fogetten)
where not([value] = 32)
-


by the way ,

Is there Anyone that knows available e-paper about "log storage and data storage"?

|||SO EARGERLY FOR SOME ANSWERS.|||MARK|||up|||First, the update command you have listed above cannot create the values you show, since you set [twice_value]=[twice_value], unless you have a trigger setting the twice_value.

Second, the UPDATE statement creates an implicit transaction. Which means either all the records update or none of the records update and if there is a lock, it will wait for that lock to release. So there should be no possible way to create the results you describe after the query succeeds. Unless, you have something else changing the data, like a trigger.

If the isolation level was set to "READ UNCOMMITTED", a query could return what you describe, while the update was running. This is not unique to SP2.

With my corrected UPDATE statement, I cannot duplicate what you describe under any of the 3 versions of 2005, including SP2, I have or 2000 SP4, after the query has finished successfully.

Please post a duplication script of your problem.|||

As Tom Phillips already mentioned your actual scenario is not really clear. But assuming that Tom's interpretation of your question is correct (except in the part that he as far as I can see implicitly supposes that you never run the queries that observe the data in the table concurrently with the updates – but I’m not 100% sure if this time I interpret him correctly), the answers are the following:

In general when reading the row using the interfaces available through T-SQL the transactional cross-column consistency for a single row is guaranteed by the engine for all isolation levels except the READ UNCOMMITTED. One example when the cross-column consistency could be violated when using dirty reads is when certain columns are not physically stored in the row – those include off-row LOB values or the variable length non-LOB columns that were pushed off-row because they don’t fit the data page.

The cross-row consistency is a different story and in order to be absolutely certain that an arbitrary DML statement will never see inconsistent results, one should use the SERAILIZABLE isolation level. For the queries is could also be guaranteed by the SNAPSHOT isolation level. However, in your particular example of the UPDATE statement where no rows are added or deleted, the REPEATABLE READ would also guarantee both the cross-column for a single row, and the cross-row transactional consistency for the entire table for any kind of query.

|||up|||UP|||UP

Saturday, February 11, 2012

@Microsoft: E-Learning Course database mirroring

Hi MS-Guys,

the following E-Learning course has some errors which have to be investigated otherwise the course will be very disappointing for the participants:

Kurs 2938: Datenverfügbarkeitsfeatures in Microsoft? SQL Server? 2005 (this is only the german subject for the course, the link should apply in english versions as well, as the course is actually in english)

While starting the VLab to setup mirroring, the sqlinstance2 and sqlinstance3 is not started (this sure can be done very easily), another point is that you installed RTM version where database mirroring is disabled by default (sure this can be done by swithcing the trace flag, but the course is not about doing administrative tasks, right ? :-) )

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Thanks for your feedback. I have forwarded your feedback through the contact us link with the course. You can do so as well, if you follow the contact us link on the elearning site.|||

Hi,

I tried, but it told me that it couldn′t "process the URL", whatever that means :-)

-Jens

@@Version not updating

Greetings,
I recently installed Service Pack 4 on SQL 2000. The install went
smooth with no errors and a message at the end stating the install
completed successfully. I rebooted the server (Windows Server '03) and
tried to check the @.@.Version global variable but it still lists only
Service Pack 1.
Could it be that SP4 didn't install? Or is it more likely something
else is preventing the @.@.Version from updating?
Thanks in advance,
BenHi Ben
What do you get from
SELECT SERVERPROPERTY('ProductLevel')
HTH
Kalen Delaney, SQL Server MVP
"sullins602" <ben.sullins@.gmail.com> wrote in message
news:1152814872.081466.270730@.s13g2000cwa.googlegroups.com...
> Greetings,
> I recently installed Service Pack 4 on SQL 2000. The install went
> smooth with no errors and a message at the end stating the install
> completed successfully. I rebooted the server (Windows Server '03) and
> tried to check the @.@.Version global variable but it still lists only
> Service Pack 1.
> Could it be that SP4 didn't install? Or is it more likely something
> else is preventing the @.@.Version from updating?
> Thanks in advance,
> Ben
>|||Hi Ben,
Looks like @.@.version does not show the SQL Server service pack number but a
version number. Check for a number like 8.00.2039. Probably the service pack
listed is for the operating system.
Hope this helps,
Ben Nevarez, MCDBA, OCP
Database Administrator
"sullins602" wrote:

> Greetings,
> I recently installed Service Pack 4 on SQL 2000. The install went
> smooth with no errors and a message at the end stating the install
> completed successfully. I rebooted the server (Windows Server '03) and
> tried to check the @.@.Version global variable but it still lists only
> Service Pack 1.
> Could it be that SP4 didn't install? Or is it more likely something
> else is preventing the @.@.Version from updating?
> Thanks in advance,
> Ben
>|||Thats it! I was looking at the service pack for the OS not the
database. Thanks for your help fellas...
-ben

@@Version not updating

Greetings,
I recently installed Service Pack 4 on SQL 2000. The install went
smooth with no errors and a message at the end stating the install
completed successfully. I rebooted the server (Windows Server '03) and
tried to check the @.@.Version global variable but it still lists only
Service Pack 1.
Could it be that SP4 didn't install? Or is it more likely something
else is preventing the @.@.Version from updating?
Thanks in advance,
BenHi Ben
What do you get from
SELECT SERVERPROPERTY('ProductLevel')
--
HTH
Kalen Delaney, SQL Server MVP
"sullins602" <ben.sullins@.gmail.com> wrote in message
news:1152814872.081466.270730@.s13g2000cwa.googlegroups.com...
> Greetings,
> I recently installed Service Pack 4 on SQL 2000. The install went
> smooth with no errors and a message at the end stating the install
> completed successfully. I rebooted the server (Windows Server '03) and
> tried to check the @.@.Version global variable but it still lists only
> Service Pack 1.
> Could it be that SP4 didn't install? Or is it more likely something
> else is preventing the @.@.Version from updating?
> Thanks in advance,
> Ben
>|||Hi Ben,
Looks like @.@.version does not show the SQL Server service pack number but a
version number. Check for a number like 8.00.2039. Probably the service pack
listed is for the operating system.
Hope this helps,
Ben Nevarez, MCDBA, OCP
Database Administrator
"sullins602" wrote:
> Greetings,
> I recently installed Service Pack 4 on SQL 2000. The install went
> smooth with no errors and a message at the end stating the install
> completed successfully. I rebooted the server (Windows Server '03) and
> tried to check the @.@.Version global variable but it still lists only
> Service Pack 1.
> Could it be that SP4 didn't install? Or is it more likely something
> else is preventing the @.@.Version from updating?
> Thanks in advance,
> Ben
>|||Thats it! I was looking at the service pack for the OS not the
database. Thanks for your help fellas...
-ben