Problem running SSIS from C# executable when kicked off by another executable.

If I kick off my C# executable from the server everything works fine but if I have another C# executable kick off the C# executable that runs the SSIS I get an error message saying it cannot run SSIS package. I am thinking it sounds like a permissions problem but not sure. Any suggestions/guidance would be greatly appreciated.

Errors I am getting.

2007-09-26 15:02:30,187 [1] ERROR reporting.Processor [(null)] - Problem with Direct Script

2007-09-26 15:02:30,843 [1] ERROR reporting.Processor [(null)] - {Microsoft.SqlServer.Dts.Runtime.DtsError, Microsoft.SqlServer.Dts.Runtime.DtsError, Microsoft.SqlServer.Dts.Runtime.DtsError, Microsoft.SqlServer.Dts.Runtime.DtsError, Microsoft.SqlServer.Dts.Runtime.DtsError}

Thanks in advance.It appears to hqve a different ID running the executable when kicked off from the first executable which is kicked off from JCL. When I run the Exe it has my id and runs fine. What is a better approach to fixing this, changing the roles on the SSIS scripts or adding the id to SQL Server? Assuming this is the problem.|||You might have to better show the whole picture. Where packages are stored, how many packages, what your "C# executables" do, and then you mention JCL, a mainframe concept. Seems like quite a few pieces here.

Do you have package logging turned on?|||

Can you add a message box in your app to display the current credentials? I'd guess that your user credentials aren't being passed from the first app to the second.

Problem running SSIS from C#

have one script that works fine. I am doing the exact same thging with this new script and it runs fine from C# on my desktop and runs fine from SS on the server but comes back with a failure when trying to run from C# on the server. Is there any additional info I can retrieve about the problem? All I am getting right now is "Failure" from the result field.

if (result == DTSExecResult.Failure)

{

Console.WriteLine("Task failed or abended");

log.Error("Problem with DTS Script");

log.Error(result);

}

else

I would first try looking at the error info in Package.Errors, especially the error description stored in each error object in the collection.|||package.errors did not really give me any useful information. Is there anything else I can look at or canm anybody think of any reason why the SSIS would not work from a C# program but works everyplace else? I have others that work and cannot find any difference between the two.|||If you have other packages that work from your C# program, then it's possible something in that particular package is causing a problem (e.g. missing dependency for a task). I would try to narrow this down by reducing that package is something simpler that works (e.g. by disabling or removing tasks), then start adding back functionality until you get an error.|||

Ted Lee - MSFT wrote:

If you have other packages that work from your C# program, then it's possible something in that particular package is causing a problem (e.g. missing dependency for a task). I would try to narrow this down by reducing that package is something simpler that works (e.g. by disabling or removing tasks), then start adding back functionality until you get an error.

Package runs from the C# on my desktop and runs from SQL Server from the server. It is just after moving the EXE to the server and running it on the server that the SSIS will come back as a "Failure" and bomb.

|||What is the actual error message reported from the package?sql

Problem running Proc from Job

I have a stored procedure that runs fine using the Query Analyzer:

exec sp_ProcessRecords

However, when I create a job to run the stored proc once an hour, the job fails, with the following message:

Executed as user: sa. String or binary data would be truncated. [SQLSTATE 22001] (Error 8152) The statement has been terminated. [SQLSTATE 01000] (Error 3621). The step failed.

I don't think it's a permission problem, since the job runs as sa.

I don't understand why it would work if I run it manually, but not when it runs as a job.

Any help would be greatly appreciated.Check your parameters that are being passed to the stored procedure. This means that some parameter that is being passed it too long for the datatype and will be truncated.|||Originally posted by rnealejr
Check your parameters that are being passed to the stored procedure. This means that some parameter that is being passed it too long for the datatype and will be truncated.

Unfortunately, the stored proc called from the job does not take any parameters.

The odd thing is that the stored proc will work fine if it is run manually from the Query Analyzer. The error only occurs when the proc is run from the job, using the exact syntax!

I'm at a loss...|||Can you post the stored proc code - or describe what it is doing ? If you are doing inserts/updates then the same problem can occur.sql

Problem running full text search - it's broken!

I have a 2-tier application
The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
This works fine for ALL database calls, except when it requires a full text
query. The error message received is:
Microsoft OLE DB Provider for SQL Server error '80040e14'
Execution of a full-text operation failed. The catalog does not exist or is
currently unavailable. Please retry the action again later and if this
symptom persists, contact the system administrator.
However...I know that the full text catalogue DOES exist on the data tier
(I've rebuilt & repopulated it).
I also have an "identical" pair of machines and it works fine on that
one... By identical, I mean all the ASP code running under IIS is the
same.
No idea what I should be checking. The ADODB connection is identical on
both machines (uses a SQL Server account with identical access permissions)
and SQLServer is running under the ADMINISTRATOR account on both servers.
Thanks
Griff
Are there any pertinent messages from MSSearch or MSSCI in the event log?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Griff" <Howling@.The.Moon> wrote in message
news:e9f62cw3FHA.3628@.TK2MSFTNGP12.phx.gbl...
> I have a 2-tier application
> The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
> This works fine for ALL database calls, except when it requires a full
text
> query. The error message received is:
> --
> Microsoft OLE DB Provider for SQL Server error '80040e14'
> Execution of a full-text operation failed. The catalog does not exist or
is
> currently unavailable. Please retry the action again later and if this
> symptom persists, contact the system administrator.
> --
> However...I know that the full text catalogue DOES exist on the data tier
> (I've rebuilt & repopulated it).
> I also have an "identical" pair of machines and it works fine on that
> one... By identical, I mean all the ASP code running under IIS is the
> same.
> No idea what I should be checking. The ADODB connection is identical on
> both machines (uses a SQL Server account with identical access
permissions)
> and SQLServer is running under the ADMINISTRATOR account on both servers.
> Thanks
> Griff
>
>
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Are there any pertinent messages from MSSearch or MSSCI in the event log?
Hi Hilary
I'm afraid not. The only messages state that the catalogues were built
successfully, e.g.:
Master merge has completed on
d:\mssql\ftdata\sql0000700005\build\indexer\cifile s.
The only warning mentioned is:
SuperSocket info: (SpnRegister) : Error 1355.
Griff
|||Griff,
I think we need additional information from the server to understand why
this error OLE DB '80040e14' is being raised and that you have confirmed
that the full text catalogue DOES exist on this server. Could you set trace
flag 7300 on, you can get extended OLEDB error info?
dbcc traceon (3604, 7300)
Could you also post the exact CONTAINS* or FREETEXT* query that you're using
along with the search word or phrase, and re-run the query and post the
extended OLEDB error info?
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Griff" <Howling@.The.Moon> wrote in message
news:uUpfG%2343FHA.3628@.TK2MSFTNGP12.phx.gbl...
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Hi Hilary
> I'm afraid not. The only messages state that the catalogues were built
> successfully, e.g.:
> Master merge has completed on
> d:\mssql\ftdata\sql0000700005\build\indexer\cifile s.
> The only warning mentioned is:
> SuperSocket info: (SpnRegister) : Error 1355.
> Griff
>
sql

Problem running full text search - it's broken!

I have a 2-tier application
The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
This works fine for ALL database calls, except when it requires a full text
query. The error message received is:
--
Microsoft OLE DB Provider for SQL Server error '80040e14'
Execution of a full-text operation failed. The catalog does not exist or is
currently unavailable. Please retry the action again later and if this
symptom persists, contact the system administrator.
--
However...I know that the full text catalogue DOES exist on the data tier
(I've rebuilt & repopulated it).
I also have an "identical" pair of machines and it works fine on that
one... By identical, I mean all the ASP code running under IIS is the
same.
No idea what I should be checking. The ADODB connection is identical on
both machines (uses a SQL Server account with identical access permissions)
and SQLServer is running under the ADMINISTRATOR account on both servers.
Thanks
GriffAre there any pertinent messages from MSSearch or MSSCI in the event log?
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Griff" <Howling@.The.Moon> wrote in message
news:e9f62cw3FHA.3628@.TK2MSFTNGP12.phx.gbl...
> I have a 2-tier application
> The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
> This works fine for ALL database calls, except when it requires a full
text
> query. The error message received is:
> --
> Microsoft OLE DB Provider for SQL Server error '80040e14'
> Execution of a full-text operation failed. The catalog does not exist or
is
> currently unavailable. Please retry the action again later and if this
> symptom persists, contact the system administrator.
> --
> However...I know that the full text catalogue DOES exist on the data tier
> (I've rebuilt & repopulated it).
> I also have an "identical" pair of machines and it works fine on that
> one... By identical, I mean all the ASP code running under IIS is the
> same.
> No idea what I should be checking. The ADODB connection is identical on
> both machines (uses a SQL Server account with identical access
permissions)
> and SQLServer is running under the ADMINISTRATOR account on both servers.
> Thanks
> Griff
>
>|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Are there any pertinent messages from MSSearch or MSSCI in the event log?
Hi Hilary
I'm afraid not. The only messages state that the catalogues were built
successfully, e.g.:
Master merge has completed on
d:\mssql\ftdata\sql0000700005\build\indexer\cifiles.
The only warning mentioned is:
SuperSocket info: (SpnRegister) : Error 1355.
Griff|||Griff,
I think we need additional information from the server to understand why
this error OLE DB '80040e14' is being raised and that you have confirmed
that the full text catalogue DOES exist on this server. Could you set trace
flag 7300 on, you can get extended OLEDB error info?
dbcc traceon (3604, 7300)
Could you also post the exact CONTAINS* or FREETEXT* query that you're using
along with the search word or phrase, and re-run the query and post the
extended OLEDB error info?
Thanks,
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Griff" <Howling@.The.Moon> wrote in message
news:uUpfG%2343FHA.3628@.TK2MSFTNGP12.phx.gbl...
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
>> Are there any pertinent messages from MSSearch or MSSCI in the event log?
> Hi Hilary
> I'm afraid not. The only messages state that the catalogues were built
> successfully, e.g.:
> Master merge has completed on
> d:\mssql\ftdata\sql0000700005\build\indexer\cifiles.
> The only warning mentioned is:
> SuperSocket info: (SpnRegister) : Error 1355.
> Griff
>

Problem running full text search - it's broken!

I have a 2-tier application
The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
This works fine for ALL database calls, except when it requires a full text
query. The error message received is:
Microsoft OLE DB Provider for SQL Server error '80040e14'
Execution of a full-text operation failed. The catalog does not exist or is
currently unavailable. Please retry the action again later and if this
symptom persists, contact the system administrator.
However...I know that the full text catalogue DOES exist on the data tier
(I've rebuilt & repopulated it).
I also have an "identical" pair of machines and it works fine on that
one... By identical, I mean all the ASP code running under IIS is the
same.
No idea what I should be checking. The ADODB connection is identical on
both machines (uses a SQL Server account with identical access permissions)
and SQLServer is running under the ADMINISTRATOR account on both servers.
Thanks
Griff
Are there any pertinent messages from MSSearch or MSSCI in the event log?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Griff" <Howling@.The.Moon> wrote in message
news:e9f62cw3FHA.3628@.TK2MSFTNGP12.phx.gbl...
> I have a 2-tier application
> The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
> This works fine for ALL database calls, except when it requires a full
text
> query. The error message received is:
> --
> Microsoft OLE DB Provider for SQL Server error '80040e14'
> Execution of a full-text operation failed. The catalog does not exist or
is
> currently unavailable. Please retry the action again later and if this
> symptom persists, contact the system administrator.
> --
> However...I know that the full text catalogue DOES exist on the data tier
> (I've rebuilt & repopulated it).
> I also have an "identical" pair of machines and it works fine on that
> one... By identical, I mean all the ASP code running under IIS is the
> same.
> No idea what I should be checking. The ADODB connection is identical on
> both machines (uses a SQL Server account with identical access
permissions)
> and SQLServer is running under the ADMINISTRATOR account on both servers.
> Thanks
> Griff
>
>
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Are there any pertinent messages from MSSearch or MSSCI in the event log?
Hi Hilary
I'm afraid not. The only messages state that the catalogues were built
successfully, e.g.:
Master merge has completed on
d:\mssql\ftdata\sql0000700005\build\indexer\cifile s.
The only warning mentioned is:
SuperSocket info: (SpnRegister) : Error 1355.
Griff
|||Griff,
I think we need additional information from the server to understand why
this error OLE DB '80040e14' is being raised and that you have confirmed
that the full text catalogue DOES exist on this server. Could you set trace
flag 7300 on, you can get extended OLEDB error info?
dbcc traceon (3604, 7300)
Could you also post the exact CONTAINS* or FREETEXT* query that you're using
along with the search word or phrase, and re-run the query and post the
extended OLEDB error info?
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Griff" <Howling@.The.Moon> wrote in message
news:uUpfG%2343FHA.3628@.TK2MSFTNGP12.phx.gbl...
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Hi Hilary
> I'm afraid not. The only messages state that the catalogues were built
> successfully, e.g.:
> Master merge has completed on
> d:\mssql\ftdata\sql0000700005\build\indexer\cifile s.
> The only warning mentioned is:
> SuperSocket info: (SpnRegister) : Error 1355.
> Griff
>

Problem running full text search - it's broken!

I have a 2-tier application
The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
This works fine for ALL database calls, except when it requires a full text
query. The error message received is:
--
Microsoft OLE DB Provider for SQL Server error '80040e14'
Execution of a full-text operation failed. The catalog does not exist or is
currently unavailable. Please retry the action again later and if this
symptom persists, contact the system administrator.
However...I know that the full text catalogue DOES exist on the data tier
(I've rebuilt & repopulated it).
I also have an "identical" pair of machines and it works fine on that
one... By identical, I mean all the ASP code running under IIS is the
same.
No idea what I should be checking. The ADODB connection is identical on
both machines (uses a SQL Server account with identical access permissions)
and SQLServer is running under the ADMINISTRATOR account on both servers.
Thanks
GriffAre there any pertinent messages from MSSearch or MSSCI in the event log?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Griff" <Howling@.The.Moon> wrote in message
news:e9f62cw3FHA.3628@.TK2MSFTNGP12.phx.gbl...
> I have a 2-tier application
> The top tier is a web tier (IIS/ASP) and the lower tier runs SQLServer.
> This works fine for ALL database calls, except when it requires a full
text
> query. The error message received is:
> --
> Microsoft OLE DB Provider for SQL Server error '80040e14'
> Execution of a full-text operation failed. The catalog does not exist or
is
> currently unavailable. Please retry the action again later and if this
> symptom persists, contact the system administrator.
> --
> However...I know that the full text catalogue DOES exist on the data tier
> (I've rebuilt & repopulated it).
> I also have an "identical" pair of machines and it works fine on that
> one... By identical, I mean all the ASP code running under IIS is the
> same.
> No idea what I should be checking. The ADODB connection is identical on
> both machines (uses a SQL Server account with identical access
permissions)
> and SQLServer is running under the ADMINISTRATOR account on both servers.
> Thanks
> Griff
>
>|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Are there any pertinent messages from MSSearch or MSSCI in the event log?
Hi Hilary
I'm afraid not. The only messages state that the catalogues were built
successfully, e.g.:
Master merge has completed on
d:\mssql\ftdata\sql0000700005\build\inde
xer\cifiles.
The only warning mentioned is:
SuperSocket info: (SpnRegister) : Error 1355.
Griff|||Griff,
I think we need additional information from the server to understand why
this error OLE DB '80040e14' is being raised and that you have confirmed
that the full text catalogue DOES exist on this server. Could you set trace
flag 7300 on, you can get extended OLEDB error info?
dbcc traceon (3604, 7300)
Could you also post the exact CONTAINS* or FREETEXT* query that you're using
along with the search word or phrase, and re-run the query and post the
extended OLEDB error info?
Thanks,
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Griff" <Howling@.The.Moon> wrote in message
news:uUpfG%2343FHA.3628@.TK2MSFTNGP12.phx.gbl...
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ul3Lixw3FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Hi Hilary
> I'm afraid not. The only messages state that the catalogues were built
> successfully, e.g.:
> Master merge has completed on
> d:\mssql\ftdata\sql0000700005\build\inde
xer\cifiles.
> The only warning mentioned is:
> SuperSocket info: (SpnRegister) : Error 1355.
> Griff
>

Problem running a SQL job

I have a SQL job that runs as part of a nightly load of data tables. Part
of the job is a DTS job (loading a table from a text file), and other parts
of it are either sql code, or calling of a stored procedure.
We have 2 production servers, both (I thought) set up identically. SQL
2000, most recent service packs.
However, 2 times in the last several weeks, (3 times overall) we've gotten
this error in the same spot:
"A floating point exception occurred in the user process. Current
transaction is canceled. [SQLSTATE 42000] (Error 3628). The step failed
."
We went back & checked the source table for it, and saw no problems.
We took the same job (a collection of about 10 stored procedure calls) that
looked like this:
sp_build_table_1
go
sp_build_table_2
go
sp_build_table_3
go
and so on...
and pulled it into query analyzer.
When run in Query Analyzer from a desktop (not the server), the jobs run
fine - no floating point exceptions or anything.
Any ideas as to what the problem might be? Not sure if it is a dts problem,
a programming problem or just a server setup issue.
Thanks,
SCSC,
There are several reasons that this might manifest itself that have nothing
to do with the data and everything to do with the complexity of a query.
You might check out these KB articles and see if they help.
http://support.microsoft.com/defaul...kb;en-us;818899
http://support.microsoft.com/defaul...kb;en-us;829444
http://support.microsoft.com/defaul...kb;en-us;812995
http://support.microsoft.com/defaul...kb;en-us;816503
Russell Fields
"Goober" <me@.privacy.net> wrote in message
news:uVnH2pFhEHA.3536@.TK2MSFTNGP12.phx.gbl...
> I have a SQL job that runs as part of a nightly load of data tables. Part
> of the job is a DTS job (loading a table from a text file), and other
parts
> of it are either sql code, or calling of a stored procedure.
> We have 2 production servers, both (I thought) set up identically. SQL
> 2000, most recent service packs.
> However, 2 times in the last several weeks, (3 times overall) we've gotten
> this error in the same spot:
> "A floating point exception occurred in the user process. Current
> transaction is canceled. [SQLSTATE 42000] (Error 3628). The step fail
ed."
> We went back & checked the source table for it, and saw no problems.
> We took the same job (a collection of about 10 stored procedure calls)
that
> looked like this:
> sp_build_table_1
> go
> sp_build_table_2
> go
> sp_build_table_3
> go
> and so on...
> and pulled it into query analyzer.
> When run in Query Analyzer from a desktop (not the server), the jobs run
> fine - no floating point exceptions or anything.
> Any ideas as to what the problem might be? Not sure if it is a dts
problem,
> a programming problem or just a server setup issue.
> Thanks,
> SC
>sql

Problem running a SQL job

I have a SQL job that runs as part of a nightly load of data tables. Part
of the job is a DTS job (loading a table from a text file), and other parts
of it are either sql code, or calling of a stored procedure.
We have 2 production servers, both (I thought) set up identically. SQL
2000, most recent service packs.
However, 2 times in the last several weeks, (3 times overall) we've gotten
this error in the same spot:
"A floating point exception occurred in the user process. Current
transaction is canceled. [SQLSTATE 42000] (Error 3628). The step failed."
We went back & checked the source table for it, and saw no problems.
We took the same job (a collection of about 10 stored procedure calls) that
looked like this:
sp_build_table_1
go
sp_build_table_2
go
sp_build_table_3
go
and so on...
and pulled it into query analyzer.
When run in Query Analyzer from a desktop (not the server), the jobs run
fine - no floating point exceptions or anything.
Any ideas as to what the problem might be? Not sure if it is a dts problem,
a programming problem or just a server setup issue.
Thanks,
SC
SC,
There are several reasons that this might manifest itself that have nothing
to do with the data and everything to do with the complexity of a query.
You might check out these KB articles and see if they help.
http://support.microsoft.com/default...b;en-us;818899
http://support.microsoft.com/default...b;en-us;829444
http://support.microsoft.com/default...b;en-us;812995
http://support.microsoft.com/default...b;en-us;816503
Russell Fields
"Goober" <me@.privacy.net> wrote in message
news:uVnH2pFhEHA.3536@.TK2MSFTNGP12.phx.gbl...
> I have a SQL job that runs as part of a nightly load of data tables. Part
> of the job is a DTS job (loading a table from a text file), and other
parts
> of it are either sql code, or calling of a stored procedure.
> We have 2 production servers, both (I thought) set up identically. SQL
> 2000, most recent service packs.
> However, 2 times in the last several weeks, (3 times overall) we've gotten
> this error in the same spot:
> "A floating point exception occurred in the user process. Current
> transaction is canceled. [SQLSTATE 42000] (Error 3628). The step failed."
> We went back & checked the source table for it, and saw no problems.
> We took the same job (a collection of about 10 stored procedure calls)
that
> looked like this:
> sp_build_table_1
> go
> sp_build_table_2
> go
> sp_build_table_3
> go
> and so on...
> and pulled it into query analyzer.
> When run in Query Analyzer from a desktop (not the server), the jobs run
> fine - no floating point exceptions or anything.
> Any ideas as to what the problem might be? Not sure if it is a dts
problem,
> a programming problem or just a server setup issue.
> Thanks,
> SC
>

Problem running a SQL job

I have a SQL job that runs as part of a nightly load of data tables. Part
of the job is a DTS job (loading a table from a text file), and other parts
of it are either sql code, or calling of a stored procedure.
We have 2 production servers, both (I thought) set up identically. SQL
2000, most recent service packs.
However, 2 times in the last several weeks, (3 times overall) we've gotten
this error in the same spot:
"A floating point exception occurred in the user process. Current
transaction is canceled. [SQLSTATE 42000] (Error 3628). The step failed."
We went back & checked the source table for it, and saw no problems.
We took the same job (a collection of about 10 stored procedure calls) that
looked like this:
sp_build_table_1
go
sp_build_table_2
go
sp_build_table_3
go
and so on...
and pulled it into query analyzer.
When run in Query Analyzer from a desktop (not the server), the jobs run
fine - no floating point exceptions or anything.
Any ideas as to what the problem might be? Not sure if it is a dts problem,
a programming problem or just a server setup issue.
Thanks,
SCSC,
There are several reasons that this might manifest itself that have nothing
to do with the data and everything to do with the complexity of a query.
You might check out these KB articles and see if they help.
http://support.microsoft.com/default.aspx?scid=kb;en-us;818899
http://support.microsoft.com/default.aspx?scid=kb;en-us;829444
http://support.microsoft.com/default.aspx?scid=kb;en-us;812995
http://support.microsoft.com/default.aspx?scid=kb;en-us;816503
Russell Fields
"Goober" <me@.privacy.net> wrote in message
news:uVnH2pFhEHA.3536@.TK2MSFTNGP12.phx.gbl...
> I have a SQL job that runs as part of a nightly load of data tables. Part
> of the job is a DTS job (loading a table from a text file), and other
parts
> of it are either sql code, or calling of a stored procedure.
> We have 2 production servers, both (I thought) set up identically. SQL
> 2000, most recent service packs.
> However, 2 times in the last several weeks, (3 times overall) we've gotten
> this error in the same spot:
> "A floating point exception occurred in the user process. Current
> transaction is canceled. [SQLSTATE 42000] (Error 3628). The step failed."
> We went back & checked the source table for it, and saw no problems.
> We took the same job (a collection of about 10 stored procedure calls)
that
> looked like this:
> sp_build_table_1
> go
> sp_build_table_2
> go
> sp_build_table_3
> go
> and so on...
> and pulled it into query analyzer.
> When run in Query Analyzer from a desktop (not the server), the jobs run
> fine - no floating point exceptions or anything.
> Any ideas as to what the problem might be? Not sure if it is a dts
problem,
> a programming problem or just a server setup issue.
> Thanks,
> SC
>

problem installing sp4 on msde 2000 release A

Hello,
When I try to run the setup with the parameters I need (I have a default
instance installed already) to upgrade MSDE 2000 the setup program runs with
a blue screen on background and a modal window appears showing me the
parameters (like /i /p /v etc.). It seems to me that the setup is somehow
messed (I wonder if has something to do with the Windows Installer). Can
anyone help?
Thanks!
hi Leonardo,
Leonardo wrote:
> Hello,
> When I try to run the setup with the parameters I need (I have a
> default instance installed already) to upgrade MSDE 2000 the setup
> program runs with a blue screen on background and a modal window
> appears showing me the parameters (like /i /p /v etc.). It seems to
> me that the setup is somehow messed (I wonder if has something to do
> with the Windows Installer). Can anyone help?
have you tried re-downloading the sp4 package? perhaps it' corrupted..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply