it's very urgent regarding XP_SEND MAIL

Hi,
I have a problem in sending mail from sql server 2000 which is using
windows 2000 professional and outlook express
Iam pasting my code below
/
************************************************************************************************************
Create procedure Pub_SendingMail
as
declare
@.EmailAddTO varchar(30),
@.EmailSubject varchar(130),
@.EmailText varchar(255),
@.return int,
@.Counting int
@.
begin
/* SET value */
set @.return = 0
set @.Counting = 0
set @.EmailSubject = 'TEST EMAIL'
set @.EmailText = 'This is a test email'
set @.EmailAddTO = 'nagesh@.emids.com'
/* LOOP. If e-mail is sent, break loop; ELSE WAIT 10 seconds, and
then RETRY. */
WHILE 1=1
begin
set @.Counting = @.Counting + 1
exec @.return = master.dbo.xp_sendmail
@.recipients = @.EmailAddTO,
@.message = @.EmailText ,
@.subject = @.EmailSubject
@.attachments = 'c:\attachment.txt'
/* CHECK value, break if SUCCESS */
if @.return = 0
begin
print 'EMAIL SENT'
break
end
else
begin
/* Try 1 times */
if @.Counting = 1
break
print 'EMAIL FAILED, WAIT 10 SECONDS, TRY AGAIN'
/*000 hours, 00 minutes, and 10 seconds */
waitfor delay '000:00:03'
end
end
end
*****************************************************************************************************************/
and when iam executing
EXEC Pub_SendingMail
it is giving the following error
Server: Msg 18030, Level 16, State 1, Line 0
xp_sendmail: Either there is no default mail client or the current
mail client cannot fulfill the messaging request. Please run Microsoft
Outlook and set it as the default mail client.
but here i need to send mail not only to out look express but also
general mail servers
I would deeply appriciate if any body can help me about this issue
and send any modifications in the above code.And also how to configure
the Microsoft Outlook Express as the default mail client.
it is very very very very very urgent
Regards
prasadXp_sendmail cannot use Outlook Express. Do yourself a big favor and use xp_smtp_sendmail from
www.sqldev.net.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<shyam.yarlagadda@.gmail.com> wrote in message
news:1170414875.690570.8220@.v45g2000cwv.googlegroups.com...
> Hi,
> I have a problem in sending mail from sql server 2000 which is using
> windows 2000 professional and outlook express
> Iam pasting my code below
> /
> ************************************************************************************************************
> Create procedure Pub_SendingMail
> as
> declare
> @.EmailAddTO varchar(30),
> @.EmailSubject varchar(130),
> @.EmailText varchar(255),
> @.return int,
> @.Counting int
> @.
> begin
> /* SET value */
> set @.return = 0
> set @.Counting = 0
> set @.EmailSubject = 'TEST EMAIL'
> set @.EmailText = 'This is a test email'
> set @.EmailAddTO = 'nagesh@.emids.com'
> /* LOOP. If e-mail is sent, break loop; ELSE WAIT 10 seconds, and
> then RETRY. */
> WHILE 1=1
> begin
> set @.Counting = @.Counting + 1
> exec @.return = master.dbo.xp_sendmail
> @.recipients = @.EmailAddTO,
> @.message = @.EmailText ,
> @.subject = @.EmailSubject
> @.attachments = 'c:\attachment.txt'
> /* CHECK value, break if SUCCESS */
> if @.return = 0
> begin
> print 'EMAIL SENT'
> break
> end
> else
> begin
> /* Try 1 times */
> if @.Counting = 1
> break
> print 'EMAIL FAILED, WAIT 10 SECONDS, TRY AGAIN'
> /*000 hours, 00 minutes, and 10 seconds */
> waitfor delay '000:00:03'
> end
> end
> end
> *****************************************************************************************************************/
> and when iam executing
> EXEC Pub_SendingMail
> it is giving the following error
> Server: Msg 18030, Level 16, State 1, Line 0
> xp_sendmail: Either there is no default mail client or the current
> mail client cannot fulfill the messaging request. Please run Microsoft
> Outlook and set it as the default mail client.
> but here i need to send mail not only to out look express but also
> general mail servers
> I would deeply appriciate if any body can help me about this issue
> and send any modifications in the above code.And also how to configure
> the Microsoft Outlook Express as the default mail client.
> it is very very very very very urgent
> Regards
> prasad
>|||You'll need to set up a MAPI mail profile for this to work. Alternatively
you could use the XPSMTP.DLL which is free
(http://www.sqldev.net/xp/xpsmtp.htm).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Its urgent:Please help me!

Hi All,

1) When I tried to install SQL 2000, i could only install client componets and unable to install server components because

i have windows xp professional edition installed on machine.So, I cannot connect to local server instance.

I am trying to install SQL server 2000 reporting services. But I am stuck in between, Reprting services installer asking

for SQL 2000 instance. But I cannot specfify the instance because I have only installed client componets of SQL 2000.

2) I have SQL 2005 express local instance running on my system. But Reporting services 2000 unable to accept it.

3) How unstall SQL service pack 4. because i want to install sevice pack 3a.

Please help me..

Thank you

Abdul

Why not install SQL2005 Reporting Services? There are components for working with SQL2005 Express.

|||

You will have problems if you are using Beta version or 2003 version SQL Reporting Service and later you decide to use SQL2005 Reporting Service running old version RDL files. They don't work, because the rdl definitions are different.

It is better to use the most up-to-date application. Nonetheless, even if you want to use SQL2005 Reporting Service with the old version reporting databases, you have to upgrade the databases first in Report Configuration.

|||

1) SQL Server 2000 will not be able to install on XP except express edition. Please refer to SQL Server 2000 installation guide.

2) SQL 2000 Reporting Service does not have next generation database driver so that it's not passible to connect to the higher version SQL Server than SQL Server 2000. Only backward compatibility will be implemented. Please read the white paper for SQL Server 2000 Reporting Services.

3) It's not able to down-grade the patch. By the way, the service pack 4 has already included in all the patches of service pack 3a. Please find the technical document on Microsoft Technical Sopport site.

As other person's reply, why don't you try sql server 2005 reporting services?

======================================================================

When you get help, please mark it to let people know you have been helped.

Issues/Problems with SQL MSDE running on Windows XP

Can anyone tell me if there are known problems/issues with running SQL MSDE
on Windows XP? We have a wise install program that installs an Excel
application with msde and it runs fine on Windows 2000 but not on XP. The
install program completes fine but when we go to view the database we find
that the SQL Server instance is there with the msdb, model, and other default
system databases but none of the databases that the install script creates.
When the same installation is ran on 2000 everything works beautifully.
Any help greatly appreciated!
Thanks,
Ang
This is likely an issue with your installation program and not with MSDE.
MSDE works just fine with XP. Contact your application vendor.
-Andrew
"Angela" <Angela@.discussions.microsoft.com> wrote in message
news:E0E98FDB-4923-4CE0-9E1F-D2F8733B4B79@.microsoft.com...
> Can anyone tell me if there are known problems/issues with running SQL
> MSDE
> on Windows XP? We have a wise install program that installs an Excel
> application with msde and it runs fine on Windows 2000 but not on XP. The
> install program completes fine but when we go to view the database we find
> that the SQL Server instance is there with the msdb, model, and other
> default
> system databases but none of the databases that the install script
> creates.
> When the same installation is ran on 2000 everything works beautifully.
> Any help greatly appreciated!
> Thanks,
> Ang

Issues with connecting from .NET to Sybase ASE 12

If anyone out there has been successful in connecting to Sybase ASE 12
from Visual Studio .NET 2003 either in a Windows Forms or Reporting
Services project, can you please help me.
...
In summary, I wish to:
(a) create a Windows Forms application using VB.NET (Visual Studio
.NET 2003 and .NET Framework 1.1) that will connect to Sybase ASE 12.0
to execute stored procedures.
(b) create a SQL Server Reporting Services report using Visual Studio
.NET 2003, .NET Framework 1.1 and SQL Server Reporting Services that
will connect to Sybase ASE 12.0 also via stored procedures.
I have Sybase 12 Client installed on my development machine and am
able to connect to a test server from this machine using SQL
Advantage.
My code for (a) is:
>>
Dim sybaseconn As System.Data.OleDb.OleDbConnection
Dim sybaseconnstring As String = "Provider=Sybase.ASEOLEDBProvider;Server Name=XXXXXX;Initial
Catalog=YYYYYY;User ID=UUUUUU;Password=PPPPPP;"
Try
sybaseconn = New System.Data.OleDb.OleDbConnection(sybaseconnstring)
sybaseconn.Open()
Catch ex As Exception
MsgBox(ex.Message)
Finally
Select Case sybaseconn.State
Case ConnectionState.Broken, ConnectionState.Closed
Case Else
sybaseconn.Close()
sybaseconn.Dispose()
End Select
sybaseconn = Nothing
End Try
>>
When I run this, I receive the following message on the Open() line:
"The 'Sybase.ASEOLEDBProvider' provider is not registered on the local
machine."
and this is the exception:
?ex
{System.InvalidOperationException}
[System.InvalidOperationException]:
{System.InvalidOperationException}
HelpLink: Nothing
InnerException: {System.Data.OleDb.OleDbException}
Message: "The 'Sybase.ASEOLEDBProvider' provider is not registered
on the local machine."
Source: "System.Data"
StackTrace: " at
System.Data.OleDb.OleDbConnection.CreateProviderError(Int32 hr)
at System.Data.OleDb.OleDbConnection.CreateProvider(OleDbConnectionString
constr)
at System.Data.OleDb.OleDbConnection.Open()
at Sybase_Stuff.Form1.Button1_Click(Object sender, EventArgs e) in
C:\Documents and Settings\allchini\My Documents\Visual Studio
Projects\Sybase Stuff\Form1.vb:line 98"
TargetSite: {System.Reflection.RuntimeMethodInfo}
My problem with (b) is as follows:
In my Reporting Services project in Visual Studio .NET 2003 I attempt
to set up a shared data source by selecting Add New Datasource. This
displays the Data Link Properties dialog. On the Provider tab, I
select "Sybase ASE OLE DB Provider". When I press Next or OK, I
receive the following message:
Microsoft Data Link Error
Provider is no longer available. Ensure that the provider is
installed properly.
Can you tell me how to achieve (a) and/ or (b)?
Thanks
Ian AllchinFurther to my earlier posting, I contacted Sybase who were helpful. I
have resolved the first issue. My Sybase installation was corrupted,
so I uninstalled completely. I then installed Sybase ASE 12.5.2 PC
Client which includes the ASE ADO .NET Provider. I have been able to
write a .NET Windows Forms application using this provider in very
much the same way as the SQL Server .NET Provider.
Information about the Sybase ASE .NET Data Provider can be found at:
http://sybooks.sybase.com/onlinebooks/group-adonet/asnetg0110e/adonet
I AM STILL LOOKING FOR HELP ON HOW TO CONNECT TO SYBASE ASE 12 FROM A
SQL SERVER REPORTING SERVICES PROJECT. PLEASE RESPOND IF YOU HAVE ANY
INFORMATION.
Ian Allchin
Alpha Ventures Limited, UK|||I have not done it myself, but this should get you started with using Sybase
ASE 12 in Reporting Services:
* First, you have to make sure the ASE data provider is installed correctly,
so that the report designer in VS.NET and report server inside ASP.NET are
able to load the dlls of the data provider at runtime. Note: there could be
file system permissions issues which prevent ASP.NET from accessing the ASE
data provider dlls. You might want to try to copy the dlls directly into the
report designer and report server installation directories.
* close down all VS.NET sessions before modifying rsReportDesigner.config
* backup the existing rsReportDesigner.config and rsReportServer.config
* Add these entries to rsReportDesigner.config in the Data section:
<Extension Name="Sybase"
Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
... and in the Designer section:
<Extension Name="Sybase"
Type="Microsoft.ReportDesigner.Design.GenericQueryDesigner,Microsoft.Reporti
ngServices.Designer"/>
* Stop the ReportServer Windows service
* Add this entry to rsReportServer.config in the Data section:
<Extension Name="Sybase"
Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
* Restart ReportServer Windows service
* Reset IIS/ASP.NET by running iisreset from the command line
There are several people on this newsgroups who have indicated they are
using Sybase. Not sure if they have tried the managed Sybase provider.
You might also want to read this thread:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=f02812e9-65de-4007-a142-b689522d4c93&sloc=en-us
As indicated in the thread, it should work on the report server, but I'm not
sure about the report designer. It will depend on how the Sybase ASE
provider is implemented internally.
Documentation on the config files:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
Robert M. Bruckner
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0408050554.4a18275d@.posting.google.com...
> Further to my earlier posting, I contacted Sybase who were helpful. I
> have resolved the first issue. My Sybase installation was corrupted,
> so I uninstalled completely. I then installed Sybase ASE 12.5.2 PC
> Client which includes the ASE ADO .NET Provider. I have been able to
> write a .NET Windows Forms application using this provider in very
> much the same way as the SQL Server .NET Provider.
> Information about the Sybase ASE .NET Data Provider can be found at:
> http://sybooks.sybase.com/onlinebooks/group-adonet/asnetg0110e/adonet
> I AM STILL LOOKING FOR HELP ON HOW TO CONNECT TO SYBASE ASE 12 FROM A
> SQL SERVER REPORTING SERVICES PROJECT. PLEASE RESPOND IF YOU HAVE ANY
> INFORMATION.
> Ian Allchin
> Alpha Ventures Limited, UK|||I have used both the ODBC and OLEDB providers. I have not used the dotnet
managed provider. Correct me if I am wrong but it would only use the
provider if you used the generic designer. At runtime it would use it but
during development only the oledb provider?
Bruce L-C
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:%233M8BkweEHA.2028@.tk2msftngp13.phx.gbl...
> I have not done it myself, but this should get you started with using
Sybase
> ASE 12 in Reporting Services:
> * First, you have to make sure the ASE data provider is installed
correctly,
> so that the report designer in VS.NET and report server inside ASP.NET are
> able to load the dlls of the data provider at runtime. Note: there could
be
> file system permissions issues which prevent ASP.NET from accessing the
ASE
> data provider dlls. You might want to try to copy the dlls directly into
the
> report designer and report server installation directories.
> * close down all VS.NET sessions before modifying rsReportDesigner.config
> * backup the existing rsReportDesigner.config and rsReportServer.config
> * Add these entries to rsReportDesigner.config in the Data section:
> <Extension Name="Sybase"
> Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
> ... and in the Designer section:
> <Extension Name="Sybase"
>
Type="Microsoft.ReportDesigner.Design.GenericQueryDesigner,Microsoft.Reporti
> ngServices.Designer"/>
> * Stop the ReportServer Windows service
> * Add this entry to rsReportServer.config in the Data section:
> <Extension Name="Sybase"
> Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
> * Restart ReportServer Windows service
> * Reset IIS/ASP.NET by running iisreset from the command line
> There are several people on this newsgroups who have indicated they are
> using Sybase. Not sure if they have tried the managed Sybase provider.
> You might also want to read this thread:
>
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=f02812e9-65de-4007-a142-b689522d4c93&sloc=en-us
> As indicated in the thread, it should work on the report server, but I'm
not
> sure about the report designer. It will depend on how the Sybase ASE
> provider is implemented internally.
> Documentation on the config files:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
>
> --
> Robert M. Bruckner
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Ian Allchin" <ian.allchin@.talk21.com> wrote in message
> news:1f2dd58b.0408050554.4a18275d@.posting.google.com...
> > Further to my earlier posting, I contacted Sybase who were helpful. I
> > have resolved the first issue. My Sybase installation was corrupted,
> > so I uninstalled completely. I then installed Sybase ASE 12.5.2 PC
> > Client which includes the ASE ADO .NET Provider. I have been able to
> > write a .NET Windows Forms application using this provider in very
> > much the same way as the SQL Server .NET Provider.
> >
> > Information about the Sybase ASE .NET Data Provider can be found at:
> >
> > http://sybooks.sybase.com/onlinebooks/group-adonet/asnetg0110e/adonet
> >
> > I AM STILL LOOKING FOR HELP ON HOW TO CONNECT TO SYBASE ASE 12 FROM A
> > SQL SERVER REPORTING SERVICES PROJECT. PLEASE RESPOND IF YOU HAVE ANY
> > INFORMATION.
> >
> > Ian Allchin
> > Alpha Ventures Limited, UK
>|||If you register any managed data provider in report designer and select it
in the data source dialog, the designer will only enable the generic query
designer. The toggle icon for the visual query designer will be disabled
(because the visual query designer is not capable of working with managed
data providers right now as discussed in the referenced thread below).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:O$iOYRxeEHA.1356@.TK2MSFTNGP09.phx.gbl...
> I have used both the ODBC and OLEDB providers. I have not used the dotnet
> managed provider. Correct me if I am wrong but it would only use the
> provider if you used the generic designer. At runtime it would use it but
> during development only the oledb provider?
> Bruce L-C
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:%233M8BkweEHA.2028@.tk2msftngp13.phx.gbl...
> > I have not done it myself, but this should get you started with using
> Sybase
> > ASE 12 in Reporting Services:
> >
> > * First, you have to make sure the ASE data provider is installed
> correctly,
> > so that the report designer in VS.NET and report server inside ASP.NET
are
> > able to load the dlls of the data provider at runtime. Note: there could
> be
> > file system permissions issues which prevent ASP.NET from accessing the
> ASE
> > data provider dlls. You might want to try to copy the dlls directly into
> the
> > report designer and report server installation directories.
> >
> > * close down all VS.NET sessions before modifying
rsReportDesigner.config
> > * backup the existing rsReportDesigner.config and rsReportServer.config
> >
> > * Add these entries to rsReportDesigner.config in the Data section:
> > <Extension Name="Sybase"
> > Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
> > ... and in the Designer section:
> > <Extension Name="Sybase"
> >
>
Type="Microsoft.ReportDesigner.Design.GenericQueryDesigner,Microsoft.Reporti
> > ngServices.Designer"/>
> >
> > * Stop the ReportServer Windows service
> > * Add this entry to rsReportServer.config in the Data section:
> > <Extension Name="Sybase"
> > Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
> > * Restart ReportServer Windows service
> > * Reset IIS/ASP.NET by running iisreset from the command line
> >
> > There are several people on this newsgroups who have indicated they are
> > using Sybase. Not sure if they have tried the managed Sybase provider.
> >
> > You might also want to read this thread:
> >
>
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=f02812e9-65de-4007-a142-b689522d4c93&sloc=en-us
> > As indicated in the thread, it should work on the report server, but I'm
> not
> > sure about the report designer. It will depend on how the Sybase ASE
> > provider is implemented internally.
> >
> > Documentation on the config files:
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
> >
> >
> > --
> > Robert M. Bruckner
> > Microsoft SQL Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Ian Allchin" <ian.allchin@.talk21.com> wrote in message
> > news:1f2dd58b.0408050554.4a18275d@.posting.google.com...
> > > Further to my earlier posting, I contacted Sybase who were helpful. I
> > > have resolved the first issue. My Sybase installation was corrupted,
> > > so I uninstalled completely. I then installed Sybase ASE 12.5.2 PC
> > > Client which includes the ASE ADO .NET Provider. I have been able to
> > > write a .NET Windows Forms application using this provider in very
> > > much the same way as the SQL Server .NET Provider.
> > >
> > > Information about the Sybase ASE .NET Data Provider can be found at:
> > >
> > > http://sybooks.sybase.com/onlinebooks/group-adonet/asnetg0110e/adonet
> > >
> > > I AM STILL LOOKING FOR HELP ON HOW TO CONNECT TO SYBASE ASE 12 FROM A
> > > SQL SERVER REPORTING SERVICES PROJECT. PLEASE RESPOND IF YOU HAVE ANY
> > > INFORMATION.
> > >
> > > Ian Allchin
> > > Alpha Ventures Limited, UK
> >
> >
>|||First of all thanks to Robert and Bruce for your comments. The DBA
and I have followed the instructions regarding modifying the designer
and server installations, have made some progress on this issue but
are still experiencing some problems ...
On the server, the Sybase .NET provider does not appear in the list of
available connection types within the New Data Source page. We still
just have: Microsoft SQL Server, OLE DB, Oracle and ODBC.
On the client, I have some mixed results:
Sybase IS available as a type in the shared datasource dialog. This
looked encouraging to start with.
I have set up a shared datasource using a connection that I know works
with the ASE .NET provider (tested in a Windows Forms project) and
then tried to used that shared datasource.
When I create a new dataset, with the shared dataset, the only command
type that is available is text (whereas for SQL Server there are 3
options including Stored Procedure).
Within the Generic Query Designer, the Stored Procedure command type
is available.
When I try to create a dataset using a simple text command such as
"SELECT field1 FROM dbo.table1", field1 appears in the field list and
if I press the exclamation mark button field1 is retrieved from the
database OK. However, if I add field1 into a table on the layout tab
and then try to switch to the preview tab, I receive the following
error message:
An error has occurred during report processing.
Operation is not valid due to the current state of the object.
I have also attempted various ways of executing a Sybase stored
procedure with a single integer parameter, using both text and stored
procedure command types, none of which will preview. The most common
message I receive is:
The procedure expected paramater <@.param_name> which was not provided.
Since it is recognising it is a procedure, and picking up the expected
parameter, this also seems promising, but there appear to be mapping
problems.
Ultimately, I want to re-use existing Sybase stored procedures (with
parameters of various data types) within reporting services, so I need
to resolve this.
Any help would be greatly appreciated.
Ian Allchin
Alpha Ventures Limited, UK|||Hi Santiago
Your posting sounds as if you are having some success as you say "it
works". I am also having some issues as described in my most recent
posting on 20 August 2004. For me, reports where the dataset is built
from even text commands and stored procedures with or without
parameters are not working (although if I press the exclamation mark
button, the rows are returned in the grid at the bottom of the generic
query designer). Are you experiencing the same problems or have you
managed to successfully preview or deploy any reports using the Sybase
.NET Provider? If you have, I would be really grateful if you would
describe exactly how you have done it.
If I have any more news, I will post back.
Many thanks
Ian Allchin
Alpha Ventures Limited, UK|||If you can't get the dotnet provider working then I suggest trying the ODBC
or the OLEDB provider. I had an issue with the OLEDB provider, if you setup
multiple OLEDB sources it always wants to use the first one. The Sybase site
had a workaround but it did not work for me (maybe I didn't implement the
workaround correctly). I didn't want to waste anymore time so I went with
the ODBC. The ODBC has worked well and consistantly for me. The only issue I
have had is with stored procedure with parameters. I am currently going
against 11.9.2 backend with a 12.5.2 client. I am upgrading the server to
12.5.2 shortly and hope that the stored procedure problem goes away (I
believe someone that had posted previously had stored procedures working
with ODBC against a 12.5 server). Anyway, I suggest giving the ODBC driver a
chance.
Wait a minute, I just re-read your posting there. You say you get rows
returned. Have you tried the refresh fields button (it looks like the
refresh a web page button in IE). Try that and see if you get your field
list. If you are returning rows then things should be OK.
Bruce L-C
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0408212332.32a40752@.posting.google.com...
> Hi Santiago
> Your posting sounds as if you are having some success as you say "it
> works". I am also having some issues as described in my most recent
> posting on 20 August 2004. For me, reports where the dataset is built
> from even text commands and stored procedures with or without
> parameters are not working (although if I press the exclamation mark
> button, the rows are returned in the grid at the bottom of the generic
> query designer). Are you experiencing the same problems or have you
> managed to successfully preview or deploy any reports using the Sybase
> .NET Provider? If you have, I would be really grateful if you would
> describe exactly how you have done it.
> If I have any more news, I will post back.
> Many thanks
> Ian Allchin
> Alpha Ventures Limited, UK|||Bruce
Thanks for the information regarding ODBC and OLEDB. I have already
tried OLEDB with some success (ie I did manage to call stored
procedures and preview reports), although I had some minor issues with
using 12.5.2 client against 12.0 server. I will revisit this and ODBC
if I cannot resolve the current issues with the ADO .NET route, which
I what Sybase recommended.
My current situation with the ADO .NET provider is that I can connect
to a database and execute a non parameterised text command within the
generic query designer - eg SELECT * FROM tablename. My field list
appears without me pressing refresh fields and if I press the
exclamation mark button I see my rows returned to the grid. However,
when I add fields to a table control on the layout tab and then try to
switch to the preview tab, I receive an error message:
An error has occurred during report processing.
Operation is not valid due to the current state of the object.
I have also tried EXEC storedprocedurename 1 (where 1 is a hard coded
argument) as a text command. Reporting services brings back my
expected field list and returns rows in the grid. However, when I add
fields to a table control on the layout tab and then try to switch to
the preview tab, I receive the same error message.
The reason I am using text commands is that this appears to be the
only option that is fully available and other attempts to deal with
stored procedures have caused different error messages (see my posting
20 August 2004).
Stop Press:
I am able to build and deploy the report. When selecting the report
on the portal, I receive a more detailed error message:
An error has occurred during report processing. (rsProcessingAborted)
An attempt has been made to use a data extension 'Sybase' that is not
registered for this report server. (rsDataExtensionNotFound)
OK, so that may explain the "invalid state of the object".
Does anyone know what we have to do to register it correctly? Also,
should the stored procedure option be available as a command type like
with SQL Server?
Thanks
Ian Allchin
Alpha Ventures Limited UK|||Sorry I can't help anymore with this. I would like to use the dotnet
provider for Sybase as well if it can be made to work.
Bruce L-C
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0408230016.50afd7ac@.posting.google.com...
> Bruce
> Thanks for the information regarding ODBC and OLEDB. I have already
> tried OLEDB with some success (ie I did manage to call stored
> procedures and preview reports), although I had some minor issues with
> using 12.5.2 client against 12.0 server. I will revisit this and ODBC
> if I cannot resolve the current issues with the ADO .NET route, which
> I what Sybase recommended.
> My current situation with the ADO .NET provider is that I can connect
> to a database and execute a non parameterised text command within the
> generic query designer - eg SELECT * FROM tablename. My field list
> appears without me pressing refresh fields and if I press the
> exclamation mark button I see my rows returned to the grid. However,
> when I add fields to a table control on the layout tab and then try to
> switch to the preview tab, I receive an error message:
> An error has occurred during report processing.
> Operation is not valid due to the current state of the object.
> I have also tried EXEC storedprocedurename 1 (where 1 is a hard coded
> argument) as a text command. Reporting services brings back my
> expected field list and returns rows in the grid. However, when I add
> fields to a table control on the layout tab and then try to switch to
> the preview tab, I receive the same error message.
> The reason I am using text commands is that this appears to be the
> only option that is fully available and other attempts to deal with
> stored procedures have caused different error messages (see my posting
> 20 August 2004).
> Stop Press:
> I am able to build and deploy the report. When selecting the report
> on the portal, I receive a more detailed error message:
> An error has occurred during report processing. (rsProcessingAborted)
> An attempt has been made to use a data extension 'Sybase' that is not
> registered for this report server. (rsDataExtensionNotFound)
> OK, so that may explain the "invalid state of the object".
> Does anyone know what we have to do to register it correctly? Also,
> should the stored procedure option be available as a command type like
> with SQL Server?
> Thanks
> Ian Allchin
> Alpha Ventures Limited UK|||I have now had a response from Microsoft technical support. They said
that the Sybase ADO .NET Provider is not a Reporting Services Data
Extension. These are two different things. Sybase would need to
provide a Reporting Services Data Extension.
The Microsoft technical support person recommended trying OLEDB and
only using ODBC if OLEDB was unsuccessful. I intend to follow this
advice, but I will also contact Sybase and ask if they have any plans
to provide a Reporting Services Data Extension and post back.
Ian Allchin
Alpha Ventures Limited, UK|||Interesting. I thought all that was needed was a dotnet data provider.
Didn't know that it was more than that. Thanks for posting back on this.
Bruce L-C
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0408240942.262fd3a1@.posting.google.com...
> I have now had a response from Microsoft technical support. They said
> that the Sybase ADO .NET Provider is not a Reporting Services Data
> Extension. These are two different things. Sybase would need to
> provide a Reporting Services Data Extension.
> The Microsoft technical support person recommended trying OLEDB and
> only using ODBC if OLEDB was unsuccessful. I intend to follow this
> advice, but I will also contact Sybase and ask if they have any plans
> to provide a Reporting Services Data Extension and post back.
> Ian Allchin
> Alpha Ventures Limited, UK|||I have contacted Sybase. They are now considering whether to
implement a Reporting Services Data Extension. A decision is expected
within the next few months and I will post back if I receive any news
on this. In the meantime, I will be going back to try OLEDB and ODBC.
Ian Allchin
Alpha Ventures Limited, UK|||Thanks for the update. If you have any problems with either OLEDB or ODBC
post back here. I have used ODBC extensively with Sybase and am now
migrating to 12.5.2. Others have used OLEDB successfully (and I will be
giving that a try shortly as well).
Thanks again, now I won't waste any time with with the dotnet provider.
Bruce L-C
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0409060212.3f64dffb@.posting.google.com...
>I have contacted Sybase. They are now considering whether to
> implement a Reporting Services Data Extension. A decision is expected
> within the next few months and I will post back if I receive any news
> on this. In the meantime, I will be going back to try OLEDB and ODBC.
> Ian Allchin
> Alpha Ventures Limited, UK

Issues with 2000 SP4 Upgrade.

I have two servers now, which I am getting the same issue. The servers are
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I see
that the server starts but nothing happens......Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>|||Here is the last portion of the log.
....
....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
> >I have two servers now, which I am getting the same issue. The servers are
> > Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> > through copying files and then says "Initializing Server for Upgrade". I
> > see
> > that the server starts but nothing happens......
> >
> >
> >
>
>

Issue with VB6 ADO on vista

Hi,

I am having a vb6 application with sql server 2005 database. It works fine on windows xp. But when i install the application on windows vista I am getting Adodc error "login failed for user sa". Still the forms are populated with data from the database. But the event handlers dosent seem to work after i get this error. Does someone know what caused that adodc error. I have disabled User account control for the vista installation.

Vinith

Hi Vinith.

I'm not sure what Adodc but could you please report the complete error message and the associated error message logged to the server's error log. Please take a look at this webpage for more info: http://msdn2.microsoft.com/en-us/library/ms366351.aspx

Thanks,

Il-Sung.

|||

There was a change in Vista to be more secure in terms of credental propagation. Without more details it is hard to say if this is the case for you.

Try adding

Persist Security Info=True

to your connection string and see if your application is affected by that change.|||

Hi Il Sung and Anton,

I have given persist security info=true and it seems to have solved my problem.

I have kept my connection in an ADOCD connection object. I was using that object when ever i needed database connection. The password was not getting persisted in the connection object. ie before executing if i checked ADODC.connectionstring it didnt contain password information. And that caused the message login failed for user sa.

However this problem occured only when the application runs on vista. With XP it worked fine. Anyway by giving Persist Security Info = true in vista connection string the problem is solved and the password is persisted.

Thanks a lot

Vinith

Issue with VB6 ADO on vista

Hi,

I am having a vb6 application with sql server 2005 database. It works fine on windows xp. But when i install the application on windows vista I am getting Adodc error "login failed for user sa". Still the forms are populated with data from the database. But the event handlers dosent seem to work after i get this error. Does someone know what caused that adodc error. I have disabled User account control for the vista installation.

Vinith

Hi Vinith.

I'm not sure what Adodc but could you please report the complete error message and the associated error message logged to the server's error log. Please take a look at this webpage for more info: http://msdn2.microsoft.com/en-us/library/ms366351.aspx

Thanks,

Il-Sung.

|||

There was a change in Vista to be more secure in terms of credental propagation. Without more details it is hard to say if this is the case for you.

Try adding

Persist Security Info=True

to your connection string and see if your application is affected by that change.|||

Hi Il Sung and Anton,

I have given persist security info=true and it seems to have solved my problem.

I have kept my connection in an ADOCD connection object. I was using that object when ever i needed database connection. The password was not getting persisted in the connection object. ie before executing if i checked ADODC.connectionstring it didnt contain password information. And that caused the message login failed for user sa.

However this problem occured only when the application runs on vista. With XP it worked fine. Anyway by giving Persist Security Info = true in vista connection string the problem is solved and the password is persisted.

Thanks a lot

Vinith

issue with RS 2000, WSS and asp.net 2.0

I am having trouble upgrading a machine. It has Reporting Services(RS) 2000 SP2 and Windows Sharepoint Services (WSS) SP2 running side by side. They are working just fine and have been for quite some time. The problem is I would like to have .net 2.0 installed as well. When I installed it, some things broke.

Specifically, now when I go to http://machinename/reports or http://machinename/reportserver, I get an error page that says "Server Error in '/Reports' Application" and points to the web.config file. The Parser Error Message says "Unrecognized attribute 'processRequestInApplicationTrust' ".

Does anyone know how to get all three running on the same machine? Is this even allowed?

Any help that you can provide would be appreciated. I am stuck.

Dennis

The problem is that Web.Config files are inherited. So your "/reports" which is .net 1.1 is inheriting a .net 2.0 web.config and it doesn't recognize some tags. Only solution I know of is to rearrange the folder hierarchy to not have 1.1 apps under 2.0 apps. I would love a 2.0 version of Report Server... Anyone know if it exists?

-Jesse

issue with linked server connecting to Access

Hi,
I have a linked server setup to connect to an access file from a filer
server. If I am on the server computer logged in using Windows NT
authencation, the connections works. However, if I use a native SQL login
(with sys admin rights) it gave the following error:
Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine can
not
open the file '\\filer-la03p\Mbs\Credit Mortgage
Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
exclusively by another user, or you need permission to view its data.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
The linked server has security mapping as remote user:"admin" with password
null.
I also have noticed that if I connect to the server using EM from my desktop
using NT authencation, the error ocurrs as well. In this case I will say it
is a "double-hopping" issue. But why when using a native SQL account will
have a problem?
From my understanding when using linked server to connect to an access file,
it is using the service account that starts SQL Server. I had setup all
privilages required for the SQL Service account. And as I inicated earlier,
it connects ok if I am at the server using NT authencation to log in.
I rearch online and it seems like I am not the only one who has problems
with linked server for access from other computers. Unfortunately, nobody ha
s
given the resolutions that works for the requester.
Someone please help, we are a microsoft shop and everything is microsoft.
This problem has stopped our development for the business units a great deal
.
Our clients were just bought in to convert a lot of their stuff to SQL
Server. Now they are going to back off!
Thanks if someone can respond quickly.
ChristineA few suggestions:
--Make sure that the Access mdb (and mdw) reside on a file share that
the Windows account has read/write/delete ACLs on for the files and
folders.
--Make sure that the Access mdb is totally unsecured (check the owner
property -- it should NOT say 'unknown').
--Make sure that the login you are using is Admin with an empty string
(''), not null.
--Use filemon (www.sysinternals.com) to check to see if SQLS is
getting access to the files/folders.
FWIW, linked servers to Access are a real PITA. You'd have a much
easier time if you worked it the other way around, linking to SQL
Server from the Access .mdb.
--Mary
On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
C@.discussions.microsoft.com> wrote:

>Hi,
>I have a linked server setup to connect to an access file from a filer
>server. If I am on the server computer logged in using Windows NT
>authencation, the connections works. However, if I use a native SQL login
>(with sys admin rights) it gave the following error:
>Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: The Microsoft Jet database engine ca
nnot
>open the file '\\filer-la03p\Mbs\Credit Mortgage
>Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
>exclusively by another user, or you need permission to view its data.]
>OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>IDBInitialize::Initialize returned 0x80004005: ].
>The linked server has security mapping as remote user:"admin" with password
>null.
>I also have noticed that if I connect to the server using EM from my deskto
p
>using NT authencation, the error ocurrs as well. In this case I will say it
>is a "double-hopping" issue. But why when using a native SQL account will
>have a problem?
>From my understanding when using linked server to connect to an access file
,
>it is using the service account that starts SQL Server. I had setup all
>privilages required for the SQL Service account. And as I inicated earlier,
>it connects ok if I am at the server using NT authencation to log in.
>I rearch online and it seems like I am not the only one who has problems
>with linked server for access from other computers. Unfortunately, nobody h
as
>given the resolutions that works for the requester.
>Someone please help, we are a microsoft shop and everything is microsoft.
>This problem has stopped our development for the business units a great dea
l.
>Our clients were just bought in to convert a lot of their stuff to SQL
>Server. Now they are going to back off!
>Thanks if someone can respond quickly.
>Christine
>|||Mary,
Thanks for replying.
All the checklists you suggested are all there and correct, otherwise it
wouldn't have worked for some cases. It would just not work AT ALL.
I have found the fix for one issue now, but not another:
1. After I added the spn for the server to the AD account that started SQL
Server, I was able to connect from my desktop to the linked server through N
T
authencation.
Before this is only possible if I am at the server.
2. If I connect to SQL Server using SQL accounts, it still doesn't work on
either from the server or my desktop. So I was wondering if I login as 'sa',
what kind of security context that was verified against the file server on
the network? After it gets through the file system then the security check
will use "Admin" to open Access as specified in my linked server security
tab. But what happened before then?
I would assume either way (login as SQL or NT authencation to my SQL Server)
it should use the service account that starts SQL Server, but apparently it
is not the case.
I am really puzzled now...
"Mary Chipman" wrote:

> A few suggestions:
> --Make sure that the Access mdb (and mdw) reside on a file share that
> the Windows account has read/write/delete ACLs on for the files and
> folders.
> --Make sure that the Access mdb is totally unsecured (check the owner
> property -- it should NOT say 'unknown').
> --Make sure that the login you are using is Admin with an empty string
> (''), not null.
> --Use filemon (www.sysinternals.com) to check to see if SQLS is
> getting access to the files/folders.
> FWIW, linked servers to Access are a real PITA. You'd have a much
> easier time if you worked it the other way around, linking to SQL
> Server from the Access .mdb.
> --Mary
> On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
> C@.discussions.microsoft.com> wrote:
>
>|||What did filemon show?
--Mary
On Thu, 14 Oct 2004 16:31:02 -0700, "Christine C"
<ChristineC@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mary,
>Thanks for replying.
>All the checklists you suggested are all there and correct, otherwise it
>wouldn't have worked for some cases. It would just not work AT ALL.
>I have found the fix for one issue now, but not another:
>1. After I added the spn for the server to the AD account that started SQL
>Server, I was able to connect from my desktop to the linked server through
NT
>authencation.
>Before this is only possible if I am at the server.
>2. If I connect to SQL Server using SQL accounts, it still doesn't work on
>either from the server or my desktop. So I was wondering if I login as 'sa'
,
>what kind of security context that was verified against the file server on
>the network? After it gets through the file system then the security check
>will use "Admin" to open Access as specified in my linked server security
>tab. But what happened before then?
>I would assume either way (login as SQL or NT authencation to my SQL Server
)
>it should use the service account that starts SQL Server, but apparently it
>is not the case.
>I am really puzzled now...
>
>"Mary Chipman" wrote:
>

issue with linked server connecting to Access

Hi,
I have a linked server setup to connect to an access file from a filer
server. If I am on the server computer logged in using Windows NT
authencation, the connections works. However, if I use a native SQL login
(with sys admin rights) it gave the following error:
Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine cannot
open the file '\\filer-la03p\Mbs\Credit Mortgage
Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
exclusively by another user, or you need permission to view its data.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
The linked server has security mapping as remote user:"admin" with password
null.
I also have noticed that if I connect to the server using EM from my desktop
using NT authencation, the error ocurrs as well. In this case I will say it
is a "double-hopping" issue. But why when using a native SQL account will
have a problem?
From my understanding when using linked server to connect to an access file,
it is using the service account that starts SQL Server. I had setup all
privilages required for the SQL Service account. And as I inicated earlier,
it connects ok if I am at the server using NT authencation to log in.
I rearch online and it seems like I am not the only one who has problems
with linked server for access from other computers. Unfortunately, nobody has
given the resolutions that works for the requester.
Someone please help, we are a microsoft shop and everything is microsoft.
This problem has stopped our development for the business units a great deal.
Our clients were just bought in to convert a lot of their stuff to SQL
Server. Now they are going to back off!
Thanks if someone can respond quickly.
Christine
A few suggestions:
--Make sure that the Access mdb (and mdw) reside on a file share that
the Windows account has read/write/delete ACLs on for the files and
folders.
--Make sure that the Access mdb is totally unsecured (check the owner
property -- it should NOT say 'unknown').
--Make sure that the login you are using is Admin with an empty string
(''), not null.
--Use filemon (www.sysinternals.com) to check to see if SQLS is
getting access to the files/folders.
FWIW, linked servers to Access are a real PITA. You'd have a much
easier time if you worked it the other way around, linking to SQL
Server from the Access .mdb.
--Mary
On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
C@.discussions.microsoft.com> wrote:

>Hi,
>I have a linked server setup to connect to an access file from a filer
>server. If I am on the server computer logged in using Windows NT
>authencation, the connections works. However, if I use a native SQL login
>(with sys admin rights) it gave the following error:
>Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: The Microsoft Jet database engine cannot
>open the file '\\filer-la03p\Mbs\Credit Mortgage
>Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
>exclusively by another user, or you need permission to view its data.]
>OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>IDBInitialize::Initialize returned 0x80004005: ].
>The linked server has security mapping as remote user:"admin" with password
>null.
>I also have noticed that if I connect to the server using EM from my desktop
>using NT authencation, the error ocurrs as well. In this case I will say it
>is a "double-hopping" issue. But why when using a native SQL account will
>have a problem?
>From my understanding when using linked server to connect to an access file,
>it is using the service account that starts SQL Server. I had setup all
>privilages required for the SQL Service account. And as I inicated earlier,
>it connects ok if I am at the server using NT authencation to log in.
>I rearch online and it seems like I am not the only one who has problems
>with linked server for access from other computers. Unfortunately, nobody has
>given the resolutions that works for the requester.
>Someone please help, we are a microsoft shop and everything is microsoft.
>This problem has stopped our development for the business units a great deal.
>Our clients were just bought in to convert a lot of their stuff to SQL
>Server. Now they are going to back off!
>Thanks if someone can respond quickly.
>Christine
>
|||Mary,
Thanks for replying.
All the checklists you suggested are all there and correct, otherwise it
wouldn't have worked for some cases. It would just not work AT ALL.
I have found the fix for one issue now, but not another:
1. After I added the spn for the server to the AD account that started SQL
Server, I was able to connect from my desktop to the linked server through NT
authencation.
Before this is only possible if I am at the server.
2. If I connect to SQL Server using SQL accounts, it still doesn't work on
either from the server or my desktop. So I was wondering if I login as 'sa',
what kind of security context that was verified against the file server on
the network? After it gets through the file system then the security check
will use "Admin" to open Access as specified in my linked server security
tab. But what happened before then?
I would assume either way (login as SQL or NT authencation to my SQL Server)
it should use the service account that starts SQL Server, but apparently it
is not the case.
I am really puzzled now...
"Mary Chipman" wrote:

> A few suggestions:
> --Make sure that the Access mdb (and mdw) reside on a file share that
> the Windows account has read/write/delete ACLs on for the files and
> folders.
> --Make sure that the Access mdb is totally unsecured (check the owner
> property -- it should NOT say 'unknown').
> --Make sure that the login you are using is Admin with an empty string
> (''), not null.
> --Use filemon (www.sysinternals.com) to check to see if SQLS is
> getting access to the files/folders.
> FWIW, linked servers to Access are a real PITA. You'd have a much
> easier time if you worked it the other way around, linking to SQL
> Server from the Access .mdb.
> --Mary
> On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
> C@.discussions.microsoft.com> wrote:
>
>
|||What did filemon show?
--Mary
On Thu, 14 Oct 2004 16:31:02 -0700, "Christine C"
<ChristineC@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mary,
>Thanks for replying.
>All the checklists you suggested are all there and correct, otherwise it
>wouldn't have worked for some cases. It would just not work AT ALL.
>I have found the fix for one issue now, but not another:
>1. After I added the spn for the server to the AD account that started SQL
>Server, I was able to connect from my desktop to the linked server through NT
>authencation.
>Before this is only possible if I am at the server.
>2. If I connect to SQL Server using SQL accounts, it still doesn't work on
>either from the server or my desktop. So I was wondering if I login as 'sa',
>what kind of security context that was verified against the file server on
>the network? After it gets through the file system then the security check
>will use "Admin" to open Access as specified in my linked server security
>tab. But what happened before then?
>I would assume either way (login as SQL or NT authencation to my SQL Server)
>it should use the service account that starts SQL Server, but apparently it
>is not the case.
>I am really puzzled now...
>
>"Mary Chipman" wrote:

issue with linked server connecting to Access

Hi,
I have a linked server setup to connect to an access file from a filer
server. If I am on the server computer logged in using Windows NT
authencation, the connections works. However, if I use a native SQL login
(with sys admin rights) it gave the following error:
Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine cannot
open the file '\\filer-la03p\Mbs\Credit Mortgage
Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
exclusively by another user, or you need permission to view its data.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
The linked server has security mapping as remote user:"admin" with password
null.
I also have noticed that if I connect to the server using EM from my desktop
using NT authencation, the error ocurrs as well. In this case I will say it
is a "double-hopping" issue. But why when using a native SQL account will
have a problem?
From my understanding when using linked server to connect to an access file,
it is using the service account that starts SQL Server. I had setup all
privilages required for the SQL Service account. And as I inicated earlier,
it connects ok if I am at the server using NT authencation to log in.
I rearch online and it seems like I am not the only one who has problems
with linked server for access from other computers. Unfortunately, nobody has
given the resolutions that works for the requester.
Someone please help, we are a microsoft shop and everything is microsoft.
This problem has stopped our development for the business units a great deal.
Our clients were just bought in to convert a lot of their stuff to SQL
Server. Now they are going to back off!
Thanks if someone can respond quickly.
ChristineA few suggestions:
--Make sure that the Access mdb (and mdw) reside on a file share that
the Windows account has read/write/delete ACLs on for the files and
folders.
--Make sure that the Access mdb is totally unsecured (check the owner
property -- it should NOT say 'unknown').
--Make sure that the login you are using is Admin with an empty string
(''), not null.
--Use filemon (www.sysinternals.com) to check to see if SQLS is
getting access to the files/folders.
FWIW, linked servers to Access are a real PITA. You'd have a much
easier time if you worked it the other way around, linking to SQL
Server from the Access .mdb.
--Mary
On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
C@.discussions.microsoft.com> wrote:
>Hi,
>I have a linked server setup to connect to an access file from a filer
>server. If I am on the server computer logged in using Windows NT
>authencation, the connections works. However, if I use a native SQL login
>(with sys admin rights) it gave the following error:
>Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: The Microsoft Jet database engine cannot
>open the file '\\filer-la03p\Mbs\Credit Mortgage
>Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
>exclusively by another user, or you need permission to view its data.]
>OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>IDBInitialize::Initialize returned 0x80004005: ].
>The linked server has security mapping as remote user:"admin" with password
>null.
>I also have noticed that if I connect to the server using EM from my desktop
>using NT authencation, the error ocurrs as well. In this case I will say it
>is a "double-hopping" issue. But why when using a native SQL account will
>have a problem?
>From my understanding when using linked server to connect to an access file,
>it is using the service account that starts SQL Server. I had setup all
>privilages required for the SQL Service account. And as I inicated earlier,
>it connects ok if I am at the server using NT authencation to log in.
>I rearch online and it seems like I am not the only one who has problems
>with linked server for access from other computers. Unfortunately, nobody has
>given the resolutions that works for the requester.
>Someone please help, we are a microsoft shop and everything is microsoft.
>This problem has stopped our development for the business units a great deal.
>Our clients were just bought in to convert a lot of their stuff to SQL
>Server. Now they are going to back off!
>Thanks if someone can respond quickly.
>Christine
>|||Mary,
Thanks for replying.
All the checklists you suggested are all there and correct, otherwise it
wouldn't have worked for some cases. It would just not work AT ALL.
I have found the fix for one issue now, but not another:
1. After I added the spn for the server to the AD account that started SQL
Server, I was able to connect from my desktop to the linked server through NT
authencation.
Before this is only possible if I am at the server.
2. If I connect to SQL Server using SQL accounts, it still doesn't work on
either from the server or my desktop. So I was wondering if I login as 'sa',
what kind of security context that was verified against the file server on
the network? After it gets through the file system then the security check
will use "Admin" to open Access as specified in my linked server security
tab. But what happened before then?
I would assume either way (login as SQL or NT authencation to my SQL Server)
it should use the service account that starts SQL Server, but apparently it
is not the case.
I am really puzzled now...
"Mary Chipman" wrote:
> A few suggestions:
> --Make sure that the Access mdb (and mdw) reside on a file share that
> the Windows account has read/write/delete ACLs on for the files and
> folders.
> --Make sure that the Access mdb is totally unsecured (check the owner
> property -- it should NOT say 'unknown').
> --Make sure that the login you are using is Admin with an empty string
> (''), not null.
> --Use filemon (www.sysinternals.com) to check to see if SQLS is
> getting access to the files/folders.
> FWIW, linked servers to Access are a real PITA. You'd have a much
> easier time if you worked it the other way around, linking to SQL
> Server from the Access .mdb.
> --Mary
> On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
> C@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >I have a linked server setup to connect to an access file from a filer
> >server. If I am on the server computer logged in using Windows NT
> >authencation, the connections works. However, if I use a native SQL login
> >(with sys admin rights) it gave the following error:
> >
> >Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
> >
> >OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
> >
> >[OLE/DB provider returned message: The Microsoft Jet database engine cannot
> >open the file '\\filer-la03p\Mbs\Credit Mortgage
> >Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
> >exclusively by another user, or you need permission to view its data.]
> >
> >OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
> >IDBInitialize::Initialize returned 0x80004005: ].
> >
> >The linked server has security mapping as remote user:"admin" with password
> >null.
> >I also have noticed that if I connect to the server using EM from my desktop
> >using NT authencation, the error ocurrs as well. In this case I will say it
> >is a "double-hopping" issue. But why when using a native SQL account will
> >have a problem?
> >
> >From my understanding when using linked server to connect to an access file,
> >it is using the service account that starts SQL Server. I had setup all
> >privilages required for the SQL Service account. And as I inicated earlier,
> >it connects ok if I am at the server using NT authencation to log in.
> >
> >I rearch online and it seems like I am not the only one who has problems
> >with linked server for access from other computers. Unfortunately, nobody has
> >given the resolutions that works for the requester.
> >
> >Someone please help, we are a microsoft shop and everything is microsoft.
> >This problem has stopped our development for the business units a great deal.
> >Our clients were just bought in to convert a lot of their stuff to SQL
> >Server. Now they are going to back off!
> >
> >Thanks if someone can respond quickly.
> >
> >Christine
> >
>|||What did filemon show?
--Mary
On Thu, 14 Oct 2004 16:31:02 -0700, "Christine C"
<ChristineC@.discussions.microsoft.com> wrote:
>Mary,
>Thanks for replying.
>All the checklists you suggested are all there and correct, otherwise it
>wouldn't have worked for some cases. It would just not work AT ALL.
>I have found the fix for one issue now, but not another:
>1. After I added the spn for the server to the AD account that started SQL
>Server, I was able to connect from my desktop to the linked server through NT
>authencation.
>Before this is only possible if I am at the server.
>2. If I connect to SQL Server using SQL accounts, it still doesn't work on
>either from the server or my desktop. So I was wondering if I login as 'sa',
>what kind of security context that was verified against the file server on
>the network? After it gets through the file system then the security check
>will use "Admin" to open Access as specified in my linked server security
>tab. But what happened before then?
>I would assume either way (login as SQL or NT authencation to my SQL Server)
>it should use the service account that starts SQL Server, but apparently it
>is not the case.
>I am really puzzled now...
>
>"Mary Chipman" wrote:
>> A few suggestions:
>> --Make sure that the Access mdb (and mdw) reside on a file share that
>> the Windows account has read/write/delete ACLs on for the files and
>> folders.
>> --Make sure that the Access mdb is totally unsecured (check the owner
>> property -- it should NOT say 'unknown').
>> --Make sure that the login you are using is Admin with an empty string
>> (''), not null.
>> --Use filemon (www.sysinternals.com) to check to see if SQLS is
>> getting access to the files/folders.
>> FWIW, linked servers to Access are a real PITA. You'd have a much
>> easier time if you worked it the other way around, linking to SQL
>> Server from the Access .mdb.
>> --Mary
>> On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
>> C@.discussions.microsoft.com> wrote:
>> >Hi,
>> >
>> >I have a linked server setup to connect to an access file from a filer
>> >server. If I am on the server computer logged in using Windows NT
>> >authencation, the connections works. However, if I use a native SQL login
>> >(with sys admin rights) it gave the following error:
>> >
>> >Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
>> >
>> >OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>> >
>> >[OLE/DB provider returned message: The Microsoft Jet database engine cannot
>> >open the file '\\filer-la03p\Mbs\Credit Mortgage
>> >Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
>> >exclusively by another user, or you need permission to view its data.]
>> >
>> >OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>> >IDBInitialize::Initialize returned 0x80004005: ].
>> >
>> >The linked server has security mapping as remote user:"admin" with password
>> >null.
>> >I also have noticed that if I connect to the server using EM from my desktop
>> >using NT authencation, the error ocurrs as well. In this case I will say it
>> >is a "double-hopping" issue. But why when using a native SQL account will
>> >have a problem?
>> >
>> >From my understanding when using linked server to connect to an access file,
>> >it is using the service account that starts SQL Server. I had setup all
>> >privilages required for the SQL Service account. And as I inicated earlier,
>> >it connects ok if I am at the server using NT authencation to log in.
>> >
>> >I rearch online and it seems like I am not the only one who has problems
>> >with linked server for access from other computers. Unfortunately, nobody has
>> >given the resolutions that works for the requester.
>> >
>> >Someone please help, we are a microsoft shop and everything is microsoft.
>> >This problem has stopped our development for the business units a great deal.
>> >Our clients were just bought in to convert a lot of their stuff to SQL
>> >Server. Now they are going to back off!
>> >
>> >Thanks if someone can respond quickly.
>> >
>> >Christine
>> >
>>

Issue when setting up the XML connection to Analysis Services on W

I am using XML For Analysis in a Windows 2000 server in order to access my
OLAP cubes and I'm getting the following error when using the Sample VB app
that comes with the package:
Run-time error '500'
<FaultCode>1198808394</FaultCode>
<Description></Description>
Can some one help me?You may want to ask this question in the analysis services group.
Best regards
Michael
"Carlos La Rovere" <Carlos La Rovere@.discussions.microsoft.com> wrote in
message news:F602ABDF-A418-49A5-B6A3-CA36C3DBE102@.microsoft.com...
>I am using XML For Analysis in a Windows 2000 server in order to access my
> OLAP cubes and I'm getting the following error when using the Sample VB
> app
> that comes with the package:
> Run-time error '500'
> <FaultCode>1198808394</FaultCode>
> <Description></Description>
> Can some one help me?

Issue to install Reporting Services

I installed SQL Server 2005 Express with Reporting Service on Windows Server 2003 Standard on a server called psmart01. I type the URL of reporting services: http://psmart01/reportserver$SQLEXPRESS and I get only:

psmart01/ReportServer$SQLExpress - /

Microsoft SQL Server Reporting Services Version 9.00.2047.00

I have gone through the Troubleshoot a Reporting Services Installation Problem of MSDN but there is not such issue.

I wonder if reporting service database is not created properly. When I restart the SQL Server Reporting Services I see in the eventvwr: Starting up database 'ReportServer$SQLExpressTempDB'. Why TempDB ?

Can someone help ?

I think you are seeing the Report Server v-dir listing, and your catalog is empty. This is expected. What do you see when you navigate to this URL:

http://psmart01/Reports$SQLExpress

Issue publishing reports under Win2k3

I'm trying to publish some reports using the RS tool under Windows
Server 2003 SBS.
It works fine under Win XP but using SBS I get the messages
"The operation you are attempting requires a secure connection
(HTTPS)."
Any ideas?
Cheers
Chris.The rs script uses rs.CreateReport
and this is where the exception occurs.|||On 18 Jun, 18:54, theinvisibleGhost <theinvisibleGh...@.yahoo.com>
wrote:
> The rs script uses rs.CreateReport
> and this is where the exception occurs.
I found a similar message here:
http://groups.google.co.uk/group/microsoft.public.crm/browse_thread/thread/4b3872a882e9bcd7/bdba3dfc3d002231?lnk=st&q=Microsoft.ReportingServices.Diagnostics.Utilities.SecureConnectionRequiredException&rnum=1&hl=en#bdba3dfc3d002231
It didn't resolve my issue but I found that my virtual directorys were
corrupted in someway.
I deleted them and then recreated them and my issue was resolved.

Issue in browsing msxisapi.dll please help

Hi all, I installed several times the xml analysis provider but I am
having severe issues in having it working on a Windows 2003 server
machine. I followed all the described steps including adding and
enabling a Web service extension for that dll. Also read and execute
permissions are setted up; all seems exactly the same to what I did
other times...but I am unable to browse it from that machine.

Any help is sooo appreciated,

Thanks and regards

ElenaWhat type of error are you getting exactly?

Are you able to browse it from other machines?

<ELEMA.LO@.terra.es> wrote in message
news:1118095685.145011.186500@.z14g2000cwz.googlegr oups.com...
> Hi all, I installed several times the xml analysis provider but I am
> having severe issues in having it working on a Windows 2003 server
> machine. I followed all the described steps including adding and
> enabling a Web service extension for that dll. Also read and execute
> permissions are setted up; all seems exactly the same to what I did
> other times...but I am unable to browse it from that machine.
> Any help is sooo appreciated,
> Thanks and regards
> Elena|||There are several discussions of issues with this DLL:

http://groups-beta.google.com/group...lr=&sa=N&tab=wg

If this doesn't help, you should post some more information - which
version/servicepack of MSSQL, what error you get, which steps you
followed etc.

Simon|||Hi all, thanks for the reply. I don't get any message...just it
stalls...please help it is very urgent !

Thanks and regards

Elena|||(ELEMA.LO@.terra.es) writes:
> Hi all, thanks for the reply. I don't get any message...just it
> stalls...please help it is very urgent !

If you want to rely on newsgroups, microsoft.public.sqlserver.xml
may be your best bet.

But if it's very urgent, you should probably consider open a case with
Microsoft.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Issue

Anyone know this answer?
[New].[Configuration:]
O/S: Windows XP Service Pack2 on a machine named MERCURY
SQL Server Developer's Edition SP4
[Old].[Configuration]
O/S: Windows 2000 on a machine called PIONEER
SQL Server Developer's Edition SP4
[Problem].[ Description:]
1. Created 25 clean, functional DTS packages on PIONEER. On that machine,
any task in DTS designer which allows the user to select a single table name
from a drop-down list (Combo Box) (such as Bulk Insert Tasks), have Square
Delimited Indentifiers. For example:
[DBO].[TABLENAME1]
[DBO].[TABLENAME1]
[DBO].[TABLENAME1]
[DBO].[TABLENAME1]
2. Packages were then moved to a new computer, running the configuration
shown at the top.On that computer, the ODBC Administrator has default
settings for each new connection. These settings include the check box for
ANSI Quoted Identifiers which are ON (Checked). That is the same default as
Windows 2000 ODBC. We unchecked the box for every new connection.
3. When the packages from the PIONEER machine with square bracketed
identifiers in the Drop down lists were opened then square brackets
disappeared from the first display item as soon as you click the button of
the drop-down list. The drop down functionality apparently dropped the list
items from the old package, required the database with the same name on
PIONEER, repopulated the list, but this time, EVERY SINGLE IDENTIFIER WAS
DELIMITED WITH DOUBLE-QUOTES, and, worst of all, the correct name was
replaced with the first alphabetical name.The new list looked like this:
"DBO"."TABLENAME1"
"DBO"."TABLENAME1"
"DBO"."TABLENAME1"
"DBO"."TABLENAME1"
Doesn't that JUST BLOW!
Also, it appears that no connections can recognize the objects anymore.
Robert

> Anyone know this answer?
> [New].[Configuration:]
> O/S: Windows XP Service Pack2 on a machine named MERCURY
> SQL Server Developer's Edition SP4
> [Old].[Configuration]
> O/S: Windows 2000 on a machine called PIONEER
> SQL Server Developer's Edition SP4
> [Problem].[ Description:]
> 1. Created 25 clean, functional DTS packages on PIONEER. On that machine,
> any task in DTS designer which allows the user to select a single table
> name from a drop-down list (Combo Box) (such as Bulk Insert Tasks), have
> Square Delimited Indentifiers. For example:
> [DBO].[TABLENAME1]
> [DBO].[TABLENAME1]
> [DBO].[TABLENAME1]
> [DBO].[TABLENAME1]
> 2. Packages were then moved to a new computer, running the configuration
> shown at the top.On that computer, the ODBC Administrator has default
> settings for each new connection. These settings include the check box for
> ANSI Quoted Identifiers which are ON (Checked). That is the same default
> as Windows 2000 ODBC. We unchecked the box for every new connection.
> 3. When the packages from the PIONEER machine with square bracketed
> identifiers in the Drop down lists were opened then square brackets
> disappeared from the first display item as soon as you click the button of
> the drop-down list. The drop down functionality apparently dropped the
> list items from the old package, required the database with the same name
> on PIONEER, repopulated the list, but this time, EVERY SINGLE IDENTIFIER
> WAS DELIMITED WITH DOUBLE-QUOTES, and, worst of all, the correct name was
> replaced with the first alphabetical name.
>
>
>

ISQL query fails after reboot

Good morning we are having a wierd issue with our Windows 2003 server and SQ
L
2000 sp4 server. From the client side we use isql queries. When we reboot
the server the isql queries that are larger then 512 bytes will fail from
both the client or from the sql server itself smaller ones will work. Query
analyzer works perfectly. The strange part is if we run any query in either
query analyzer or using isql then restart the services everything works. We
also have another server which appears to be identical and everything works
with no issues. If anyone can point me in the right direction to
troubleshoot this issue it would be greatly appreciated.
Richard TracyHave you tried using OSQL instead of ISQL?
In terms of why you are having problems, that's hard to say
without knowing what error message you receive when running
the queries that fail. As a guess, it sounds like you could
be running into issues related to ISQL and the packet size.
Try using the -a switch and increase the default packet
size.
-Sue
On Wed, 12 Apr 2006 07:50:02 -0700, Richard Tracy
<RichardTracy@.discussions.microsoft.com> wrote:

>Good morning we are having a wierd issue with our Windows 2003 server and S
QL
>2000 sp4 server. From the client side we use isql queries. When we reboot
>the server the isql queries that are larger then 512 bytes will fail from
>both the client or from the sql server itself smaller ones will work. Quer
y
>analyzer works perfectly. The strange part is if we run any query in eithe
r
>query analyzer or using isql then restart the services everything works. W
e
>also have another server which appears to be identical and everything works
>with no issues. If anyone can point me in the right direction to
>troubleshoot this issue it would be greatly appreciated.
>Richard Tracy|||We have tried using the -a with no success the error we get is a network
error even if we run it on the localhost. We have also uninstalled sql
server and tried it on a plain vanilla sql server with no success. Any idea
s
of how to troubleshoot this would be greatly appreciated
Thank you
"Sue Hoegemeier" wrote:

> Have you tried using OSQL instead of ISQL?
> In terms of why you are having problems, that's hard to say
> without knowing what error message you receive when running
> the queries that fail. As a guess, it sounds like you could
> be running into issues related to ISQL and the packet size.
> Try using the -a switch and increase the default packet
> size.
> -Sue
> On Wed, 12 Apr 2006 07:50:02 -0700, Richard Tracy
> <RichardTracy@.discussions.microsoft.com> wrote:
>
>|||You really have to look at the exact full error messages and
the error number. You can try googling on those or try
posting with the full information. Connectivity issues are
generally difficult to troubleshoot via newsgroups. If you
want to do that, you need to post a lot of details, full
error messages, configurations, exact steps to reproduce,
etc. Even then, it can be difficult via newsgroups.
-Sue
On Thu, 13 Apr 2006 23:18:02 -0700, Richard Tracy
<RichardTracy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>We have tried using the -a with no success the error we get is a network
>error even if we run it on the localhost. We have also uninstalled sql
>server and tried it on a plain vanilla sql server with no success. Any ide
as
>of how to troubleshoot this would be greatly appreciated
>Thank you
>"Sue Hoegemeier" wrote:
>|||Thank you for your help Sue. We found what the issue was, we found it was
being caused by an application called NCS (Native Command Substitution. It
is installed with lightspeed which was created by imceda software which has
been bought by quest software. We removed this software and it has worked
without an issue. Again thak you very much for your help
"Sue Hoegemeier" wrote:

> You really have to look at the exact full error messages and
> the error number. You can try googling on those or try
> posting with the full information. Connectivity issues are
> generally difficult to troubleshoot via newsgroups. If you
> want to do that, you need to post a lot of details, full
> error messages, configurations, exact steps to reproduce,
> etc. Even then, it can be difficult via newsgroups.
> -Sue
> On Thu, 13 Apr 2006 23:18:02 -0700, Richard Tracy
> <RichardTracy@.discussions.microsoft.com> wrote:
>
>|||That's interesting one ...thanks for posting back.
-Sue
On Sun, 16 Apr 2006 14:01:02 -0700, Richard Tracy
<RichardTracy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thank you for your help Sue. We found what the issue was, we found it was
>being caused by an application called NCS (Native Command Substitution. It
>is installed with lightspeed which was created by imceda software which has
>been bought by quest software. We removed this software and it has worked
>without an issue. Again thak you very much for your help
>"Sue Hoegemeier" wrote:
>