Error when using SSL encryption for SQL server 2000

Hi,
I am having trouble connecting to SQL server 2000 using SSL.
My environment is as follows:
1. Microsoft Certificate server running on a Windows 2000 server machine.
2. SQL Server 2000 running on a Win NT machine with SP6 installed. SQL
Server service pack 3a has been installed.
3. Client machine running Windows XP with SQL Server service pack 3a
installed.
We use a type 4 JDBC secure driver to connect to SQL server from our Java ap
plication running on the client machine.
We also setup the certificate as described in the article 276553 - HOW TO: E
nable SSL Encryption for SQL Server 2000 with Certificate Server.
The installation of the certificate was successful. However, when I tried to
connect to the SQL server using SQL Query Analyzer, I received the followin
g error message.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Encryption not supported on SQL Serv
er
Thanks,
Chacko.Usually, you receive that error if you enable SSL from the client and the
server doesn't have the certificate.
But, the bad news is you won't be able to use SSL with a type 4 Java driver.
The implementation of protocol encryption requires the driver to access
SSL. In
particular protocol encryption uses SSL APIs implemented in NT. Type 4 JDBC
drivers have a problem in that they are not allowed to directly call system
dlls. There is no library in Java 1.4 or below that emulates the protocol
encryption behavior of SSL from Windows NT.
If your JDBC application requires protocol encryption to SQL 2000,
you will have to use alternate method of encryption such as IPSEC or use a
suitable SSL enabled Type 3 JDBC Driver.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
Thanks for your response.
We did generate and install the certificate using the web browser and not us
ing MMC since it is a Win NT 4.0 box. When we look at the certificate on the
database server machine via the IE properties applet, the certificate shows
up fine as described in th
e Microsoft setup document. So, I am not sure where I am going wrong. Is the
re any way to trouble shoot this issue?
Also, we are not even trying the connectivity with the type 4 JDBC driver ye
t even though that is what we want to do ultimately. However, right now we a
re using Query Analyzer on the client machine to test the communication. We
get the error when we try a
nd login to the database via Query Analyzer.
About the type 4 JDBC driver, the documentation from i-net OPTA type 4 JDBC driver says
that it supports SSL for SQL Server 2000. Am I misunderstanding something here? You ca
n find information about i-net OPTA at [url]http://www.inetsoftware.de/English/Produkt[
/url]
e/OPTA/default.htm
Your thoughts are greatly appreciated.
Thanks Kevin.
Chacko.

Error when using rskeymgmt to backup encryption key

When I run the rskeymgmt program to backup the encryption key, I get the
following error:
The Report Server Windows service is not responding to RPC requests. The
service may not be running.
I have checked, and the service is running. We are using SQL Server 2005
sp2. The command I am using is:
rskeymgmt -e -fc:\rskey\rsdbkey.txt -psomepassword
Any ideas why this is failing. I was able to run the program some time ago.
Thanks.On May 2, 11:50 am, "Tim Kelley" <tkel...@.company.com> wrote:
> When I run the rskeymgmt program to backup the encryption key, I get the
> following error:
> The Report Server Windows service is not responding to RPC requests. The
> service may not be running.
> I have checked, and the service is running. We are using SQL Server 2005
> sp2. The command I am using is:
> rskeymgmt -e -fc:\rskey\rsdbkey.txt -psomepassword
> Any ideas why this is failing. I was able to run the program some time ago.
> Thanks.
This link might be helpful:
http://www.technologyone.org/new-6210113-3731.html
Regards,
Enrique Martinez
Sr. Software Consultant

Error when trying to modify a table in Sql Server 2005 beta 2

Hi there.
All the times when I try to modify a table, I receive a COM error and the
modify windows is not showed. Below you can see the exception message. That
way, I am unable to modify a table using Sql Server 2005 beta 2. Any
suggestions?
************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT
E_FAIL has been returned from a call to a COM component.
at
Microsoft.VisualStudio.DataTools.UI.Grid.IDTGridSt orage.GetCellDataAsString(Int64 nRowIndex, Int32 nColIndex)
at
Microsoft.VisualStudio.DataTools.UI.Grid.DTGridSto rageWrapper.GetCellDataAsString(Int64 nRowIndex, Int32 nColIndex)
at
Microsoft.SqlServer.Management.UI.Grid.GridTextCol umn.DrawCell(Graphics g,
Brush bkBrush, Brush textBrush, Font textFont, Rectangle rect, IGridStorage
storage, Int64 nRowIndex)
at
Microsoft.SqlServer.Management.UI.Grid.GridControl .DoCellPainting(Graphics g,
SolidBrush bkBrush, SolidBrush textBrush, Font textFont, Rectangle cellRect,
GridColumn gridColumn, Int64 rowNumber, Boolean enabledState)
at
Microsoft.SqlServer.Management.UI.Grid.GridControl .PaintOneCell(Graphics g,
Int32 nCol, Int64 nRow, Int32 nEditedCol, Int64 nEditedRow, Rectangle& rCell,
Rectangle& rCurrentCellRect, Rectangle& rEditingCellRect)
at Microsoft.SqlServer.Management.UI.Grid.GridControl .PaintGrid(Graphics g)
at
Microsoft.SqlServer.Management.UI.Grid.GridControl .OnPaint(PaintEventArgs pe)
at System.Windows.Forms.Control.PaintWithErrorHandlin g(PaintEventArgs e,
Int16 layer, Boolean disposeEventArgs)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at Microsoft.SqlServer.Management.UI.Grid.GridControl .WndProc(Message& m)
at Microsoft.VisualStudio.DataTools.UI.Grid.GridContr ol.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage (Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(M essage& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)
Thanks.
Carlos
Senior Developer
www.byteshift.com
Regarding SQL Server 2005, you should probably post to the beta newsgroups
http://communities.microsoft.com/new...r2005&slcid=us
If you want to access the newsgroups via your newsreader just scroll through
the top right hand frame for connection information
Keith
"Carlao" <Carlao@.discussions.microsoft.com> wrote in message
news:0646E034-A0F4-4692-9B3A-48A790A48FAC@.microsoft.com...
> Hi there.
> All the times when I try to modify a table, I receive a COM error and the
> modify windows is not showed. Below you can see the exception message.
That
> way, I am unable to modify a table using Sql Server 2005 beta 2. Any
> suggestions?
> ************** Exception Text **************
> System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT
> E_FAIL has been returned from a call to a COM component.
> at
>
Microsoft.VisualStudio.DataTools.UI.Grid.IDTGridSt orage.GetCellDataAsString(
Int64 nRowIndex, Int32 nColIndex)
> at
>
Microsoft.VisualStudio.DataTools.UI.Grid.DTGridSto rageWrapper.GetCellDataAsS
tring(Int64 nRowIndex, Int32 nColIndex)
> at
> Microsoft.SqlServer.Management.UI.Grid.GridTextCol umn.DrawCell(Graphics g,
> Brush bkBrush, Brush textBrush, Font textFont, Rectangle rect,
IGridStorage
> storage, Int64 nRowIndex)
> at
> Microsoft.SqlServer.Management.UI.Grid.GridControl .DoCellPainting(Graphics
g,
> SolidBrush bkBrush, SolidBrush textBrush, Font textFont, Rectangle
cellRect,
> GridColumn gridColumn, Int64 rowNumber, Boolean enabledState)
> at
> Microsoft.SqlServer.Management.UI.Grid.GridControl .PaintOneCell(Graphics
g,
> Int32 nCol, Int64 nRow, Int32 nEditedCol, Int64 nEditedRow, Rectangle&
rCell,
> Rectangle& rCurrentCellRect, Rectangle& rEditingCellRect)
> at
Microsoft.SqlServer.Management.UI.Grid.GridControl .PaintGrid(Graphics g)
> at
> Microsoft.SqlServer.Management.UI.Grid.GridControl .OnPaint(PaintEventArgs
pe)
> at System.Windows.Forms.Control.PaintWithErrorHandlin g(PaintEventArgs
e,
> Int16 layer, Boolean disposeEventArgs)
> at System.Windows.Forms.Control.WmPaint(Message& m)
> at System.Windows.Forms.Control.WndProc(Message& m)
> at Microsoft.SqlServer.Management.UI.Grid.GridControl .WndProc(Message&
m)
> at
Microsoft.VisualStudio.DataTools.UI.Grid.GridContr ol.WndProc(Message& m)
> at System.Windows.Forms.ControlNativeWindow.OnMessage (Message& m)
> at System.Windows.Forms.ControlNativeWindow.WndProc(M essage& m)
> at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
> IntPtr wparam, IntPtr lparam)
> Thanks.
> Carlos
> --
> Senior Developer
> www.byteshift.com

Error when trying to log in to SQL server

I've just finished developing a web app, which works fine on my PC, running IIS locally. It uses windows authentication and a trusted connection to retrieve data from SQL server. So far so routine. When I deploy the app to my live server, it returns the error:

Login failed for user '\'

The stack trace seems to indicate that it's at the point where the app tries to retrieve data that the error occurs. I proved this by changing my connection string to explicitly define the log on, and it retrieved the data no problem.

I set up a very simple webform with a label on, to return what it thought the user's log on name was, and it returns the correct name.

Any ideas as to why the username isn't being correctly passed to SQL server?Have you made sure the Web Account is a valid user of the SQL Server? If the IIS box and the SQL box are different you have to ensure the user has network rights too.|||Yes, the user (me!) definitely has rights on the SQL server. How come it works locally on my PC, but not on the server?

What network rights do you think I should investigate?

Thanks.|||Sorry I mis-read your original post, I didn't notice that your site was using NT Authentication. So here is my mental checklist:
1. Web Server has access to the Domain server to authenticate the user
2. The Web Server isn't the Domain Server
3. SQL Server security logins knows about the Windows user/user group
4. The SQL Database knows about the Windows user/user group

I mentioned the network security because when you use anon web access the user must have network access to go across machines. That "shouldn't" be an issue here.

Also run SQL Profiler to see if the user is getting set to SQL and then going wrong. Sounds more like its a problem on the web server though, something wrong with the impersonation.|||I'm positive that the user is being authenticated properly on the app, because when I load a simple page with a label which displays the user name, it displays correctly. For some reason this user name isn't getting passed to SQL server correctly.

I tried deploying the application to the box which has the SQL server running, and gess what? It worked. So does this mean that the first box can't access the domain server? Any idea how I can check that?

I'll have a think, and let you know how I get on.

Cheers.|||Hang on, just cause you're using Web Authentication doesn't mean it will impersonate the user onto SQL Server. Do you set the principal security when the user connects?

Check out:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetch03.asp

Error when trying to execute a job from windows service.

Hi,
I'm trying to execute a DTS package from a .NET service. The service is
running under a domain account that owns the job which it executes using
'sp_start_job'. The call to the sp succeeds however checking the Job history
gives: -
"The job failed. Unable to determine if the owner (DOMAIN\ServiceUser) of
job <JobName> has server access (reason: Could not obtain information about
Windows NT group/user 'DOMAIN\ServiceUser'. [SQLSTATE 42000] (Error 8198
))."
SQL Server 2000 SP4
Both SQLServer + SQLAgent run under a domain account (different to the
service)
ServiceUser has login to sql server not an admin, however I've tried using
the SQL Agent Proxy account still no success.
Any ideas?
thanks Paul> SQL Server 2000 SP4
> Both SQLServer + SQLAgent run under a domain account (different to the
> service)
> ServiceUser has login to sql server not an admin, however I've tried using
> the SQL Agent Proxy account still no success.
The SQL 2000 Books Online <instsql.chm::/in_overview_6k1f.htm> states that
the SQL Agent service account must be a member of the local Administrators
group in order to "Create CmdExec and ActiveScript jobs belonging to someone
other than a SQL Server administrator".
Hope this helps.
Dan Guzman
SQL Server MVP
"Paul Coulson" <nospam@.nospam.net> wrote in message
news:OZUDQ3WOGHA.3144@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I'm trying to execute a DTS package from a .NET service. The service is
> running under a domain account that owns the job which it executes using
> 'sp_start_job'. The call to the sp succeeds however checking the Job
> history gives: -
> "The job failed. Unable to determine if the owner (DOMAIN\ServiceUser) of
> job <JobName> has server access (reason: Could not obtain information
> about Windows NT group/user 'DOMAIN\ServiceUser'. [SQLSTATE 42000] (Er
ror
> 8198))."
> SQL Server 2000 SP4
> Both SQLServer + SQLAgent run under a domain account (different to the
> service)
> ServiceUser has login to sql server not an admin, however I've tried using
> the SQL Agent Proxy account still no success.
> Any ideas?
> thanks Paul
>|||Hi Dan,
Thanks that's sorted it. Also got it working using the proxy account
again this needed local admin rights.
Cheers Paul
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:ueU6PriOGHA.1192@.TK2MSFTNGP11.phx.gbl...
> The SQL 2000 Books Online <instsql.chm::/in_overview_6k1f.htm> states that
> the SQL Agent service account must be a member of the local Administrators
> group in order to "Create CmdExec and ActiveScript jobs belonging to
> someone other than a SQL Server administrator".
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Paul Coulson" <nospam@.nospam.net> wrote in message
> news:OZUDQ3WOGHA.3144@.TK2MSFTNGP11.phx.gbl...
>|||I'm glad you were able to get it working. However, I'd be leery about
granting admin rights the proxy account since that allows non-sysadmins to
run processes with admin rights. Now that you got the service accounts
sorted out, I would expect your DTS package to run fine as long as the proxy
account has permissions on data and files accessed by the package.
Hope this helps.
Dan Guzman
SQL Server MVP
"Paul Coulson" <nospam@.nospam.net> wrote in message
news:eCdaOR4OGHA.812@.TK2MSFTNGP10.phx.gbl...
> Hi Dan,
> Thanks that's sorted it. Also got it working using the proxy account
> again this needed local admin rights.
> Cheers Paul
>
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:ueU6PriOGHA.1192@.TK2MSFTNGP11.phx.gbl...
>

Error when trying to deploy a report using Oracle data source

We use SQL Server Reporting Services, My SQL box is on Win2k3. The developer
is able to run the report on his Windows XP box but when he deploys the
reports to the SQL Server where Reporting Services is running, he gets the
following error:
"An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Cannot create a connection to data source 'WMS'. (rsErrorOpeningConnection)
Get Online Help
System.Data.OracleClient requires Oracle client software version 8.1.7 or
greater
He develped this report on his XP box using Visual Studio .NET and is trying
to deploy it to our SQL server production box where Reporting Services is
installed. I have installed Oracle 9.2 client on the SQL Server box and can
make successful connections to our Oracle Database (where the report is
pulling data from). What else am I missing?
Thanks!
Bea Isabelle, Database AdministratorI used the google groups search.
Look at this link:
http://groups-beta.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/8eb65eca58e11586/05b5299775c955b9?q=oracle+8.1.7+group:microsoft.public.sqlserver.reportingsvcs&rnum=1&hl=en#05b5299775c955b9
Basically reboot after installing. Link has other things to try.
Here is the search I used:
http://groups-beta.google.com/groups?hl=en&lr=&safe=off&num=10&q=oracle+8.1.7+group%3Amicrosoft.public.sqlserver.reportingsvcs&safe=off&qt_s=Search
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"isabelle" <isabelle@.discussions.microsoft.com> wrote in message
news:66AE92CA-13A2-4FB2-96B4-9CE0464D141E@.microsoft.com...
> We use SQL Server Reporting Services, My SQL box is on Win2k3. The
> developer
> is able to run the report on his Windows XP box but when he deploys the
> reports to the SQL Server where Reporting Services is running, he gets the
> following error:
> "An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Cannot create a connection to data source 'WMS'.
> (rsErrorOpeningConnection)
> Get Online Help
> System.Data.OracleClient requires Oracle client software version 8.1.7 or
> greater
> He develped this report on his XP box using Visual Studio .NET and is
> trying
> to deploy it to our SQL server production box where Reporting Services is
> installed. I have installed Oracle 9.2 client on the SQL Server box and
> can
> make successful connections to our Oracle Database (where the report is
> pulling data from). What else am I missing?
> Thanks!
> Bea Isabelle, Database Administrator
>|||Unfortunately, my server access won't allow me to go to those links here from
work. The only
that we haven't tried is rebooting the IIS services as the documentation
noted. I've also installed the ODP .Net
driver on the FFSQL box and he still gets the error. We will try a reboot
later today and see if that clears up the error.
Thanks!
"Bruce L-C [MVP]" wrote:
> I used the google groups search.
> Look at this link:
> http://groups-beta.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/8eb65eca58e11586/05b5299775c955b9?q=oracle+8.1.7+group:microsoft.public.sqlserver.reportingsvcs&rnum=1&hl=en#05b5299775c955b9
> Basically reboot after installing. Link has other things to try.
> Here is the search I used:
> http://groups-beta.google.com/groups?hl=en&lr=&safe=off&num=10&q=oracle+8.1.7+group%3Amicrosoft.public.sqlserver.reportingsvcs&safe=off&qt_s=Search
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "isabelle" <isabelle@.discussions.microsoft.com> wrote in message
> news:66AE92CA-13A2-4FB2-96B4-9CE0464D141E@.microsoft.com...
> > We use SQL Server Reporting Services, My SQL box is on Win2k3. The
> > developer
> > is able to run the report on his Windows XP box but when he deploys the
> > reports to the SQL Server where Reporting Services is running, he gets the
> > following error:
> >
> > "An error has occurred during report processing. (rsProcessingAborted) Get
> > Online Help
> > Cannot create a connection to data source 'WMS'.
> > (rsErrorOpeningConnection)
> > Get Online Help
> > System.Data.OracleClient requires Oracle client software version 8.1.7 or
> > greater
> >
> > He develped this report on his XP box using Visual Studio .NET and is
> > trying
> > to deploy it to our SQL server production box where Reporting Services is
> > installed. I have installed Oracle 9.2 client on the SQL Server box and
> > can
> > make successful connections to our Oracle Database (where the report is
> > pulling data from). What else am I missing?
> >
> > Thanks!
> >
> > Bea Isabelle, Database Administrator
> >
>
>

error when trying to delete record

Windows 2000 Server sp4, SQL Server 2000 sp3
I get the error below when attempting to delete a record from a table called
Monitor directly from Enterprise Manager GUI.
error:
[Microsoft][ODBC SQL Server Driver][SQL Server][Invalid Obje
ct Name]
'tsvw_KJDKFAJDFKJAKLFDJKLAJDFKJASKFDJKAJ
DF'
[Microsoft][ODBC SQL Server Driver][SQL Server][Invalid Obje
ct
Name]UserA.Monitor
[Microsoft][ODBC SQL Server Driver][SQL Server][Invalid Obje
ct Name]
'ctsv_DKFJDKJFKDJFKDKFJDKJFIEJIEJIEJFIEJ
FKJDKJ'
The KDJFKDJFKJDF above is obviously not exact. The actual error contains a
long string of random characters though.. If i'm not mistaken these are
system generated names for views related to replication.
1) could this be replication related?
2) Important note: UserA is NOT the current owner of the Monitor table!
UserA used to own the table but due to replication issues the owner was
changed to dbo a long time ago. ' Can I safely run the sp_changeobjectowner
procedure specifying dbo again or would I need to drop the merge replication
in order to do that?
3) I verified that the tsvw_ect... and the ctsv_ect... do not exist in the
database?
any suggestions about how to get to the bottom of this would be GREATLY
appreciated. Thanks.It seems you have some "invalid" merge triggers (probably from a previous
publication). Did you republish after changing your table owner name? If
you do have invalid triggers, you should consider dropping and recreating
your publication.
A. Drop the subscription
B. Drop the publication.
C. Delete the triggers that reference the non-existant views
D. Recreate the publication and subscription.
E. Run the snapshot.
reference:
How to manually remove a replication in SQL Server 2000 - ID: 324401
http://support.microsoft.com/?id=324401
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx|||Thank you! I did not completely drop and recreate the merge replication
setup but what you said is exactly what happened. I had an issue removing
repl before due to the owner of the tables not being dbo. I had to manually
clean out repl.. change table owners to dbo.. and recreate the replication.
It looks like one of the triggers from the older repl setup was still there.
I found the old trigger and deleted it. It was obvious it was old because it
referenced the old user name. There were the 3 correct triggers on the table
as well. One each for insert, update, and delete. So what was happening was
this: there was the old delete trigger on this table and it was listed first
so it executed and failed. The correct trigger never fired then. Now that
old trigger is gone and all works fine.
thanks again.
"Fany Vargas [MSFT]" <fanyv@.online.microsoft.com> wrote in message
news:Yj9qhVuzEHA.3388@.cpmsftngxa10.phx.gbl...
> It seems you have some "invalid" merge triggers (probably from a previous
> publication). Did you republish after changing your table owner name? If
> you do have invalid triggers, you should consider dropping and recreating
> your publication.
> A. Drop the subscription
> B. Drop the publication.
> C. Delete the triggers that reference the non-existant views
> D. Recreate the publication and subscription.
> E. Run the snapshot.
>
> reference:
> How to manually remove a replication in SQL Server 2000 - ID: 324401
> http://support.microsoft.com/?id=324401
> Fany Vargas
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
> Microsoft software to better protect against viruses and security
> vulnerabilities. The easiest way to do this is to visit the following
> websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>

error when trying to delete record

Windows 2000 Server sp4, SQL Server 2000 sp3
I get the error below when attempting to delete a record from a table called
Monitor directly from Enterprise Manager GUI.
error:
[Microsoft][ODBC SQL Server Driver][SQL Server][Invalid Object Name]
'tsvw_KJDKFAJDFKJAKLFDJKLAJDFKJASKFDJKAJDF'
[Microsoft][ODBC SQL Server Driver][SQL Server][Invalid Object
Name]UserA.Monitor
[Microsoft][ODBC SQL Server Driver][SQL Server][Invalid Object Name]
'ctsv_DKFJDKJFKDJFKDKFJDKJFIEJIEJIEJFIEJFKJDKJ'
The KDJFKDJFKJDF above is obviously not exact. The actual error contains a
long string of random characters though.. If i'm not mistaken these are
system generated names for views related to replication.
1) could this be replication related?
2) Important note: UserA is NOT the current owner of the Monitor table!
UserA used to own the table but due to replication issues the owner was
changed to dbo a long time ago. ? Can I safely run the sp_changeobjectowner
procedure specifying dbo again or would I need to drop the merge replication
in order to do that?
3) I verified that the tsvw_ect... and the ctsv_ect... do not exist in the
database?
any suggestions about how to get to the bottom of this would be GREATLY
appreciated. Thanks.
It seems you have some "invalid" merge triggers (probably from a previous
publication). Did you republish after changing your table owner name? If
you do have invalid triggers, you should consider dropping and recreating
your publication.
A. Drop the subscription
B. Drop the publication.
C. Delete the triggers that reference the non-existant views
D. Recreate the publication and subscription.
E. Run the snapshot.
reference:
How to manually remove a replication in SQL Server 2000 - ID: 324401
http://support.microsoft.com/?id=324401
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Thank you! I did not completely drop and recreate the merge replication
setup but what you said is exactly what happened. I had an issue removing
repl before due to the owner of the tables not being dbo. I had to manually
clean out repl.. change table owners to dbo.. and recreate the replication.
It looks like one of the triggers from the older repl setup was still there.
I found the old trigger and deleted it. It was obvious it was old because it
referenced the old user name. There were the 3 correct triggers on the table
as well. One each for insert, update, and delete. So what was happening was
this: there was the old delete trigger on this table and it was listed first
so it executed and failed. The correct trigger never fired then. Now that
old trigger is gone and all works fine.
thanks again.
"Fany Vargas [MSFT]" <fanyv@.online.microsoft.com> wrote in message
news:Yj9qhVuzEHA.3388@.cpmsftngxa10.phx.gbl...
> It seems you have some "invalid" merge triggers (probably from a previous
> publication). Did you republish after changing your table owner name? If
> you do have invalid triggers, you should consider dropping and recreating
> your publication.
> A. Drop the subscription
> B. Drop the publication.
> C. Delete the triggers that reference the non-existant views
> D. Recreate the publication and subscription.
> E. Run the snapshot.
>
> reference:
> How to manually remove a replication in SQL Server 2000 - ID: 324401
> http://support.microsoft.com/?id=324401
> Fany Vargas
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
> Microsoft software to better protect against viruses and security
> vulnerabilities. The easiest way to do this is to visit the following
> websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>

error when trying to delete record

Windows 2000 Server sp4, SQL Server 2000 sp3
I get the error below when attempting to delete a record from a table called
Monitor directly from Enterprise Manager GUI.
error:
[Microsoft][ODBC SQL Server Driver][SQL Server][Invalid Object Name]
'tsvw_KJDKFAJDFKJAKLFDJKLAJDFKJASKFDJKAJDF'
[Microsoft][ODBC SQL Server Driver][SQL Server][Invalid Object
Name]UserA.Monitor
[Microsoft][ODBC SQL Server Driver][SQL Server][Invalid Object Name]
'ctsv_DKFJDKJFKDJFKDKFJDKJFIEJIEJIEJFIEJFKJDKJ'
The KDJFKDJFKJDF above is obviously not exact. The actual error contains a
long string of random characters though.. If i'm not mistaken these are
system generated names for views related to replication.
1) could this be replication related?
2) Important note: UserA is NOT the current owner of the Monitor table!
UserA used to own the table but due to replication issues the owner was
changed to dbo a long time ago. ' Can I safely run the sp_changeobjectowner
procedure specifying dbo again or would I need to drop the merge replication
in order to do that?
3) I verified that the tsvw_ect... and the ctsv_ect... do not exist in the
database?
any suggestions about how to get to the bottom of this would be GREATLY
appreciated. Thanks.It seems you have some "invalid" merge triggers (probably from a previous
publication). Did you republish after changing your table owner name? If
you do have invalid triggers, you should consider dropping and recreating
your publication.
A. Drop the subscription
B. Drop the publication.
C. Delete the triggers that reference the non-existant views
D. Recreate the publication and subscription.
E. Run the snapshot.
reference:
How to manually remove a replication in SQL Server 2000 - ID: 324401
http://support.microsoft.com/?id=324401
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx|||Thank you! I did not completely drop and recreate the merge replication
setup but what you said is exactly what happened. I had an issue removing
repl before due to the owner of the tables not being dbo. I had to manually
clean out repl.. change table owners to dbo.. and recreate the replication.
It looks like one of the triggers from the older repl setup was still there.
I found the old trigger and deleted it. It was obvious it was old because it
referenced the old user name. There were the 3 correct triggers on the table
as well. One each for insert, update, and delete. So what was happening was
this: there was the old delete trigger on this table and it was listed first
so it executed and failed. The correct trigger never fired then. Now that
old trigger is gone and all works fine.
thanks again.
"Fany Vargas [MSFT]" <fanyv@.online.microsoft.com> wrote in message
news:Yj9qhVuzEHA.3388@.cpmsftngxa10.phx.gbl...
> It seems you have some "invalid" merge triggers (probably from a previous
> publication). Did you republish after changing your table owner name? If
> you do have invalid triggers, you should consider dropping and recreating
> your publication.
> A. Drop the subscription
> B. Drop the publication.
> C. Delete the triggers that reference the non-existant views
> D. Recreate the publication and subscription.
> E. Run the snapshot.
>
> reference:
> How to manually remove a replication in SQL Server 2000 - ID: 324401
> http://support.microsoft.com/?id=324401
> Fany Vargas
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
> Microsoft software to better protect against viruses and security
> vulnerabilities. The easiest way to do this is to visit the following
> websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>

Error when SQL 2000 start

When starting my SQL Server 2000 generate error and stop. This is the log:
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)

2004-01-20 11:05:36.59 server Copyright (C) 1988-2000 Microsoft Corporation.
2004-01-20 11:05:36.59 server All rights reserved.
2004-01-20 11:05:36.59 server Server Process ID is 115.
2004-01-20 11:05:36.59 server Logging SQL Server messages in file 'C:\MSSQL7\log\ERRORLOG'.
2004-01-20 11:05:36.63 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-01-20 11:05:36.66 server SQL Server configured for thread mode processing.
2004-01-20 11:05:36.66 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2004-01-20 11:05:36.67 server Attempting to initialize Distributed Transaction Coordinator.
2004-01-20 11:05:38.69 spid3 Starting up database 'master'.
2004-01-20 11:05:38.85 spid3 Server name is 'DB_SERVER'.
2004-01-20 11:05:38.85 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-01-20 11:05:38.87 server SQL server listening on TCP, Shared Memory, Named Pipes.
2004-01-20 11:05:38.87 server SQL server listening on 192.168.1.29:1433, 172.16.48.10:1433, 127.0.0.1:1433.
2004-01-20 11:05:38.87 server SQL Server is ready for client connections
2004-01-20 11:05:38.87 spid5 Starting up database 'model'.
2004-01-20 11:05:38.87 spid8 Starting up database 'msdb'.
2004-01-20 11:05:38.87 spid9 Starting up database 'pubs'.
2004-01-20 11:05:38.87 spid10 Starting up database 'Northwind'.
2004-01-20 11:05:38.87 spid11 Starting up database 'SIM'.
2004-01-20 11:05:39.21 spid5 Error: 9003, Severity: 20, State: 1
2004-01-20 11:05:39.21 spid5 The LSN (5:377:1) passed to log scan in database 'model' is invalid..
2004-01-20 11:05:39.31 spid8 Bypassing recovery for database 'msdb' because it is marked SUSPECT.
2004-01-20 11:05:39.39 spid11 Starting up database 'GMS'.
2004-01-20 11:05:39.39 spid8 Starting up database 'euro'.
2004-01-20 11:05:40.14 spid10 Starting up database 'TigrisDB'.have you moved your system's devices around recently?|||Originally posted by ms_sql_dba
have you moved your system's devices around recently?

No, but 2 weeks before, I receive a message (Administrator alert) from PC with installed on SQL 2000.

"Drive Z: is nearly full. 1216688128 bytes are available.
Please warn users and delete unneeded files."

On "drive Z:" there is 9GB free space ...

Thanks for reading.
Best Regards|||looks like your system databases is having some problem.
try restarting sql server in single user mode and do a dbcc checkdb on model and msdb.

If this do not work, you might have to rebuild them

amit

Error when issuing OPENQUERY

I'm running on a Windows 2003 server SQL Server 2000. I'm getting the
following error when trying to execute an OPENQUERY statement. I have
about 5 linked servers, and they all worked in the past. Now one of
them is giving me trouble when issuing the OPENQUERY statement with
the following error:
Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider
'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in
the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
I've tried all the Microsoft Workaround solutions:
http://support.microsoft.com/kb/873160 (even if it doesn't apply 100%)
http://support.microsoft.com/default.aspx?scid=kb;en-us;329332
http://support.microsoft.com/default.aspx?scid=kb;en-us;816701
http://support.microsoft.com/?kbid=816701
The linked server has not changed according to the administrator.
There is no firewall under either side of the severs (internal private
network). After enabling DTC under the remote server, I've noticed
that the queries take longer, but they continue returning the same
error as indicated above.
The servers have been configured with 'No authentication on DTC' so I
can't imagine what the problem could be, I've also checked the routing
(IP routes) between the two servers and I can't see any flaw, all
traffic is internal. I say this because the servers host dual cards
(internal and external networks) - but the external network is not
being enabled. Bidirectional traceroutes show the same path.
I've Googled the error messages and they all point to the same thing,
but it appears not to work. I have other SQL servers under the same
internal networks and I can run the OPENQUERY on them.
Can anyone help me out here?
Hi
The last two links you posted are the same!
Have you tried DTCping? http://support.microsoft.com/kb/306843
John
"InvestorTrade" wrote:

> I'm running on a Windows 2003 server SQL Server 2000. I'm getting the
> following error when trying to execute an OPENQUERY statement. I have
> about 5 linked servers, and they all worked in the past. Now one of
> them is giving me trouble when issuing the OPENQUERY statement with
> the following error:
> Server: Msg 7391, Level 16, State 1, Line 1
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB' was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in
> the specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
>
> I've tried all the Microsoft Workaround solutions:
> http://support.microsoft.com/kb/873160 (even if it doesn't apply 100%)
> http://support.microsoft.com/default.aspx?scid=kb;en-us;329332
> http://support.microsoft.com/default.aspx?scid=kb;en-us;816701
> http://support.microsoft.com/?kbid=816701
> The linked server has not changed according to the administrator.
> There is no firewall under either side of the severs (internal private
> network). After enabling DTC under the remote server, I've noticed
> that the queries take longer, but they continue returning the same
> error as indicated above.
> The servers have been configured with 'No authentication on DTC' so I
> can't imagine what the problem could be, I've also checked the routing
> (IP routes) between the two servers and I can't see any flaw, all
> traffic is internal. I say this because the servers host dual cards
> (internal and external networks) - but the external network is not
> being enabled. Bidirectional traceroutes show the same path.
> I've Googled the error messages and they all point to the same thing,
> but it appears not to work. I have other SQL servers under the same
> internal networks and I can run the OPENQUERY on them.
> Can anyone help me out here?
>
>
|||On Jan 7, 12:33Xpm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> The last two links you posted are the same!
> Have you tried DTCping?http://support.microsoft.com/kb/306843
> John
>
> "InvestorTrade" wrote:
>
>
>
>
> - Show quoted text -
Thank you!!! DTCPing helped to spot the problem - Bottom line - the
RPC Locator was shutdown under the remote server - the moment I
enabled it, it worked like a charm.

Error when issuing OPENQUERY

I'm running on a Windows 2003 server SQL Server 2000. I'm getting the
following error when trying to execute an OPENQUERY statement. I have
about 5 linked servers, and they all worked in the past. Now one of
them is giving me trouble when issuing the OPENQUERY statement with
the following error:
Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider
'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in
the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
I've tried all the Microsoft Workaround solutions:
http://support.microsoft.com/kb/873160 (even if it doesn't apply 100%)
http://support.microsoft.com/default.aspx?scid=kb;en-us;329332
http://support.microsoft.com/default.aspx?scid=kb;en-us;816701
http://support.microsoft.com/?kbid=816701
The linked server has not changed according to the administrator.
There is no firewall under either side of the severs (internal private
network). After enabling DTC under the remote server, I've noticed
that the queries take longer, but they continue returning the same
error as indicated above.
The servers have been configured with 'No authentication on DTC' so I
can't imagine what the problem could be, I've also checked the routing
(IP routes) between the two servers and I can't see any flaw, all
traffic is internal. I say this because the servers host dual cards
(internal and external networks) - but the external network is not
being enabled. Bidirectional traceroutes show the same path.
I've Googled the error messages and they all point to the same thing,
but it appears not to work. I have other SQL servers under the same
internal networks and I can run the OPENQUERY on them.
Can anyone help me out here?Hi
The last two links you posted are the same!
Have you tried DTCping? http://support.microsoft.com/kb/306843
John
"InvestorTrade" wrote:
> I'm running on a Windows 2003 server SQL Server 2000. I'm getting the
> following error when trying to execute an OPENQUERY statement. I have
> about 5 linked servers, and they all worked in the past. Now one of
> them is giving me trouble when issuing the OPENQUERY statement with
> the following error:
> Server: Msg 7391, Level 16, State 1, Line 1
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB' was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in
> the specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
>
> I've tried all the Microsoft Workaround solutions:
> http://support.microsoft.com/kb/873160 (even if it doesn't apply 100%)
> http://support.microsoft.com/default.aspx?scid=kb;en-us;329332
> http://support.microsoft.com/default.aspx?scid=kb;en-us;816701
> http://support.microsoft.com/?kbid=816701
> The linked server has not changed according to the administrator.
> There is no firewall under either side of the severs (internal private
> network). After enabling DTC under the remote server, I've noticed
> that the queries take longer, but they continue returning the same
> error as indicated above.
> The servers have been configured with 'No authentication on DTC' so I
> can't imagine what the problem could be, I've also checked the routing
> (IP routes) between the two servers and I can't see any flaw, all
> traffic is internal. I say this because the servers host dual cards
> (internal and external networks) - but the external network is not
> being enabled. Bidirectional traceroutes show the same path.
> I've Googled the error messages and they all point to the same thing,
> but it appears not to work. I have other SQL servers under the same
> internal networks and I can run the OPENQUERY on them.
> Can anyone help me out here?
>
>|||On Jan 7, 12:33=A0pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> The last two links you posted are the same!
> Have you tried DTCping?http://support.microsoft.com/kb/306843
> John
>
> "InvestorTrade" wrote:
> > I'm running on a Windows 2003 server SQL Server 2000. =A0I'm getting the=
> > following error when trying to execute an OPENQUERY statement. =A0I have=
> > about 5 linked servers, and they all worked in the past. =A0Now one of
> > them is giving me trouble when issuing the OPENQUERY statement with
> > the following error:
> > Server: Msg 7391, Level 16, State 1, Line 1
> > The operation could not be performed because the OLE DB provider
> > 'SQLOLEDB' was unable to begin a distributed transaction.
> > [OLE/DB provider returned message: New transaction cannot enlist in
> > the specified transaction coordinator. ]
> > OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> > ITransactionJoin::JoinTransaction returned 0x8004d00a].
> > I've tried all the Microsoft Workaround solutions:
> >http://support.microsoft.com/kb/873160(even if it doesn't apply 100%)
> >http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;329332
> >http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;816701
> >http://support.microsoft.com/?kbid=3D816701
> > The linked server has not changed according to the administrator.
> > There is no firewall under either side of the severs (internal private
> > network). =A0After enabling DTC under the remote server, I've noticed
> > that the queries take longer, but they continue returning the same
> > error as indicated above.
> > The servers have been configured with 'No authentication on DTC' so I
> > can't imagine what the problem could be, I've also checked the routing
> > (IP routes) between the two servers and I can't see any flaw, all
> > traffic is internal. =A0I say this because the servers host dual cards
> > (internal and external networks) - but the external network is not
> > being enabled. =A0Bidirectional traceroutes show the same path.
> > I've Googled the error messages and they all point to the same thing,
> > but it appears not to work. =A0I have other SQL servers under the same
> > internal networks and I can run the OPENQUERY on them.
> > Can anyone help me out here... Hide quoted text -
> - Show quoted text -
Thank you!!! DTCPing helped to spot the problem - Bottom line - the
RPC Locator was shutdown under the remote server - the moment I
enabled it, it worked like a charm.

Error when installing SQL server 200 on SBS 2003 in Windows Small Business Server 2003

Hi,
I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the SBS
2003 server Premium).
I installed the OS lately and made all the Microsoft update.
I am now trying to install the SQL 2000 server and get this error message:
(It is the english translation of what I get on my screen)
Error message: "A previous installation program created operation files
waiting for Installtion on your computer. You have to reboot it before
executing the installation."
Of course I rebooted my server, but nothing happened.
Any idea of what to do ?
Thank you for your help
Did you try installing again after the reboot? Was there an error code
listed?
From KB Article 257716:
Q. What should I do if the installation of SQL Server 2000 is unsuccessful?
A. If you have an unsuccessful installation, you can examine two files to
help determine what went wrong. The Sqlstp.log file, which is located in the
Windows directory, gives detailed information on what setup is doing and
contains all errors encountered during setup. Reviewing this file will give
you a better understanding of where setup fails and why.
During the configuration portion of setup, SQL Server setup runs an
application called Cnfgsvr.exe to configure the SQL Server. This application
starts SQL Server, connects to it, and then runs the initial installation
scripts. Any error encountered during this process is also written to the
Sqlstp.log file; however, you should also review the SQL Server error log,
named "Errorlog" with no file extension, located by default in the Program
Files\Microsoft SQL Server\Mssql\Log directory. This error log contains
errors that SQL Server encounters when setup attempts to start SQL Server,
which may provide further insight into the failure.
If you cannot determine the cause of the Setup failure, save the two files
just mentioned and call Microsoft Product Support Services (PSS) to speak to
a SQL Server Support Professional who will help you to resolve your problem.
Note that when the Setup application fails, it rolls back all changes to the
file system, which includes removing any copied files and changes that were
made to the registry.
HTH
Jerry
"Alambiki" <alambiki@.yahoo.com> wrote in message
news:dj5qnl$ok9$1@.reader1.imaginet.fr...
> Hi,
> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
> SBS
> 2003 server Premium).
> I installed the OS lately and made all the Microsoft update.
> I am now trying to install the SQL 2000 server and get this error message:
> (It is the english translation of what I get on my screen)
> Error message: "A previous installation program created operation files
> waiting for Installtion on your computer. You have to reboot it before
> executing the installation."
> Of course I rebooted my server, but nothing happened.
> Any idea of what to do ?
> Thank you for your help
>
|||Yes I tried to reinstall after reboot.
I found the Sqlstp.log file, but am not able to understand it.
If someone has an idea...
"Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
> Did you try installing again after the reboot? Was there an error code
> listed?
> From KB Article 257716:
> Q. What should I do if the installation of SQL Server 2000 is
> unsuccessful?
> A. If you have an unsuccessful installation, you can examine two files to
> help determine what went wrong. The Sqlstp.log file, which is located in
> the Windows directory, gives detailed information on what setup is doing
> and contains all errors encountered during setup. Reviewing this file will
> give you a better understanding of where setup fails and why.
> During the configuration portion of setup, SQL Server setup runs an
> application called Cnfgsvr.exe to configure the SQL Server. This
> application starts SQL Server, connects to it, and then runs the initial
> installation scripts. Any error encountered during this process is also
> written to the Sqlstp.log file; however, you should also review the SQL
> Server error log, named "Errorlog" with no file extension, located by
> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
> This error log contains errors that SQL Server encounters when setup
> attempts to start SQL Server, which may provide further insight into the
> failure.
> If you cannot determine the cause of the Setup failure, save the two files
> just mentioned and call Microsoft Product Support Services (PSS) to speak
> to a SQL Server Support Professional who will help you to resolve your
> problem. Note that when the Setup application fails, it rolls back all
> changes to the file system, which includes removing any copied files and
> changes that were made to the registry.
>
> HTH
> Jerry
> "Alambiki" <alambiki@.yahoo.com> wrote in message
> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>
|||What were the last few successful entries? Do you have an installation that
WAS successful that you can compare it to?
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356ae9a$0$4336$626a54ce@.news.free.fr...
> Yes I tried to reinstall after reboot.
> I found the Sqlstp.log file, but am not able to understand it.
> If someone has an idea...
> "Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>
|||I already installed SBS + SQL on this server. It is the second time I
install it on this server. The only thing that changes is that I updated
with the latest ms update + installed symantec lifestate...
here is the log of SQLstp.log
19:00:30 Begin Setup
19:00:30 8.00.194
19:00:30 Mode = Normal
19:00:30 ModeType = NORMAL
19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
19:00:30 ValueFTS returned: 1
19:00:30 ValuePID returned: 1
19:00:30 ValueLic returned: 1
19:00:30 System: Small Business Server
19:00:30 SQL Server ProductType: Standard Edition [0x2]
19:00:30 Begin Action: SetupInitialize
19:00:30 End Action SetupInitialize
19:00:30 Begin Action: SetupInstall
19:00:30 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir
...
19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
19:00:30 Windows Directory=C:\WINDOWS\
19:00:30 Program Files=C:\Program Files\
19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\
19:00:30 Begin Action: SetupInstall
19:00:30 Begin Action: CheckFixedRequirements
19:00:30 Platform ID: 0xf000
19:00:30 Version: 5.2.3790
19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
19:00:31 End Action: CheckFixedRequirements
19:00:31 Begin Action: ShowDialogs
19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
19:00:31 Begin Action ShowDialogsHlpr: 0x1
19:00:31 Begin Action: DialogShowSdWelcome
19:00:32 End Action DialogShowSdWelcome
19:00:32 Dialog 0x1 returned: 1
19:00:32 End Action ShowDialogsHlpr
19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
19:00:32 Begin Action ShowDialogsHlpr: 0x2
19:00:32 Begin Action: DialogShowSdMachineName
19:01:07 ShowDlgMachine returned: -1
19:01:07 ShowDlgMachine: GetLastError returned: 0
19:01:07 Opration russie.
19:01:07 End Action DialogShowSdMachineName
19:01:07 End Action ShowDialogs
19:01:07 Action CleanUpInstall:
19:01:07 StatsGenerate returned: 2
19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
19:01:07 StatsGenerate -1,)
19:01:07 Installation Failed.
"Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
> What were the last few successful entries? Do you have an installation
> that WAS successful that you can compare it to?
> "aLAMBIKI" <alambiki@.yahoo.com> wrote in message
> news:4356ae9a$0$4336$626a54ce@.news.free.fr...
>
|||I'm sure one of the MS guys will jump in here somewhere and give you more
than I can. Can you remove the Symantic product as a test?
HTH
Jerry
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356c190$1$4337$626a54ce@.news.free.fr...
>I already installed SBS + SQL on this server. It is the second time I
>install it on this server. The only thing that changes is that I updated
>with the latest ms update + installed symantec lifestate...
> here is the log of SQLstp.log
> 19:00:30 Begin Setup
> 19:00:30 8.00.194
> 19:00:30 Mode = Normal
> 19:00:30 ModeType = NORMAL
> 19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
> 19:00:30 ValueFTS returned: 1
> 19:00:30 ValuePID returned: 1
> 19:00:30 ValueLic returned: 1
> 19:00:30 System: Small Business Server
> 19:00:30 SQL Server ProductType: Standard Edition [0x2]
> 19:00:30 Begin Action: SetupInitialize
> 19:00:30 End Action SetupInitialize
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir
> ...
> 19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
> 19:00:30 Windows Directory=C:\WINDOWS\
> 19:00:30 Program Files=C:\Program Files\
> 19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Begin Action: CheckFixedRequirements
> 19:00:30 Platform ID: 0xf000
> 19:00:30 Version: 5.2.3790
> 19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
> 19:00:31 End Action: CheckFixedRequirements
> 19:00:31 Begin Action: ShowDialogs
> 19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
> 19:00:31 Begin Action ShowDialogsHlpr: 0x1
> 19:00:31 Begin Action: DialogShowSdWelcome
> 19:00:32 End Action DialogShowSdWelcome
> 19:00:32 Dialog 0x1 returned: 1
> 19:00:32 End Action ShowDialogsHlpr
> 19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
> 19:00:32 Begin Action ShowDialogsHlpr: 0x2
> 19:00:32 Begin Action: DialogShowSdMachineName
> 19:01:07 ShowDlgMachine returned: -1
> 19:01:07 ShowDlgMachine: GetLastError returned: 0
> 19:01:07 Opration russie.
> 19:01:07 End Action DialogShowSdMachineName
> 19:01:07 End Action ShowDialogs
> 19:01:07 Action CleanUpInstall:
> 19:01:07 StatsGenerate returned: 2
> 19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
> 19:01:07 StatsGenerate -1,)
> 19:01:07 Installation Failed.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
> OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
>

Error when installing SQL server 200 on SBS 2003 in Windows Small Business Server 2003

Hi,
I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the SBS
2003 server Premium).
I installed the OS lately and made all the Microsoft update.
I am now trying to install the SQL 2000 server and get this error message:
(It is the english translation of what I get on my screen)
Error message: "A previous installation program created operation files
waiting for Installtion on your computer. You have to reboot it before
executing the installation."
Of course I rebooted my server, but nothing happened.
Any idea of what to do ?
Thank you for your helpDid you try installing again after the reboot? Was there an error code
listed?
From KB Article 257716:
Q. What should I do if the installation of SQL Server 2000 is unsuccessful?
A. If you have an unsuccessful installation, you can examine two files to
help determine what went wrong. The Sqlstp.log file, which is located in the
Windows directory, gives detailed information on what setup is doing and
contains all errors encountered during setup. Reviewing this file will give
you a better understanding of where setup fails and why.
During the configuration portion of setup, SQL Server setup runs an
application called Cnfgsvr.exe to configure the SQL Server. This application
starts SQL Server, connects to it, and then runs the initial installation
scripts. Any error encountered during this process is also written to the
Sqlstp.log file; however, you should also review the SQL Server error log,
named "Errorlog" with no file extension, located by default in the Program
Files\Microsoft SQL Server\Mssql\Log directory. This error log contains
errors that SQL Server encounters when setup attempts to start SQL Server,
which may provide further insight into the failure.
If you cannot determine the cause of the Setup failure, save the two files
just mentioned and call Microsoft Product Support Services (PSS) to speak to
a SQL Server Support Professional who will help you to resolve your problem.
Note that when the Setup application fails, it rolls back all changes to the
file system, which includes removing any copied files and changes that were
made to the registry.
HTH
Jerry
"Alambiki" <alambiki@.yahoo.com> wrote in message
news:dj5qnl$ok9$1@.reader1.imaginet.fr...
> Hi,
> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
> SBS
> 2003 server Premium).
> I installed the OS lately and made all the Microsoft update.
> I am now trying to install the SQL 2000 server and get this error message:
> (It is the english translation of what I get on my screen)
> Error message: "A previous installation program created operation files
> waiting for Installtion on your computer. You have to reboot it before
> executing the installation."
> Of course I rebooted my server, but nothing happened.
> Any idea of what to do ?
> Thank you for your help
>|||Yes I tried to reinstall after reboot.
I found the Sqlstp.log file, but am not able to understand it.
If someone has an idea...
"Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
> Did you try installing again after the reboot? Was there an error code
> listed?
> From KB Article 257716:
> Q. What should I do if the installation of SQL Server 2000 is
> unsuccessful?
> A. If you have an unsuccessful installation, you can examine two files to
> help determine what went wrong. The Sqlstp.log file, which is located in
> the Windows directory, gives detailed information on what setup is doing
> and contains all errors encountered during setup. Reviewing this file will
> give you a better understanding of where setup fails and why.
> During the configuration portion of setup, SQL Server setup runs an
> application called Cnfgsvr.exe to configure the SQL Server. This
> application starts SQL Server, connects to it, and then runs the initial
> installation scripts. Any error encountered during this process is also
> written to the Sqlstp.log file; however, you should also review the SQL
> Server error log, named "Errorlog" with no file extension, located by
> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
> This error log contains errors that SQL Server encounters when setup
> attempts to start SQL Server, which may provide further insight into the
> failure.
> If you cannot determine the cause of the Setup failure, save the two files
> just mentioned and call Microsoft Product Support Services (PSS) to speak
> to a SQL Server Support Professional who will help you to resolve your
> problem. Note that when the Setup application fails, it rolls back all
> changes to the file system, which includes removing any copied files and
> changes that were made to the registry.
>
> HTH
> Jerry
> "Alambiki" <alambiki@.yahoo.com> wrote in message
> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>|||What were the last few successful entries? Do you have an installation that
WAS successful that you can compare it to?
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356ae9a$0$4336$626a54ce@.news.free.fr...
> Yes I tried to reinstall after reboot.
> I found the Sqlstp.log file, but am not able to understand it.
> If someone has an idea...
> "Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>|||I already installed SBS + SQL on this server. It is the second time I
install it on this server. The only thing that changes is that I updated
with the latest ms update + installed symantec lifestate...
here is the log of SQLstp.log
19:00:30 Begin Setup
19:00:30 8.00.194
19:00:30 Mode = Normal
19:00:30 ModeType = NORMAL
19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
19:00:30 ValueFTS returned: 1
19:00:30 ValuePID returned: 1
19:00:30 ValueLic returned: 1
19:00:30 System: Small Business Server
19:00:30 SQL Server ProductType: Standard Edition [0x2]
19:00:30 Begin Action: SetupInitialize
19:00:30 End Action SetupInitialize
19:00:30 Begin Action: SetupInstall
19:00:30 Reading Software\Microsoft\Windows\CurrentVersio
n\CommonFilesDir
...
19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
19:00:30 Windows Directory=C:\WINDOWS\
19:00:30 Program Files=C:\Program Files\
19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Te
mp\1\
19:00:30 Begin Action: SetupInstall
19:00:30 Begin Action: CheckFixedRequirements
19:00:30 Platform ID: 0xf000
19:00:30 Version: 5.2.3790
19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
19:00:31 End Action: CheckFixedRequirements
19:00:31 Begin Action: ShowDialogs
19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
19:00:31 Begin Action ShowDialogsHlpr: 0x1
19:00:31 Begin Action: DialogShowSdWelcome
19:00:32 End Action DialogShowSdWelcome
19:00:32 Dialog 0x1 returned: 1
19:00:32 End Action ShowDialogsHlpr
19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
19:00:32 Begin Action ShowDialogsHlpr: 0x2
19:00:32 Begin Action: DialogShowSdMachineName
19:01:07 ShowDlgMachine returned: -1
19:01:07 ShowDlgMachine: GetLastError returned: 0
19:01:07 Opration russie.
19:01:07 End Action DialogShowSdMachineName
19:01:07 End Action ShowDialogs
19:01:07 Action CleanUpInstall:
19:01:07 StatsGenerate returned: 2
19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
19:01:07 StatsGenerate -1,)
19:01:07 Installation Failed.
"Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
> What were the last few successful entries? Do you have an installation
> that WAS successful that you can compare it to?
> "aLAMBIKI" <alambiki@.yahoo.com> wrote in message
> news:4356ae9a$0$4336$626a54ce@.news.free.fr...
>|||I'm sure one of the MS guys will jump in here somewhere and give you more
than I can. Can you remove the Symantic product as a test?
HTH
Jerry
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356c190$1$4337$626a54ce@.news.free.fr...
>I already installed SBS + SQL on this server. It is the second time I
>install it on this server. The only thing that changes is that I updated
>with the latest ms update + installed symantec lifestate...
> here is the log of SQLstp.log
> 19:00:30 Begin Setup
> 19:00:30 8.00.194
> 19:00:30 Mode = Normal
> 19:00:30 ModeType = NORMAL
> 19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
> 19:00:30 ValueFTS returned: 1
> 19:00:30 ValuePID returned: 1
> 19:00:30 ValueLic returned: 1
> 19:00:30 System: Small Business Server
> 19:00:30 SQL Server ProductType: Standard Edition [0x2]
> 19:00:30 Begin Action: SetupInitialize
> 19:00:30 End Action SetupInitialize
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Reading Software\Microsoft\Windows\CurrentVersio
n\CommonFilesDir
> ...
> 19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
> 19:00:30 Windows Directory=C:\WINDOWS\
> 19:00:30 Program Files=C:\Program Files\
> 19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Te
mp\1\
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Begin Action: CheckFixedRequirements
> 19:00:30 Platform ID: 0xf000
> 19:00:30 Version: 5.2.3790
> 19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
> 19:00:31 End Action: CheckFixedRequirements
> 19:00:31 Begin Action: ShowDialogs
> 19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
> 19:00:31 Begin Action ShowDialogsHlpr: 0x1
> 19:00:31 Begin Action: DialogShowSdWelcome
> 19:00:32 End Action DialogShowSdWelcome
> 19:00:32 Dialog 0x1 returned: 1
> 19:00:32 End Action ShowDialogsHlpr
> 19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
> 19:00:32 Begin Action ShowDialogsHlpr: 0x2
> 19:00:32 Begin Action: DialogShowSdMachineName
> 19:01:07 ShowDlgMachine returned: -1
> 19:01:07 ShowDlgMachine: GetLastError returned: 0
> 19:01:07 Opration russie.
> 19:01:07 End Action DialogShowSdMachineName
> 19:01:07 End Action ShowDialogs
> 19:01:07 Action CleanUpInstall:
> 19:01:07 StatsGenerate returned: 2
> 19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
> 19:01:07 StatsGenerate -1,)
> 19:01:07 Installation Failed.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
> OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
>

Error when installing SQL server 200 on SBS 2003 in Windows Small Business Server 2003

Hi,
I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the SBS
2003 server Premium).
I installed the OS lately and made all the Microsoft update.
I am now trying to install the SQL 2000 server and get this error message:
(It is the english translation of what I get on my screen)
Error message: "A previous installation program created operation files
waiting for Installtion on your computer. You have to reboot it before
executing the installation."
Of course I rebooted my server, but nothing happened.
Any idea of what to do ?
Thank you for your helpDid you try installing again after the reboot? Was there an error code
listed?
From KB Article 257716:
Q. What should I do if the installation of SQL Server 2000 is unsuccessful?
A. If you have an unsuccessful installation, you can examine two files to
help determine what went wrong. The Sqlstp.log file, which is located in the
Windows directory, gives detailed information on what setup is doing and
contains all errors encountered during setup. Reviewing this file will give
you a better understanding of where setup fails and why.
During the configuration portion of setup, SQL Server setup runs an
application called Cnfgsvr.exe to configure the SQL Server. This application
starts SQL Server, connects to it, and then runs the initial installation
scripts. Any error encountered during this process is also written to the
Sqlstp.log file; however, you should also review the SQL Server error log,
named "Errorlog" with no file extension, located by default in the Program
Files\Microsoft SQL Server\Mssql\Log directory. This error log contains
errors that SQL Server encounters when setup attempts to start SQL Server,
which may provide further insight into the failure.
If you cannot determine the cause of the Setup failure, save the two files
just mentioned and call Microsoft Product Support Services (PSS) to speak to
a SQL Server Support Professional who will help you to resolve your problem.
Note that when the Setup application fails, it rolls back all changes to the
file system, which includes removing any copied files and changes that were
made to the registry.
HTH
Jerry
"Alambiki" <alambiki@.yahoo.com> wrote in message
news:dj5qnl$ok9$1@.reader1.imaginet.fr...
> Hi,
> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
> SBS
> 2003 server Premium).
> I installed the OS lately and made all the Microsoft update.
> I am now trying to install the SQL 2000 server and get this error message:
> (It is the english translation of what I get on my screen)
> Error message: "A previous installation program created operation files
> waiting for Installtion on your computer. You have to reboot it before
> executing the installation."
> Of course I rebooted my server, but nothing happened.
> Any idea of what to do ?
> Thank you for your help
>|||Yes I tried to reinstall after reboot.
I found the Sqlstp.log file, but am not able to understand it.
If someone has an idea...
"Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
> Did you try installing again after the reboot? Was there an error code
> listed?
> From KB Article 257716:
> Q. What should I do if the installation of SQL Server 2000 is
> unsuccessful?
> A. If you have an unsuccessful installation, you can examine two files to
> help determine what went wrong. The Sqlstp.log file, which is located in
> the Windows directory, gives detailed information on what setup is doing
> and contains all errors encountered during setup. Reviewing this file will
> give you a better understanding of where setup fails and why.
> During the configuration portion of setup, SQL Server setup runs an
> application called Cnfgsvr.exe to configure the SQL Server. This
> application starts SQL Server, connects to it, and then runs the initial
> installation scripts. Any error encountered during this process is also
> written to the Sqlstp.log file; however, you should also review the SQL
> Server error log, named "Errorlog" with no file extension, located by
> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
> This error log contains errors that SQL Server encounters when setup
> attempts to start SQL Server, which may provide further insight into the
> failure.
> If you cannot determine the cause of the Setup failure, save the two files
> just mentioned and call Microsoft Product Support Services (PSS) to speak
> to a SQL Server Support Professional who will help you to resolve your
> problem. Note that when the Setup application fails, it rolls back all
> changes to the file system, which includes removing any copied files and
> changes that were made to the registry.
>
> HTH
> Jerry
> "Alambiki" <alambiki@.yahoo.com> wrote in message
> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>> Hi,
>> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
>> SBS
>> 2003 server Premium).
>> I installed the OS lately and made all the Microsoft update.
>> I am now trying to install the SQL 2000 server and get this error
>> message:
>> (It is the english translation of what I get on my screen)
>> Error message: "A previous installation program created operation files
>> waiting for Installtion on your computer. You have to reboot it before
>> executing the installation."
>> Of course I rebooted my server, but nothing happened.
>> Any idea of what to do ?
>> Thank you for your help
>|||What were the last few successful entries? Do you have an installation that
WAS successful that you can compare it to?
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356ae9a$0$4336$626a54ce@.news.free.fr...
> Yes I tried to reinstall after reboot.
> I found the Sqlstp.log file, but am not able to understand it.
> If someone has an idea...
> "Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>> Did you try installing again after the reboot? Was there an error code
>> listed?
>> From KB Article 257716:
>> Q. What should I do if the installation of SQL Server 2000 is
>> unsuccessful?
>> A. If you have an unsuccessful installation, you can examine two files to
>> help determine what went wrong. The Sqlstp.log file, which is located in
>> the Windows directory, gives detailed information on what setup is doing
>> and contains all errors encountered during setup. Reviewing this file
>> will give you a better understanding of where setup fails and why.
>> During the configuration portion of setup, SQL Server setup runs an
>> application called Cnfgsvr.exe to configure the SQL Server. This
>> application starts SQL Server, connects to it, and then runs the initial
>> installation scripts. Any error encountered during this process is also
>> written to the Sqlstp.log file; however, you should also review the SQL
>> Server error log, named "Errorlog" with no file extension, located by
>> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
>> This error log contains errors that SQL Server encounters when setup
>> attempts to start SQL Server, which may provide further insight into the
>> failure.
>> If you cannot determine the cause of the Setup failure, save the two
>> files just mentioned and call Microsoft Product Support Services (PSS) to
>> speak to a SQL Server Support Professional who will help you to resolve
>> your problem. Note that when the Setup application fails, it rolls back
>> all changes to the file system, which includes removing any copied files
>> and changes that were made to the registry.
>>
>> HTH
>> Jerry
>> "Alambiki" <alambiki@.yahoo.com> wrote in message
>> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>> Hi,
>> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
>> SBS
>> 2003 server Premium).
>> I installed the OS lately and made all the Microsoft update.
>> I am now trying to install the SQL 2000 server and get this error
>> message:
>> (It is the english translation of what I get on my screen)
>> Error message: "A previous installation program created operation files
>> waiting for Installtion on your computer. You have to reboot it before
>> executing the installation."
>> Of course I rebooted my server, but nothing happened.
>> Any idea of what to do ?
>> Thank you for your help
>>
>|||I already installed SBS + SQL on this server. It is the second time I
install it on this server. The only thing that changes is that I updated
with the latest ms update + installed symantec lifestate...
here is the log of SQLstp.log
19:00:30 Begin Setup
19:00:30 8.00.194
19:00:30 Mode = Normal
19:00:30 ModeType = NORMAL
19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
19:00:30 ValueFTS returned: 1
19:00:30 ValuePID returned: 1
19:00:30 ValueLic returned: 1
19:00:30 System: Small Business Server
19:00:30 SQL Server ProductType: Standard Edition [0x2]
19:00:30 Begin Action: SetupInitialize
19:00:30 End Action SetupInitialize
19:00:30 Begin Action: SetupInstall
19:00:30 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir
...
19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
19:00:30 Windows Directory=C:\WINDOWS\
19:00:30 Program Files=C:\Program Files\
19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\
19:00:30 Begin Action: SetupInstall
19:00:30 Begin Action: CheckFixedRequirements
19:00:30 Platform ID: 0xf000
19:00:30 Version: 5.2.3790
19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
19:00:31 End Action: CheckFixedRequirements
19:00:31 Begin Action: ShowDialogs
19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
19:00:31 Begin Action ShowDialogsHlpr: 0x1
19:00:31 Begin Action: DialogShowSdWelcome
19:00:32 End Action DialogShowSdWelcome
19:00:32 Dialog 0x1 returned: 1
19:00:32 End Action ShowDialogsHlpr
19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
19:00:32 Begin Action ShowDialogsHlpr: 0x2
19:00:32 Begin Action: DialogShowSdMachineName
19:01:07 ShowDlgMachine returned: -1
19:01:07 ShowDlgMachine: GetLastError returned: 0
19:01:07 Opération réussie.
19:01:07 End Action DialogShowSdMachineName
19:01:07 End Action ShowDialogs
19:01:07 Action CleanUpInstall:
19:01:07 StatsGenerate returned: 2
19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
19:01:07 StatsGenerate -1,)
19:01:07 Installation Failed.
"Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
> What were the last few successful entries? Do you have an installation
> that WAS successful that you can compare it to?
> "aLAMBIKI" <alambiki@.yahoo.com> wrote in message
> news:4356ae9a$0$4336$626a54ce@.news.free.fr...
>> Yes I tried to reinstall after reboot.
>> I found the Sqlstp.log file, but am not able to understand it.
>> If someone has an idea...
>> "Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
>> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>> Did you try installing again after the reboot? Was there an error code
>> listed?
>> From KB Article 257716:
>> Q. What should I do if the installation of SQL Server 2000 is
>> unsuccessful?
>> A. If you have an unsuccessful installation, you can examine two files
>> to help determine what went wrong. The Sqlstp.log file, which is located
>> in the Windows directory, gives detailed information on what setup is
>> doing and contains all errors encountered during setup. Reviewing this
>> file will give you a better understanding of where setup fails and why.
>> During the configuration portion of setup, SQL Server setup runs an
>> application called Cnfgsvr.exe to configure the SQL Server. This
>> application starts SQL Server, connects to it, and then runs the initial
>> installation scripts. Any error encountered during this process is also
>> written to the Sqlstp.log file; however, you should also review the SQL
>> Server error log, named "Errorlog" with no file extension, located by
>> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
>> This error log contains errors that SQL Server encounters when setup
>> attempts to start SQL Server, which may provide further insight into the
>> failure.
>> If you cannot determine the cause of the Setup failure, save the two
>> files just mentioned and call Microsoft Product Support Services (PSS)
>> to speak to a SQL Server Support Professional who will help you to
>> resolve your problem. Note that when the Setup application fails, it
>> rolls back all changes to the file system, which includes removing any
>> copied files and changes that were made to the registry.
>>
>> HTH
>> Jerry
>> "Alambiki" <alambiki@.yahoo.com> wrote in message
>> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>> Hi,
>> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
>> SBS
>> 2003 server Premium).
>> I installed the OS lately and made all the Microsoft update.
>> I am now trying to install the SQL 2000 server and get this error
>> message:
>> (It is the english translation of what I get on my screen)
>> Error message: "A previous installation program created operation files
>> waiting for Installtion on your computer. You have to reboot it before
>> executing the installation."
>> Of course I rebooted my server, but nothing happened.
>> Any idea of what to do ?
>> Thank you for your help
>>
>>
>|||I'm sure one of the MS guys will jump in here somewhere and give you more
than I can. Can you remove the Symantic product as a test?
HTH
Jerry
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356c190$1$4337$626a54ce@.news.free.fr...
>I already installed SBS + SQL on this server. It is the second time I
>install it on this server. The only thing that changes is that I updated
>with the latest ms update + installed symantec lifestate...
> here is the log of SQLstp.log
> 19:00:30 Begin Setup
> 19:00:30 8.00.194
> 19:00:30 Mode = Normal
> 19:00:30 ModeType = NORMAL
> 19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
> 19:00:30 ValueFTS returned: 1
> 19:00:30 ValuePID returned: 1
> 19:00:30 ValueLic returned: 1
> 19:00:30 System: Small Business Server
> 19:00:30 SQL Server ProductType: Standard Edition [0x2]
> 19:00:30 Begin Action: SetupInitialize
> 19:00:30 End Action SetupInitialize
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir
> ...
> 19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
> 19:00:30 Windows Directory=C:\WINDOWS\
> 19:00:30 Program Files=C:\Program Files\
> 19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Begin Action: CheckFixedRequirements
> 19:00:30 Platform ID: 0xf000
> 19:00:30 Version: 5.2.3790
> 19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
> 19:00:31 End Action: CheckFixedRequirements
> 19:00:31 Begin Action: ShowDialogs
> 19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
> 19:00:31 Begin Action ShowDialogsHlpr: 0x1
> 19:00:31 Begin Action: DialogShowSdWelcome
> 19:00:32 End Action DialogShowSdWelcome
> 19:00:32 Dialog 0x1 returned: 1
> 19:00:32 End Action ShowDialogsHlpr
> 19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
> 19:00:32 Begin Action ShowDialogsHlpr: 0x2
> 19:00:32 Begin Action: DialogShowSdMachineName
> 19:01:07 ShowDlgMachine returned: -1
> 19:01:07 ShowDlgMachine: GetLastError returned: 0
> 19:01:07 Opération réussie.
> 19:01:07 End Action DialogShowSdMachineName
> 19:01:07 End Action ShowDialogs
> 19:01:07 Action CleanUpInstall:
> 19:01:07 StatsGenerate returned: 2
> 19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
> 19:01:07 StatsGenerate -1,)
> 19:01:07 Installation Failed.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
> OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
>> What were the last few successful entries? Do you have an installation
>> that WAS successful that you can compare it to?
>> "aLAMBIKI" <alambiki@.yahoo.com> wrote in message
>> news:4356ae9a$0$4336$626a54ce@.news.free.fr...
>> Yes I tried to reinstall after reboot.
>> I found the Sqlstp.log file, but am not able to understand it.
>> If someone has an idea...
>> "Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
>> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>> Did you try installing again after the reboot? Was there an error code
>> listed?
>> From KB Article 257716:
>> Q. What should I do if the installation of SQL Server 2000 is
>> unsuccessful?
>> A. If you have an unsuccessful installation, you can examine two files
>> to help determine what went wrong. The Sqlstp.log file, which is
>> located in the Windows directory, gives detailed information on what
>> setup is doing and contains all errors encountered during setup.
>> Reviewing this file will give you a better understanding of where setup
>> fails and why.
>> During the configuration portion of setup, SQL Server setup runs an
>> application called Cnfgsvr.exe to configure the SQL Server. This
>> application starts SQL Server, connects to it, and then runs the
>> initial installation scripts. Any error encountered during this process
>> is also written to the Sqlstp.log file; however, you should also review
>> the SQL Server error log, named "Errorlog" with no file extension,
>> located by default in the Program Files\Microsoft SQL Server\Mssql\Log
>> directory. This error log contains errors that SQL Server encounters
>> when setup attempts to start SQL Server, which may provide further
>> insight into the failure.
>> If you cannot determine the cause of the Setup failure, save the two
>> files just mentioned and call Microsoft Product Support Services (PSS)
>> to speak to a SQL Server Support Professional who will help you to
>> resolve your problem. Note that when the Setup application fails, it
>> rolls back all changes to the file system, which includes removing any
>> copied files and changes that were made to the registry.
>>
>> HTH
>> Jerry
>> "Alambiki" <alambiki@.yahoo.com> wrote in message
>> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>> Hi,
>> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own
>> the SBS
>> 2003 server Premium).
>> I installed the OS lately and made all the Microsoft update.
>> I am now trying to install the SQL 2000 server and get this error
>> message:
>> (It is the english translation of what I get on my screen)
>> Error message: "A previous installation program created operation
>> files
>> waiting for Installtion on your computer. You have to reboot it before
>> executing the installation."
>> Of course I rebooted my server, but nothing happened.
>> Any idea of what to do ?
>> Thank you for your help
>>
>>
>>
>sql

Error when installing Reporting Services in Virtual PC 2004

When I tried installing Reporting Services in Windows Server 2003 under
Virtual PC 2004 it displays a message "Error!". I have already installed
VS.NET 2003 and SQL Server 2000 with SP3. Please help.Hi Randy:
I've installed RS on a couple VPCs, so I don't think it would be a
general problem with VPC. I'm wondering what the problem could be. Do
you have 2003 configured as an application server (IIS, ASP.NET
enabled) before the install?
--
Scott
http://www.OdeToCode.com/blogs/scott/
On Wed, 3 Nov 2004 19:23:02 -0800, "Randy Gadingan" <Randy
Gadingan@.discussions.microsoft.com> wrote:
>When I tried installing Reporting Services in Windows Server 2003 under
>Virtual PC 2004 it displays a message "Error!". I have already installed
>VS.NET 2003 and SQL Server 2000 with SP3. Please help.|||Hi Scott:
I have configured Windows Server 2003 as an application server before
installing VS NET 2003 and SQL Reporting Services.
"Scott Allen" wrote:
> Hi Randy:
> I've installed RS on a couple VPCs, so I don't think it would be a
> general problem with VPC. I'm wondering what the problem could be. Do
> you have 2003 configured as an application server (IIS, ASP.NET
> enabled) before the install?
> --
> Scott
> http://www.OdeToCode.com/blogs/scott/
> On Wed, 3 Nov 2004 19:23:02 -0800, "Randy Gadingan" <Randy
> Gadingan@.discussions.microsoft.com> wrote:
> >When I tried installing Reporting Services in Windows Server 2003 under
> >Virtual PC 2004 it displays a message "Error!". I have already installed
> >VS.NET 2003 and SQL Server 2000 with SP3. Please help.
>

error when connecting trhough enterprise manager

hi all ,
i've got an application with sql databse. it runs correctly on the server.
when i go to windows Xp and installed the appliaction and run the sql
enterprise manager to connect to the server, i get the following error:
message =: ExecuteReader requires an open and available connection. the
connection's current state is closed.
i've checked network connection ..it is ok.
the same application we've tested at office ...its working fine.
plz advise
kryshzt
Hi
Are you sure? This error's message is pretty clear, isn't it?
"kryshzt" <kryshzt@.discussions.microsoft.com> wrote in message
news:8636B1D3-80F7-40C7-A384-3DC1E6E9C8ED@.microsoft.com...
> hi all ,
> i've got an application with sql databse. it runs correctly on the server.
> when i go to windows Xp and installed the appliaction and run the sql
> enterprise manager to connect to the server, i get the following error:
> message =: ExecuteReader requires an open and available connection. the
> connection's current state is closed.
> i've checked network connection ..it is ok.
> the same application we've tested at office ...its working fine.
> plz advise
> kryshzt

error when connecting trhough enterprise manager

hi all ,
i've got an application with sql databse. it runs correctly on the server.
when i go to Windows XP and installed the appliaction and run the sql
enterprise manager to connect to the server, i get the following error:
message =: ExecuteReader requires an open and available connection. the
connection's current state is closed.
i've checked network connection ..it is ok.
the same application we've tested at office ...its working fine.
plz advise
kryshztHi
Are you sure? This error's message is pretty clear, isn't it?
"kryshzt" <kryshzt@.discussions.microsoft.com> wrote in message
news:8636B1D3-80F7-40C7-A384-3DC1E6E9C8ED@.microsoft.com...
> hi all ,
> i've got an application with sql databse. it runs correctly on the server.
> when i go to Windows XP and installed the appliaction and run the sql
> enterprise manager to connect to the server, i get the following error:
> message =: ExecuteReader requires an open and available connection. the
> connection's current state is closed.
> i've checked network connection ..it is ok.
> the same application we've tested at office ...its working fine.
> plz advise
> kryshzt

error when connecting trhough enterprise manager

hi all ,
i've got an application with sql databse. it runs correctly on the server.
when i go to windows Xp and installed the appliaction and run the sql
enterprise manager to connect to the server, i get the following error:
message =: ExecuteReader requires an open and available connection. the
connection's current state is closed.
i've checked network connection ..it is ok.
the same application we've tested at office ...its working fine.
plz advise
kryshztHi
Are you sure? This error's message is pretty clear, isn't it?
"kryshzt" <kryshzt@.discussions.microsoft.com> wrote in message
news:8636B1D3-80F7-40C7-A384-3DC1E6E9C8ED@.microsoft.com...
> hi all ,
> i've got an application with sql databse. it runs correctly on the server.
> when i go to windows Xp and installed the appliaction and run the sql
> enterprise manager to connect to the server, i get the following error:
> message =: ExecuteReader requires an open and available connection. the
> connection's current state is closed.
> i've checked network connection ..it is ok.
> the same application we've tested at office ...its working fine.
> plz advise
> kryshzt