SQL Adding a User account: machine

Showing posts with label machine. Show all posts

Tuesday, March 20, 2012

Advantages of using SQL Server vs Oracle for Small to Mdium Size N

We currently have 8 locations around the world with Access database on a
local machine in each location. Some of these locations are in remote areas
where network or internet connectivity is not available all the time. We are
looking to discontinue the Access database and migrate to either MS SQL
Server or Oracle.
We want to have local databases in each location and when ever there is
connectivity we want to be able to update the main database in the US. What
are the advantages of using SQL Server for this purpose and how can this be
done?
ThanksSQL Server 2000 Replication Overview
http://www.microsoft.com/sql/evaluation/features/replication.asp
AMB
"ADW" wrote:
> We currently have 8 locations around the world with Access database on a
> local machine in each location. Some of these locations are in remote areas
> where network or internet connectivity is not available all the time. We are
> looking to discontinue the Access database and migrate to either MS SQL
> Server or Oracle.
> We want to have local databases in each location and when ever there is
> connectivity we want to be able to update the main database in the US. What
> are the advantages of using SQL Server for this purpose and how can this be
> done?
> Thanks
>|||Thanks for the info, but what are the advantages of using MS SQL over Oracle?
ADW
"Alejandro Mesa" wrote:
> SQL Server 2000 Replication Overview
> http://www.microsoft.com/sql/evaluation/features/replication.asp
>
> AMB
> "ADW" wrote:
> > We currently have 8 locations around the world with Access database on a
> > local machine in each location. Some of these locations are in remote areas
> > where network or internet connectivity is not available all the time. We are
> > looking to discontinue the Access database and migrate to either MS SQL
> > Server or Oracle.
> >
> > We want to have local databases in each location and when ever there is
> > connectivity we want to be able to update the main database in the US. What
> > are the advantages of using SQL Server for this purpose and how can this be
> > done?
> >
> > Thanks
> >|||SQL Server is easier to admin if you don't plan to hire a dedicated
experienced Oracle DBA.
Its software license is also cheaper, dual core CPUs count as 1 CPU license.
SQL 2005 is just around the corner in November, you can check the June
preview.
http://www.microsoft.com/sql/2005/productinfo/ctp.mspx
http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx

Advantages of using SQL Server vs Oracle for Small to Mdium Size N

Monday, March 19, 2012

Advantage comparison on Attach & Restore database

If I were to copy a database from one machine to another machine, I can
use:
- Backup & restore
- Detach & attach
Not to mention on those daily backup or availability of the database.
Just consider copy one database to another machine.
Does anyone know what's the advantage of each method mention above?
I used to Detach & Attach cause it's fast. Backup & restore database
would takes long time.
Other than that, anyone know is there any side effect or drawback of
the methods mentiond above?
Peter CCHHi,
Detach and attach must be faster but it require downtime; where as Backup
and restore do not need any downtime.
Thanks
Hari
SQL Server MVP
"Peter CCH" <petercch.wodoy@.gmail.com> wrote in message
news:1156564154.830161.207440@.i3g2000cwc.googlegroups.com...
> If I were to copy a database from one machine to another machine, I can
> use:
> - Backup & restore
> - Detach & attach
> Not to mention on those daily backup or availability of the database.
> Just consider copy one database to another machine.
> Does anyone know what's the advantage of each method mention above?
> I used to Detach & Attach cause it's fast. Backup & restore database
> would takes long time.
> Other than that, anyone know is there any side effect or drawback of
> the methods mentiond above?
>
> Peter CCH
>|||Other than that, nothing else?
Then it would be fine for me cause it's a developer machine, not
production server.
We always need to copy database from machine to machine.
Thanks.
Hari Prasad wrote:
> Hi,
> Detach and attach must be faster but it require downtime; where as Backup
> and restore do not need any downtime.
> Thanks
> Hari
> SQL Server MVP
> "Peter CCH" <petercch.wodoy@.gmail.com> wrote in message
> news:1156564154.830161.207440@.i3g2000cwc.googlegroups.com...
> > If I were to copy a database from one machine to another machine, I can
> > use:
> > - Backup & restore
> > - Detach & attach
> >
> > Not to mention on those daily backup or availability of the database.
> > Just consider copy one database to another machine.
> >
> > Does anyone know what's the advantage of each method mention above?
> > I used to Detach & Attach cause it's fast. Backup & restore database
> > would takes long time.
> >
> > Other than that, anyone know is there any side effect or drawback of
> > the methods mentiond above?
> >
> >
> >
> > Peter CCH
> >|||Backup and Restore may also 'defrag' the tables and indexes.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Peter CCH" <petercch.wodoy@.gmail.com> wrote in message
news:1156564154.830161.207440@.i3g2000cwc.googlegroups.com...
> If I were to copy a database from one machine to another machine, I can
> use:
> - Backup & restore
> - Detach & attach
> Not to mention on those daily backup or availability of the database.
> Just consider copy one database to another machine.
> Does anyone know what's the advantage of each method mention above?
> I used to Detach & Attach cause it's fast. Backup & restore database
> would takes long time.
> Other than that, anyone know is there any side effect or drawback of
> the methods mentiond above?
>
> Peter CCH
>|||> Backup and Restore may also 'defrag' the tables and indexes.
No table/index defragmentation takes place during the restore; the restored
database is exactly like the original. However, a restore can effectively
defrag database files at the file system level when the files are recreated.
Such fragmentation usually occurs only when one relies on automatic growth.
With the exception of a version upgrade, few changes are made during the
restore. The only changes that come to mind are to the file paths and
database owner.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:%23gDCwVMyGHA.4336@.TK2MSFTNGP06.phx.gbl...
> Backup and Restore may also 'defrag' the tables and indexes.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Peter CCH" <petercch.wodoy@.gmail.com> wrote in message
> news:1156564154.830161.207440@.i3g2000cwc.googlegroups.com...
>> If I were to copy a database from one machine to another machine, I can
>> use:
>> - Backup & restore
>> - Detach & attach
>> Not to mention on those daily backup or availability of the database.
>> Just consider copy one database to another machine.
>> Does anyone know what's the advantage of each method mention above?
>> I used to Detach & Attach cause it's fast. Backup & restore database
>> would takes long time.
>> Other than that, anyone know is there any side effect or drawback of
>> the methods mentiond above?
>>
>> Peter CCH
>|||Thanks Dan,
I meant to say 'File' defrag, and my evil twin wrote in the other thought...
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:OhkIAJPyGHA.4912@.TK2MSFTNGP03.phx.gbl...
>> Backup and Restore may also 'defrag' the tables and indexes.
> No table/index defragmentation takes place during the restore; the
> restored database is exactly like the original. However, a restore can
> effectively defrag database files at the file system level when the files
> are recreated. Such fragmentation usually occurs only when one relies on
> automatic growth.
> With the exception of a version upgrade, few changes are made during the
> restore. The only changes that come to mind are to the file paths and
> database owner.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:%23gDCwVMyGHA.4336@.TK2MSFTNGP06.phx.gbl...
>> Backup and Restore may also 'defrag' the tables and indexes.
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>> "Peter CCH" <petercch.wodoy@.gmail.com> wrote in message
>> news:1156564154.830161.207440@.i3g2000cwc.googlegroups.com...
>> If I were to copy a database from one machine to another machine, I can
>> use:
>> - Backup & restore
>> - Detach & attach
>> Not to mention on those daily backup or availability of the database.
>> Just consider copy one database to another machine.
>> Does anyone know what's the advantage of each method mention above?
>> I used to Detach & Attach cause it's fast. Backup & restore database
>> would takes long time.
>> Other than that, anyone know is there any side effect or drawback of
>> the methods mentiond above?
>>
>> Peter CCH
>>
>

Advantage comparison on Attach & Restore database

Tuesday, March 6, 2012

ADOMD.Connection error

We are getting this error: 'ADODB.Connection: Provider is not specified
and there is no designated default provider' on a 64 bit machine with
both Sql 2K 32bit and Sql 2K5 64bit installed. It happens from Vbscript
that backs up our Olap databases. The script (below) works fine on a 32
bit server with Sql 2K installed.
Function QueryDatabaseList()
Dim oConnectionServer
Dim oRS
Dim arrDatabase
Set oConnectionServer =CreateObject("ADODB.Connection")
oConnectionServer.ConnectionString = "Data Source=" & ServerName &
"; Provider=MSOLAP.2"
oConnectionServer.Open
Set oRS = oConnectionServer.OpenSchema(adSchemaCatalogs)
arrDatabase = oRs.GetRows
oConnectionServer.Close
Set oConnectionServer = Nothing
QueryDatabaseList = arrDatabase
End Function
I am pretty sure the problem has to do with the fact that the right
driver can not be found. But which one?
Thanks in advance,
Koni.
MSOLAP.2 is for AS2000
so try MSOLAP.3 for SSAS2005
"Koni" <kkogan@.haiint.com> wrote in message
news:uAgqmPoPHHA.1152@.TK2MSFTNGP03.phx.gbl...
> We are getting this error: 'ADODB.Connection: Provider is not specified
> and there is no designated default provider' on a 64 bit machine with both
> Sql 2K 32bit and Sql 2K5 64bit installed. It happens from Vbscript that
> backs up our Olap databases. The script (below) works fine on a 32 bit
> server with Sql 2K installed.
> Function QueryDatabaseList()
> Dim oConnectionServer
> Dim oRS
> Dim arrDatabase
>
> Set oConnectionServer =CreateObject("ADODB.Connection")
> oConnectionServer.ConnectionString = "Data Source=" & ServerName & ";
> Provider=MSOLAP.2"
> oConnectionServer.Open
> Set oRS = oConnectionServer.OpenSchema(adSchemaCatalogs)
> arrDatabase = oRs.GetRows
> oConnectionServer.Close
> Set oConnectionServer = Nothing
> QueryDatabaseList = arrDatabase
> End Function
> I am pretty sure the problem has to do with the fact that the right driver
> can not be found. But which one?
>
> Thanks in advance,
> Koni.

ADOMD.Connection error

We are getting this error: 'ADODB.Connection: Provider is not specified
and there is no designated default provider' on a 64 bit machine with
both Sql 2K 32bit and Sql 2K5 64bit installed. It happens from Vbscript
that backs up our Olap databases. The script (below) works fine on a 32
bit server with Sql 2K installed.
Function QueryDatabaseList()
Dim oConnectionServer
Dim oRS
Dim arrDatabase
Set oConnectionServer =CreateObject("ADODB.Connection")
oConnectionServer.ConnectionString = "Data Source=" & ServerName &
"; Provider=MSOLAP.2"
oConnectionServer.Open
Set oRS = oConnectionServer.OpenSchema(adSchemaCatalogs)
arrDatabase = oRs.GetRows
oConnectionServer.Close
Set oConnectionServer = Nothing
QueryDatabaseList = arrDatabase
End Function
I am pretty sure the problem has to do with the fact that the right
driver can not be found. But which one?
Thanks in advance,
Koni.MSOLAP.2 is for AS2000
so try MSOLAP.3 for SSAS2005
"Koni" <kkogan@.haiint.com> wrote in message
news:uAgqmPoPHHA.1152@.TK2MSFTNGP03.phx.gbl...
> We are getting this error: 'ADODB.Connection: Provider is not specified
> and there is no designated default provider' on a 64 bit machine with both
> Sql 2K 32bit and Sql 2K5 64bit installed. It happens from Vbscript that
> backs up our Olap databases. The script (below) works fine on a 32 bit
> server with Sql 2K installed.
> Function QueryDatabaseList()
> Dim oConnectionServer
> Dim oRS
> Dim arrDatabase
>
> Set oConnectionServer =CreateObject("ADODB.Connection")
> oConnectionServer.ConnectionString = "Data Source=" & ServerName & ";
> Provider=MSOLAP.2"
> oConnectionServer.Open
> Set oRS = oConnectionServer.OpenSchema(adSchemaCatalogs)
> arrDatabase = oRs.GetRows
> oConnectionServer.Close
> Set oConnectionServer = Nothing
> QueryDatabaseList = arrDatabase
> End Function
> I am pretty sure the problem has to do with the fact that the right driver
> can not be found. But which one?
>
> Thanks in advance,
> Koni.

Saturday, February 25, 2012

ADODB Vesion 7.0.3300.0 in vb.net

Hi,

I have developed an application in vb.net 2005 Standard Edition and is running fine in my local machine. The executed version of the same application i tried to run in other machine and getting an error as follows :-

" Unable to install application. The application requires the assembly ADODB Version 7.0.3300.0 be installed in the global assembly cache (GAC) first "

Can you somebody help me to solve this problem.

Thanks

Saju John

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=174626&SiteID=1

HTH

|||I was able to solve this without resorting to the bootstrap loader by adding a reference to the adodb resource in my Studio project, then selecting this reference, and changing it's 'Copy Local' property to true.

ADODB Vesion 7.0.3300.0 in vb.net

Hi,

" Unable to install application. The application requires the assembly ADODB Version 7.0.3300.0 be installed in the global assembly cache (GAC) first "

Can you somebody help me to solve this problem.

Thanks

Saju John

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=174626&SiteID=1

HTH

ADODB Vesion 7.0.3300.0 in vb.net

Hi,

" Unable to install application. The application requires the assembly ADODB Version 7.0.3300.0 be installed in the global assembly cache (GAC) first "

Can you somebody help me to solve this problem.

Thanks

Saju John

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=174626&SiteID=1

HTH

adodb connections to a linked server

Hello,
I'd like to create an ado connection to my linked server called Prob_Schd on
a machine called pccn-nt.
When I use the code below I recieve an error of the type ' Invalid
connection string attribute'. Would someone show me how to create an ado
connection to a linked server?
Thanks,
Chieko
dim oConn, strConn
Set oConn = Server.CreateObject("ADODB.Connection")
strConn = "provider=SQLOLEDB; Datasource=Prob_Schd; Initial Catalog=null
trusted_Connection=yes "
oConn.Open strConn
set GetDataConnection = oConnADO doesn't know anything about SQL Server's linked servers. You could
connect locally, and then execute queries like adoConnObject.Execute("SELECT
* FROM Prob_Schd.pubs.dbo.authors") or, you could make an OLEDB connection
directly to the linked server.
The specific error you are getting is because the "Datasource" attribute
you've used should have a space, "Data Source"... but I'm pretty sure ADO
will still be unable to find that server unless it is in the hosts file on
the machine (in other words, it doesn't care if that's a linked server in
SQL Server).
"Chieko Kuroda" <ckuroda@.med.unc.edu> wrote in message
news:O2OVMHuzDHA.3520@.tk2msftngp13.phx.gbl...

quote:

> Hello,
> I'd like to create an ado connection to my linked server called Prob_Schd

quote:

> a machine called pccn-nt.
> When I use the code below I recieve an error of the type ' Invalid
> connection string attribute'. Would someone show me how to create an ado
> connection to a linked server?
> Thanks,
> Chieko
>
> dim oConn, strConn
> Set oConn = Server.CreateObject("ADODB.Connection")
> strConn = "provider=SQLOLEDB; Datasource=Prob_Schd; Initial

Catalog=null

quote:

> trusted_Connection=yes "
> oConn.Open strConn
> set GetDataConnection = oConn
>

ADO.NET SP throws ArgumentException after migrating to SQL 2005 Standard - UPDATE 2 - FIXED

I just migrated a database from SQL 2000 Developer Edition on W2k Server to a production machine running SQL 2005 Standard on W2k3 Server Standard. A Web Service was also migrated from .NET 1.1 on the development machine to .NET 2.0 on the production machine.

Since the migration, a stored procedure that worked on SQL 2000/.NET 1.1 now throws a System.ArgumentException: "No mapping exists from object type System.RuntimeType to a known managed proider native type."

This occurs with a date value - the stored procedure is filled from XML data the Web Service receives from the client program by a generic subroutine that recognizes the applicable table names and primary key column names, selecting the appropriate stored procedure to use, but may or may not have data to update for each field. I have tried explicitly setting the SQLDBType for the parameter as the parametercollection is filled, but still get the ArgumentException. I also tried changing the parameter type to varchar(20), and having the stored procedure convert it to datetime, but still got the exception.

I know the ultimate solution will probably be to build the data Web Service within SQL 2005, but what can I do to get this working until I have time for that conversion?

Thanks for any help.

Darrell Escola

UPDATE - I was able to use the stored procedures to manually update the database using data that should have passed through the web service, so the problem is within the web service on .NET 2.0 - I think 2.0 is much stricter on data types than was 1.1. The SPs create dynamic SQL that is then executed - I know this is not the best security, hence my eventual interest in creating an end-point within SQL 2005 to handle the data in a more secure manner.

Darrell

|||

I finally got the web service to update through the stored procedure. I was able to access the stored procedure by specifically casting the data types for each parameter using a subroutine similar to that shown below, but the web service was still throwing an exception on the output value type, which I use to get the actual primary key value for the new record, so the off-line client can properly map its dependent records to the proper key value before inserting those dependent records:

Dim newID As SQLTypes.SQLInt32

I added a subroutine to determine the data type for each column used in the update:

Private Sub AddSPParameter(ByRef cmd as SQLClient.SQLCommand, ByVal paramName as String, ByVal fieldValue as Object)

If paramName = "<stringColName1>" Or paramName = "<stringColName...>" Then

cmd.Parameters.AddWithValue(Ctype(Cstr(fieldValue), SQLTypes.SQLString).DbType = DbType.String

ElseIf paramName = "<otherTypeColName1>" Or paramName.IndexOf("...") > 0 Or paramName.EndsWith("...") Then

cmd.Parameters.AddWithValue(Ctype(Cstr(fieldValue), SQLTypes.SQL<otherType>).DbType = DbType.<otherType>

ElseIf ...

End If

This subroutine determines the column data type by matches on the column name, and then explicitly casting the parameter value to the applicable database data type.

I also had to explicitly cast the Return Value:

cmd.Parameters.AddWithValue("@.ReturnValue", Ctype(0, SQLTypes.SQLInt32)).DbType = SqlDbType.Int

cmd.Parameters("@.ReturnValue").Direction = ParameterDirection.ReturnValue

Lesson learned: Explicitly type all data values used.

Darrell

ADO.NET SP throws ArgumentException after migrating to SQL 2005 Standard

I know the ultimate solution will probably be to build the data Web Service within SQL 2005, but what can I do to get this working until I have time for that conversion?

Thanks for any help.

Darrell Escola

Darrell

|||

Dim newID As SQLTypes.SQLInt32

I added a subroutine to determine the data type for each column used in the update:

Private Sub AddSPParameter(ByRef cmd as SQLClient.SQLCommand, ByVal paramName as String, ByVal fieldValue as Object)

If paramName = "<stringColName1>" Or paramName = "<stringColName...>" Then

cmd.Parameters.AddWithValue(Ctype(Cstr(fieldValue), SQLTypes.SQLString).DbType = DbType.String

ElseIf paramName = "<otherTypeColName1>" Or paramName.IndexOf("...") > 0 Or paramName.EndsWith("...") Then

cmd.Parameters.AddWithValue(Ctype(Cstr(fieldValue), SQLTypes.SQL<otherType>).DbType = DbType.<otherType>

ElseIf ...

End If

This subroutine determines the column data type by matches on the column name, and then explicitly casting the parameter value to the applicable database data type.

I also had to explicitly cast the Return Value:

cmd.Parameters.AddWithValue("@.ReturnValue", Ctype(0, SQLTypes.SQLInt32)).DbType = SqlDbType.Int

cmd.Parameters("@.ReturnValue").Direction = ParameterDirection.ReturnValue

Lesson learned: Explicitly type all data values used.

Darrell

Thursday, February 16, 2012

ADO Connection String not working when SQL on local machine

Here is the connect tring from table properties:
ODBC;DRIVER=SQL Server;SERVER=VICRAUCH\SRVRVGSMISC;APP=Microsoft Data Access Components;WSID=VICRAUCH;DATABASE=vgs_prod;TABLE=d bo.USysCandidates

Here is the connect string from the ADO .Open connect string:
"ODBC;DRIVER=SQL Server;SERVER=VICRAUCH\SRVRVGSMISC;APP=Microsoft Data Access Components;UID=sa;PWD=xxxXX99X;WSID=VICRAUCH;DATAB ASE=vgs_prod"

Here is the ADO .Open code.
Set CNN = New ADODB.Connection
Dim strDEFConn As String
strDEFConn = FixConnStr(DEFCONN)
CNN.Open strDEFConn

The last line fails with the CNN.Open strDEFConn with this message:
Run-time error '-2147467259 (80004005)';
[Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified

This code works when the SQL Server is on it's own server, but for testing at my own office, I have SQL Server on the same machine as the Access application. I'm getting the above error where SQL Server and the Access app are on the same machine. I can open a linked SQL table from the user interface, and VBA code that deals with the tables as Access tables works. It is the ADO .Open statement where the error happens.

Thanks for any help you can give me on getting this to work.Here is the connect tring from table properties:
ODBC;DRIVER=SQL Server;SERVER=VICRAUCH\SRVRVGSMISC;APP=Microsoft Data Access Components;WSID=VICRAUCH;DATABASE=vgs_prod;TABLE=d bo.USysCandidates

Here is the connect string from the ADO .Open connect string:
"ODBC;DRIVER=SQL Server;SERVER=VICRAUCH\SRVRVGSMISC;APP=Microsoft Data Access Components;UID=sa;PWD=xxxXX99X;WSID=VICRAUCH;DATAB ASE=vgs_prod"

The error message is basically telling you that it can't find the DSN entry.

Okay, so you are using ODBC (which you have to because it's Access), how do you have the DSN configured? Is the DSN a user DSN or a user DSN. I'm not entirely clear on what it is that you are doing, but if the script is executed as a batch file using a system account, I think it won't find the DSN unless the DSN is a "system" DSN.

By the way, those connection string look a little odd to me. Did you check out www.connectionstrings.com?

Regards,

hmscott|||I think these are DSNless connections.

Ordinarily I have a switch in my apps that change the server to (Local) when developing and that pull up the server name when run by a normal user. However I am not sure how this will work with a named instance. Is there more than one instance on VICRAUCH?|||Yes, I have more than one instance on VICRAUCH. What I have to switch between different servers and databases is a local table in Access which I name "tblSetup" This is the table that holds all my "macro" variables. I use the term "macro" as in large scope. Those that relate to the app as a whole. This Access db seems to have had 3 or 4 different developers that have put it together and each one has sort of started over with their own methodology. One of my goals is to try to standardize the app without doing a complete re-write. But at the same time, be very responsive to this client when they want something done yesterday. This is continuing to be quite the challenge.
Because I am so new to SQL Server could you give me some insight as how you do the "switch" thing with the server from production to local?
Thanks,|||The "switch" is trivial - I meant (programmatically) swapping:
ODBC;DRIVER=SQL Server;SERVER=VICRAUCH\SRVRVGSMISC;APP=Microsoft Data Access Components;WSID=VICRAUCH;DATABASE=vgs_prod;TABLE=d bo.USysCandidateswith
ODBC;DRIVER=SQL Server;SERVER=(Local);APP=Microsoft Data Access Components;WSID=VICRAUCH;DATABASE=vgs_prod;TABLE=d bo.USysCandidates
However - you are connecting to a named local instance. I'm not sure how that would work. I don't have a named (local or otherwise) instance here at work but I do at home. I will try tonight if no one else sorts it out for you by then.|||What I did to get the named instance to work was "VICRAUCH\SRVRVGSMISC" as the Server= name rather than just SRVRVGSMISC. What you posted here is what needs to be done, and actually what I'm doing by changing the values in my tblSetup. I have in tblSetup the proforma connection string, Driver={SQL Native Client};Server=srvrName;Database=SQLdbName;Uid=use rName;Pwd=;and then before setting that connection string, I replace the placeholders in the proforma string with what is in the coresponding field of tblSetup.

Thank you very much for your help.

Monday, February 13, 2012

ado connection

i have developed an application that connects to SQL Server 2000.

on my machine as well as 90 % of our company's machines it works fine. but the rest (xp machines) it doesn't want to work. it keeps telling me my provider is not installed correctly. i have tried various installation of mdac but they don't install.

i see on msdn they say it could be a localization error but the workaround they give doesn't work.

what else can i try

Hi,

whats the excat error message you are gettin g?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

it says "Provider cannot be found. it may not be properly installed"

|||

i found the solution

just repair XP

it was the only thing i found that worked.

ado "sql authentication" connections affected by loss of domain controller

a. Setup 3 machines.
i. one domain controller machine. windows 2000 based. I have tried
both a regular domain setup and a domain setup in compatibility mode.
ii. one sql server machine that is a member of the domain. windows
2000.
iii. one client machine running an ado test program that communicates
with the sql server machine. I have tried both 2000 and xp.

b. Start your test ado program and create a connection.
c. Fire a query.
d. It should work.
e. Unplug the network cord on the domain controller.
f. Create a new connection and fire a new connection about a minute or
so after.
g. It should work. Apparently the client caches account information
from the domain controller for a certain amount of time. The time
seems to be shorter by default in xp than 2000.
h. Wait 20 minutes or more.
i. Create another new connection. You will notice a timeout error.
If your using windows authentication the timeout will happen 100% of
the time. That is to be expected. If your using sql authentication
the timeout seems to happen about 50% of the time. I can't explain it
other than some strange Microsoft bug. I speculate that it may be
some bug with the way ado caches connections. Perhaps a previously
setup windows authentication connection gets reused by a request for a
sql authentication connection. However I haven't been able to prove
it.

Any insight you can offer would be appreciated. I also have a test
program you can use to reproduce this behavior if you are interested.

Thanks,
Frank"Frank" <frank@.policecentral.com> wrote in message
news:c148e27c.0401120604.7d0b3c0f@.posting.google.c om...
> I have observed that a temporary loss of a domain controller can cause
> problems creating new ado connections between a client machine running
> ado and a separate sql server machine that are members of the domain.
> I understand why this happens when creating connections with windows
> authentication. What is a mystery is that it also sometimes effects
> new connections that use "sql authentication". Below is a description
> of my test scenario.
> a. Setup 3 machines.
> i. one domain controller machine. windows 2000 based. I have tried
> both a regular domain setup and a domain setup in compatibility mode.
> ii. one sql server machine that is a member of the domain. windows
> 2000.
> iii. one client machine running an ado test program that communicates
> with the sql server machine. I have tried both 2000 and xp.
> b. Start your test ado program and create a connection.
> c. Fire a query.
> d. It should work.
> e. Unplug the network cord on the domain controller.
> f. Create a new connection and fire a new connection about a minute or
> so after.
> g. It should work. Apparently the client caches account information
> from the domain controller for a certain amount of time. The time
> seems to be shorter by default in xp than 2000.
> h. Wait 20 minutes or more.
> i. Create another new connection. You will notice a timeout error.
> If your using windows authentication the timeout will happen 100% of
> the time. That is to be expected. If your using sql authentication
> the timeout seems to happen about 50% of the time. I can't explain it
> other than some strange Microsoft bug. I speculate that it may be
> some bug with the way ado caches connections. Perhaps a previously
> setup windows authentication connection gets reused by a request for a
> sql authentication connection. However I haven't been able to prove
> it.
> Any insight you can offer would be appreciated. I also have a test
> program you can use to reproduce this behavior if you are interested.
> Thanks,
> Frank

This is a complete guess, and may be an overly obvious question, but could
the 50% failure rate be due to unsuccessful name resolution, and not an
MSSQL login issue? So in the cases where the SQL authenticated connection
fails, can you still resolve the name of the SQL server? Certainly in
theory, losing the domain controller shouldn't affect SQL logins, provided
that the client can actually find the server to begin with.

Simon|||"Simon Hayes" <sql@.hayes.ch> wrote in message news:<4002fd9c$1_1@.news.bluewin.ch>...
> "Frank" <frank@.policecentral.com> wrote in message
> news:c148e27c.0401120604.7d0b3c0f@.posting.google.c om...
> > I have observed that a temporary loss of a domain controller can cause
> > problems creating new ado connections between a client machine running
> > ado and a separate sql server machine that are members of the domain.
> > I understand why this happens when creating connections with windows
> > authentication. What is a mystery is that it also sometimes effects
> > new connections that use "sql authentication". Below is a description
> > of my test scenario.
> > a. Setup 3 machines.
> > i. one domain controller machine. windows 2000 based. I have tried
> > both a regular domain setup and a domain setup in compatibility mode.
> > ii. one sql server machine that is a member of the domain. windows
> > 2000.
> > iii. one client machine running an ado test program that communicates
> > with the sql server machine. I have tried both 2000 and xp.
> > b. Start your test ado program and create a connection.
> > c. Fire a query.
> > d. It should work.
> > e. Unplug the network cord on the domain controller.
> > f. Create a new connection and fire a new connection about a minute or
> > so after.
> > g. It should work. Apparently the client caches account information
> > from the domain controller for a certain amount of time. The time
> > seems to be shorter by default in xp than 2000.
> > h. Wait 20 minutes or more.
> > i. Create another new connection. You will notice a timeout error.
> > If your using windows authentication the timeout will happen 100% of
> > the time. That is to be expected. If your using sql authentication
> > the timeout seems to happen about 50% of the time. I can't explain it
> > other than some strange Microsoft bug. I speculate that it may be
> > some bug with the way ado caches connections. Perhaps a previously
> > setup windows authentication connection gets reused by a request for a
> > sql authentication connection. However I haven't been able to prove
> > it.
> > Any insight you can offer would be appreciated. I also have a test
> > program you can use to reproduce this behavior if you are interested.
> > Thanks,
> > Frank
> This is a complete guess, and may be an overly obvious question, but could
> the 50% failure rate be due to unsuccessful name resolution, and not an
> MSSQL login issue? So in the cases where the SQL authenticated connection
> fails, can you still resolve the name of the SQL server? Certainly in
> theory, losing the domain controller shouldn't affect SQL logins, provided
> that the client can actually find the server to begin with.
> Simon

I thought of that and tried doing a ping by name after it failed. It
worked ok. However given the 50% nature of the problem I still don't
totally rule it out.

ado "sql authentication" connections affected by loss of domain controller

I have observed that a temporary loss of a domain controller can cause
problems creating new ado connections between a client machine running
ado and a separate sql server machine that are members of the domain.
I understand why this happens when creating connections with windows
authentication. What is a mystery is that it also sometimes effects
new connections that use "sql authentication". Below is a description
of my test scenario.
a. Setup 3 machines.
i. one domain controller machine. windows 2000 based. I have tried
both a regular domain setup and a domain setup in compatibility mode.
ii. one sql server machine that is a member of the domain. windows
2000.
iii. one client machine running an ado test program that communicates
with the sql server machine. I have tried both 2000 and xp.
b. Start your test ado program and create a connection.
c. Fire a query.
d. It should work.
e. Unplug the network cord on the domain controller.
f. Create a new connection and fire a new connection about a minute or
so after.
g. It should work. Apparently the client caches account information
from the domain controller for a certain amount of time. The time
seems to be shorter by default in xp than 2000.
h. Wait 20 minutes or more.
i. Create another new connection. You will notice a timeout error.
If your using windows authentication the timeout will happen 100% of
the time. That is to be expected. If your using sql authentication
the timeout seems to happen about 50% of the time. I can't explain it
other than some strange Microsoft bug. I speculate that it may be
some bug with the way ado caches connections. Perhaps a previously
setup windows authentication connection gets reused by a request for a
sql authentication connection. However I haven't been able to prove
it.
Any insight you can offer would be appreciated. I also have a test
program you can use to reproduce this behavior if you are interested.
Thanks,
Frank"Frank" <frank@.policecentral.com> wrote in message
news:c148e27c.0401120604.7d0b3c0f@.posting.google.com...
> I have observed that a temporary loss of a domain controller can cause
> problems creating new ado connections between a client machine running
> ado and a separate sql server machine that are members of the domain.
> I understand why this happens when creating connections with windows
> authentication. What is a mystery is that it also sometimes effects
> new connections that use "sql authentication". Below is a description
> of my test scenario.
> a. Setup 3 machines.
> i. one domain controller machine. windows 2000 based. I have tried
> both a regular domain setup and a domain setup in compatibility mode.
> ii. one sql server machine that is a member of the domain. windows
> 2000.
> iii. one client machine running an ado test program that communicates
> with the sql server machine. I have tried both 2000 and xp.
> b. Start your test ado program and create a connection.
> c. Fire a query.
> d. It should work.
> e. Unplug the network cord on the domain controller.
> f. Create a new connection and fire a new connection about a minute or
> so after.
> g. It should work. Apparently the client caches account information
> from the domain controller for a certain amount of time. The time
> seems to be shorter by default in xp than 2000.
> h. Wait 20 minutes or more.
> i. Create another new connection. You will notice a timeout error.
> If your using windows authentication the timeout will happen 100% of
> the time. That is to be expected. If your using sql authentication
> the timeout seems to happen about 50% of the time. I can't explain it
> other than some strange Microsoft bug. I speculate that it may be
> some bug with the way ado caches connections. Perhaps a previously
> setup windows authentication connection gets reused by a request for a
> sql authentication connection. However I haven't been able to prove
> it.
> Any insight you can offer would be appreciated. I also have a test
> program you can use to reproduce this behavior if you are interested.
> Thanks,
> Frank
This is a complete guess, and may be an overly obvious question, but could
the 50% failure rate be due to unsuccessful name resolution, and not an
MSSQL login issue? So in the cases where the SQL authenticated connection
fails, can you still resolve the name of the SQL server? Certainly in
theory, losing the domain controller shouldn't affect SQL logins, provided
that the client can actually find the server to begin with.
Simon|||Which network library are you using to establish the
connection? Named pipes will require an underlying
NetBIOS connection to the SQL Server, which may result in
the "cache-ing" behavior you are seeing. NetBIOS
connections will require NT user account authentication
and the use of a domain controller.
If you refer to the SQL Server by IP Address in your
connectino string, you can force the client to connect
using TCP/IP which does not require an underlying Named
Pipe connection.
I don't know if this will help, but it is one possible
explanation.
Matthew Bando
BandoM@.CSCTGI(remove this).com
>--Original Message--
>I have observed that a temporary loss of a domain
controller can cause
>problems creating new ado connections between a client
machine running
>ado and a separate sql server machine that are members
of the domain.
>I understand why this happens when creating connections
with windows
>authentication. What is a mystery is that it also
sometimes effects
>new connections that use "sql authentication". Below is
a description
>of my test scenario.
>a. Setup 3 machines.
> i. one domain controller machine. windows 2000
based. I have tried
>both a regular domain setup and a domain setup in
compatibility mode.
> ii. one sql server machine that is a member of
the domain. windows
>2000.
> iii. one client machine running an ado test
program that communicates
>with the sql server machine. I have tried both 2000 and
xp.
>b. Start your test ado program and create a connection.
>c. Fire a query.
>d. It should work.
>e. Unplug the network cord on the domain controller.
>f. Create a new connection and fire a new connection
about a minute or
>so after.
>g. It should work. Apparently the client caches account
information
>from the domain controller for a certain amount of
time. The time
>seems to be shorter by default in xp than 2000.
>h. Wait 20 minutes or more.
>i. Create another new connection. You will notice a
timeout error.
>If your using windows authentication the timeout will
happen 100% of
>the time. That is to be expected. If your using sql
authentication
>the timeout seems to happen about 50% of the time. I
can't explain it
>other than some strange Microsoft bug. I speculate that
it may be
>some bug with the way ado caches connections. Perhaps a
previously
>setup windows authentication connection gets reused by a
request for a
>sql authentication connection. However I haven't been
able to prove
>it.
>Any insight you can offer would be appreciated. I also
have a test
>program you can use to reproduce this behavior if you
are interested.
>Thanks,
>Frank
>.
>|||"Simon Hayes" <sql@.hayes.ch> wrote in message news:<4002fd9c$1_1@.news.bluewin.ch>...
> "Frank" <frank@.policecentral.com> wrote in message
> news:c148e27c.0401120604.7d0b3c0f@.posting.google.com...
> > I have observed that a temporary loss of a domain controller can cause
> > problems creating new ado connections between a client machine running
> > ado and a separate sql server machine that are members of the domain.
> > I understand why this happens when creating connections with windows
> > authentication. What is a mystery is that it also sometimes effects
> > new connections that use "sql authentication". Below is a description
> > of my test scenario.
> >
> > a. Setup 3 machines.
> > i. one domain controller machine. windows 2000 based. I have tried
> > both a regular domain setup and a domain setup in compatibility mode.
> > ii. one sql server machine that is a member of the domain. windows
> > 2000.
> > iii. one client machine running an ado test program that communicates
> > with the sql server machine. I have tried both 2000 and xp.
> >
> > b. Start your test ado program and create a connection.
> > c. Fire a query.
> > d. It should work.
> > e. Unplug the network cord on the domain controller.
> > f. Create a new connection and fire a new connection about a minute or
> > so after.
> > g. It should work. Apparently the client caches account information
> > from the domain controller for a certain amount of time. The time
> > seems to be shorter by default in xp than 2000.
> > h. Wait 20 minutes or more.
> > i. Create another new connection. You will notice a timeout error.
> > If your using windows authentication the timeout will happen 100% of
> > the time. That is to be expected. If your using sql authentication
> > the timeout seems to happen about 50% of the time. I can't explain it
> > other than some strange Microsoft bug. I speculate that it may be
> > some bug with the way ado caches connections. Perhaps a previously
> > setup windows authentication connection gets reused by a request for a
> > sql authentication connection. However I haven't been able to prove
> > it.
> >
> > Any insight you can offer would be appreciated. I also have a test
> > program you can use to reproduce this behavior if you are interested.
> >
> > Thanks,
> > Frank
> This is a complete guess, and may be an overly obvious question, but could
> the 50% failure rate be due to unsuccessful name resolution, and not an
> MSSQL login issue? So in the cases where the SQL authenticated connection
> fails, can you still resolve the name of the SQL server? Certainly in
> theory, losing the domain controller shouldn't affect SQL logins, provided
> that the client can actually find the server to begin with.
> Simon
I thought of that and tried doing a ping by name after it failed. It
worked ok. However given the 50% nature of the problem I still don't
totally rule it out.|||I considered that possibility. I did bring up the "Client Network
Utility" on the client and made tcp/ip the only choice. The behavior
did not change. However I am referencing the machine by name and not
ip. I will try the ip technique and report back.
"Matthew Bando" <anonymous@.discussions.microsoft.com> wrote in message news:<062d01c3d9ec$f7e783c0$a001280a@.phx.gbl>...
> Which network library are you using to establish the
> connection? Named pipes will require an underlying
> NetBIOS connection to the SQL Server, which may result in
> the "cache-ing" behavior you are seeing. NetBIOS
> connections will require NT user account authentication
> and the use of a domain controller.
> If you refer to the SQL Server by IP Address in your
> connectino string, you can force the client to connect
> using TCP/IP which does not require an underlying Named
> Pipe connection.
> I don't know if this will help, but it is one possible
> explanation.
> Matthew Bando
> BandoM@.CSCTGI(remove this).com
>
> >--Original Message--
> >I have observed that a temporary loss of a domain
> controller can cause
> >problems creating new ado connections between a client
> machine running
> >ado and a separate sql server machine that are members
> of the domain.
> >I understand why this happens when creating connections
> with windows
> >authentication. What is a mystery is that it also
> sometimes effects
> >new connections that use "sql authentication". Below is
> a description
> >of my test scenario.
> >
> >a. Setup 3 machines.
> > i. one domain controller machine. windows 2000
> based. I have tried
> >both a regular domain setup and a domain setup in
> compatibility mode.
> > ii. one sql server machine that is a member of
> the domain. windows
> >2000.
> > iii. one client machine running an ado test
> program that communicates
> >with the sql server machine. I have tried both 2000 and
> xp.
> >
> >b. Start your test ado program and create a connection.
> >c. Fire a query.
> >d. It should work.
> >e. Unplug the network cord on the domain controller.
> >f. Create a new connection and fire a new connection
> about a minute or
> >so after.
> >g. It should work. Apparently the client caches account
> information
> >from the domain controller for a certain amount of
> time. The time
> >seems to be shorter by default in xp than 2000.
> >h. Wait 20 minutes or more.
> >i. Create another new connection. You will notice a
> timeout error.
> >If your using windows authentication the timeout will
> happen 100% of
> >the time. That is to be expected. If your using sql
> authentication
> >the timeout seems to happen about 50% of the time. I
> can't explain it
> >other than some strange Microsoft bug. I speculate that
> it may be
> >some bug with the way ado caches connections. Perhaps a
> previously
> >setup windows authentication connection gets reused by a
> request for a
> >sql authentication connection. However I haven't been
> able to prove
> >it.
> >
> >Any insight you can offer would be appreciated. I also
> have a test
> >program you can use to reproduce this behavior if you
> are interested.
> >
> >Thanks,
> >Frank
> >.
> >|||Thanks for the help. The mystery has been solved. I ended up opening
a ms support incident and they helped me figure it out. For those
that guessed dns server that was the right idea. However what made it
difficult to pin down is the following.
A. I tried as one person suggested connecting by ip address. I
thought this would eliminate dns issues from the equation. However as
the ms support guy informed me ado does a gethostbyaddr early in the
connection if you pass in an ip address. Therefore if the computer
can't do that your out of business.
B. I also thought that dns was not a factor because I could ping by
name after a connection failure and it would work. However the reason
it worked is because all the machines were on the same subnet and the
broadcast was what made it work. Once the dns server drops out the
first ping response was very slow. if you would do a ping immediately
after the response the 2nd ping would be fast. That behavior was what
was causing the randomness of the connection working. The first time
the connection would time out. However the attempt woke things up and
the second attempt would succeed.
Now that I know this I can route the important machines to a more
isolated and protected dns server or manually edit the hosts files to
eliminate the domain controller / dns controller that I can't control
from the equation.
frank@.policecentral.com (Frank) wrote in message news:<c148e27c.0401131411.32f26332@.posting.google.com>...
> I considered that possibility. I did bring up the "Client Network
> Utility" on the client and made tcp/ip the only choice. The behavior
> did not change. However I am referencing the machine by name and not
> ip. I will try the ip technique and report back.
> "Matthew Bando" <anonymous@.discussions.microsoft.com> wrote in message news:<062d01c3d9ec$f7e783c0$a001280a@.phx.gbl>...
> > Which network library are you using to establish the
> > connection? Named pipes will require an underlying
> > NetBIOS connection to the SQL Server, which may result in
> > the "cache-ing" behavior you are seeing. NetBIOS
> > connections will require NT user account authentication
> > and the use of a domain controller.
> >
> > If you refer to the SQL Server by IP Address in your
> > connectino string, you can force the client to connect
> > using TCP/IP which does not require an underlying Named
> > Pipe connection.
> >
> > I don't know if this will help, but it is one possible
> > explanation.
> >
> > Matthew Bando
> > BandoM@.CSCTGI(remove this).com
> >
> >
> >
> > >--Original Message--
> > >I have observed that a temporary loss of a domain
> controller can cause
> > >problems creating new ado connections between a client
> machine running
> > >ado and a separate sql server machine that are members
> of the domain.
> > >I understand why this happens when creating connections
> with windows
> > >authentication. What is a mystery is that it also
> sometimes effects
> > >new connections that use "sql authentication". Below is
> a description
> > >of my test scenario.
> > >
> > >a. Setup 3 machines.
> > > i. one domain controller machine. windows 2000
> based. I have tried
> > >both a regular domain setup and a domain setup in
> compatibility mode.
> > > ii. one sql server machine that is a member of
> the domain. windows
> > >2000.
> > > iii. one client machine running an ado test
> program that communicates
> > >with the sql server machine. I have tried both 2000 and
> xp.
> > >
> > >b. Start your test ado program and create a connection.
> > >c. Fire a query.
> > >d. It should work.
> > >e. Unplug the network cord on the domain controller.
> > >f. Create a new connection and fire a new connection
> about a minute or
> > >so after.
> > >g. It should work. Apparently the client caches account
> information
> > >from the domain controller for a certain amount of
> time. The time
> > >seems to be shorter by default in xp than 2000.
> > >h. Wait 20 minutes or more.
> > >i. Create another new connection. You will notice a
> timeout error.
> > >If your using windows authentication the timeout will
> happen 100% of
> > >the time. That is to be expected. If your using sql
> authentication
> > >the timeout seems to happen about 50% of the time. I
> can't explain it
> > >other than some strange Microsoft bug. I speculate that
> it may be
> > >some bug with the way ado caches connections. Perhaps a
> previously
> > >setup windows authentication connection gets reused by a
> request for a
> > >sql authentication connection. However I haven't been
> able to prove
> > >it.
> > >
> > >Any insight you can offer would be appreciated. I also
> have a test
> > >program you can use to reproduce this behavior if you
> are interested.
> > >
> > >Thanks,
> > >Frank
> > >.
> > >

ado "sql authentication" connections affected by loss of domain controller

quote:

> I have observed that a temporary loss of a domain controller can cause
> problems creating new ado connections between a client machine running
> ado and a separate sql server machine that are members of the domain.
> I understand why this happens when creating connections with windows
> authentication. What is a mystery is that it also sometimes effects
> new connections that use "sql authentication". Below is a description
> of my test scenario.
> a. Setup 3 machines.
> i. one domain controller machine. Windows 2000 based. I have tried
> both a regular domain setup and a domain setup in compatibility mode.
> ii. one sql server machine that is a member of the domain. windows
> 2000.
> iii. one client machine running an ado test program that communicates
> with the sql server machine. I have tried both 2000 and xp.
> b. Start your test ado program and create a connection.
> c. Fire a query.
> d. It should work.
> e. Unplug the network cord on the domain controller.
> f. Create a new connection and fire a new connection about a minute or
> so after.
> g. It should work. Apparently the client caches account information
> from the domain controller for a certain amount of time. The time
> seems to be shorter by default in xp than 2000.
> h. Wait 20 minutes or more.
> i. Create another new connection. You will notice a timeout error.
> If your using windows authentication the timeout will happen 100% of
> the time. That is to be expected. If your using sql authentication
> the timeout seems to happen about 50% of the time. I can't explain it
> other than some strange Microsoft bug. I speculate that it may be
> some bug with the way ado caches connections. Perhaps a previously
> setup windows authentication connection gets reused by a request for a
> sql authentication connection. However I haven't been able to prove
> it.
> Any insight you can offer would be appreciated. I also have a test
> program you can use to reproduce this behavior if you are interested.
> Thanks,
> Frank

quote:
darkred">
> "Frank" <frank@.policecentral.com> wrote in message
> news:c148e27c.0401120604.7d0b3c0f@.posting.google.com...
> This is a complete guess, and may be an overly obvious question, but could
> the 50% failure rate be due to unsuccessful name resolution, and not an
> MSSQL login issue? So in the cases where the SQL authenticated connection
> fails, can you still resolve the name of the SQL server? Certainly in
> theory, losing the domain controller shouldn't affect SQL logins, provided
> that the client can actually find the server to begin with.
> Simon

I thought of that and tried doing a ping by name after it failed. It
worked ok. However given the 50% nature of the problem I still don't
totally rule it out.

Sunday, February 12, 2012

Administrator with No Report Manager Privileges

I am logged on as a user with administrative privileges to
my machine, to the machine housing the report server
database, and to the the web server, yet when I go to
Report Manager, I do not have access to the Home folder,
only one lower folder, and no Site Settings for anything.
How do I add the necessary privileges if I'm already the
administrator?I found that if you have set the Report Server virtual directory to allow
anonymous access in the IIS mgmt console, you may find yourself in the
situation you described. I was experimenting with anonymous and got into the
situation, where I was a local admin but options like create new folders and
upload files were all gone from Report Manager. After I removed anonymous
access, I was able to fully administer Reporting Services via Report Manager
again.
Linchi
"Terry" <anonymous@.discussions.microsoft.com> wrote in message
news:029c01c47a5e$9cc531a0$a601280a@.phx.gbl...
> I am logged on as a user with administrative privileges to
> my machine, to the machine housing the report server
> database, and to the the web server, yet when I go to
> Report Manager, I do not have access to the Home folder,
> only one lower folder, and no Site Settings for anything.
> How do I add the necessary privileges if I'm already the
> administrator?
>|||Linchi, Thanks for your response and you are correct
about the configuration of anonymous access, however,
this site needs anonymous access. Any suggestions on how
to get my rights back and keep anonymous access?
>--Original Message--
>I found that if you have set the Report Server virtual
directory to allow
>anonymous access in the IIS mgmt console, you may find
yourself in the
>situation you described. I was experimenting with
anonymous and got into the
>situation, where I was a local admin but options like
create new folders and
>upload files were all gone from Report Manager. After I
removed anonymous
>access, I was able to fully administer Reporting
Services via Report Manager
>again.
>Linchi
>"Terry" <anonymous@.discussions.microsoft.com> wrote in
message
>news:029c01c47a5e$9cc531a0$a601280a@.phx.gbl...
>> I am logged on as a user with administrative
privileges to
>> my machine, to the machine housing the report server
>> database, and to the the web server, yet when I go to
>> Report Manager, I do not have access to the Home
folder,
>> only one lower folder, and no Site Settings for
anything.
>> How do I add the necessary privileges if I'm already
the
>> administrator?
>
>.
>|||No, I have not found why or how to work around it. In my case, I didn't
really need anonymous access. I hope MS folks can shed some light on this
behavior.
Linchi
"Terry" <anonymous@.discussions.microsoft.com> wrote in message
news:085c01c47af3$75d2fe20$a301280a@.phx.gbl...
> Linchi, Thanks for your response and you are correct
> about the configuration of anonymous access, however,
> this site needs anonymous access. Any suggestions on how
> to get my rights back and keep anonymous access?
>
> >--Original Message--
> >I found that if you have set the Report Server virtual
> directory to allow
> >anonymous access in the IIS mgmt console, you may find
> yourself in the
> >situation you described. I was experimenting with
> anonymous and got into the
> >situation, where I was a local admin but options like
> create new folders and
> >upload files were all gone from Report Manager. After I
> removed anonymous
> >access, I was able to fully administer Reporting
> Services via Report Manager
> >again.
> >
> >Linchi
> >
> >"Terry" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:029c01c47a5e$9cc531a0$a601280a@.phx.gbl...
> >> I am logged on as a user with administrative
> privileges to
> >> my machine, to the machine housing the report server
> >> database, and to the the web server, yet when I go to
> >> Report Manager, I do not have access to the Home
> folder,
> >> only one lower folder, and no Site Settings for
> anything.
> >> How do I add the necessary privileges if I'm already
> the
> >> administrator?
> >>
> >
> >
> >.
> >|||When you enable anonymous access, all requests come in as the anonymous
user. Since that user does not have any role assignments in the report
server, they cannot see any folders, nor can they perform operations.
We recommend that you do not use anonymous access to the report server, but
enable windows secuirty.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Linchi Shea" <linchi_shea@.NOSPAM.ml.com> wrote in message
news:eBZrcj1eEHA.2028@.tk2msftngp13.phx.gbl...
> No, I have not found why or how to work around it. In my case, I didn't
> really need anonymous access. I hope MS folks can shed some light on this
> behavior.
> Linchi
> "Terry" <anonymous@.discussions.microsoft.com> wrote in message
> news:085c01c47af3$75d2fe20$a301280a@.phx.gbl...
>> Linchi, Thanks for your response and you are correct
>> about the configuration of anonymous access, however,
>> this site needs anonymous access. Any suggestions on how
>> to get my rights back and keep anonymous access?
>>
>> >--Original Message--
>> >I found that if you have set the Report Server virtual
>> directory to allow
>> >anonymous access in the IIS mgmt console, you may find
>> yourself in the
>> >situation you described. I was experimenting with
>> anonymous and got into the
>> >situation, where I was a local admin but options like
>> create new folders and
>> >upload files were all gone from Report Manager. After I
>> removed anonymous
>> >access, I was able to fully administer Reporting
>> Services via Report Manager
>> >again.
>> >
>> >Linchi
>> >
>> >"Terry" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> >news:029c01c47a5e$9cc531a0$a601280a@.phx.gbl...
>> >> I am logged on as a user with administrative
>> privileges to
>> >> my machine, to the machine housing the report server
>> >> database, and to the the web server, yet when I go to
>> >> Report Manager, I do not have access to the Home
>> folder,
>> >> only one lower folder, and no Site Settings for
>> anything.
>> >> How do I add the necessary privileges if I'm already
>> the
>> >> administrator?
>> >>
>> >
>> >
>> >.
>> >
>

Administrator does not have any privileges

I am logged on as a user with administrative privileges to my machine, yet when I go to the Report Manager, I have no tabs or Site Settings. How do I add the necessary privileges if I'm already the administrator?Are you using a custom security extension?
-Lukasz
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in message
news:56D7FB04-7279-4193-A809-E12D46827F6A@.microsoft.com...
> I am logged on as a user with administrative privileges to my machine, yet
when I go to the Report Manager, I have no tabs or Site Settings. How do I
add the necessary privileges if I'm already the administrator?|||No. I have everything set up very generically.
"Lukasz Pawlowski [MSFT]" wrote:
> Are you using a custom security extension?
> -Lukasz
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in message
> news:56D7FB04-7279-4193-A809-E12D46827F6A@.microsoft.com...
> > I am logged on as a user with administrative privileges to my machine, yet
> when I go to the Report Manager, I have no tabs or Site Settings. How do I
> add the necessary privileges if I'm already the administrator?
>
>|||Are you loggedin locally? Your user is a memeber of the local
administrators group?
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in message
news:EC031FF7-BDCB-46B4-98E2-2E8787C030A6@.microsoft.com...
> No. I have everything set up very generically.
> "Lukasz Pawlowski [MSFT]" wrote:
> > Are you using a custom security extension?
> >
> > -Lukasz
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> >
> > "Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in message
> > news:56D7FB04-7279-4193-A809-E12D46827F6A@.microsoft.com...
> > > I am logged on as a user with administrative privileges to my machine,
yet
> > when I go to the Report Manager, I have no tabs or Site Settings. How
do I
> > add the necessary privileges if I'm already the administrator?
> >
> >
> >|||Yes. I am logged on as a member of the Administrators group. Thanks!
"Lukasz Pawlowski [MSFT]" wrote:
> Are you loggedin locally? Your user is a memeber of the local
> administrators group?
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in message
> news:EC031FF7-BDCB-46B4-98E2-2E8787C030A6@.microsoft.com...
> > No. I have everything set up very generically.
> >
> > "Lukasz Pawlowski [MSFT]" wrote:
> >
> > > Are you using a custom security extension?
> > >
> > > -Lukasz
> > >
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > >
> > > "Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in message
> > > news:56D7FB04-7279-4193-A809-E12D46827F6A@.microsoft.com...
> > > > I am logged on as a user with administrative privileges to my machine,
> yet
> > > when I go to the Report Manager, I have no tabs or Site Settings. How
> do I
> > > add the necessary privileges if I'm already the administrator?
> > >
> > >
> > >
>
>|||Was this ever resolved? I am having the same problem.
>--Original Message--
>Yes. I am logged on as a member of the Administrators
group. Thanks!
>"Lukasz Pawlowski [MSFT]" wrote:
>> Are you loggedin locally? Your user is a memeber of
the local
>> administrators group?
>> -Lukasz
>>
>> --
>> This posting is provided "AS IS" with no warranties,
and confers no rights.
>>
>> "Patrick_McD" <Patrick_McD@.discussions.microsoft.com>
wrote in message
>> news:EC031FF7-BDCB-46B4-98E2-
2E8787C030A6@.microsoft.com...
>> > No. I have everything set up very generically.
>> >
>> > "Lukasz Pawlowski [MSFT]" wrote:
>> >
>> > > Are you using a custom security extension?
>> > >
>> > > -Lukasz
>> > >
>> > > --
>> > > This posting is provided "AS IS" with no
warranties, and confers no
>> rights.
>> > >
>> > >
>> > >
>> > > "Patrick_McD"
<Patrick_McD@.discussions.microsoft.com> wrote in message
>> > > news:56D7FB04-7279-4193-A809-
E12D46827F6A@.microsoft.com...
>> > > > I am logged on as a user with administrative
privileges to my machine,
>> yet
>> > > when I go to the Report Manager, I have no tabs or
Site Settings. How
>> do I
>> > > add the necessary privileges if I'm already the
administrator?
>> > >
>> > >
>> > >
>>
>.
>|||Are the /reportserver and /reports virtual directories configured to use
integrated security and *no* anonymous access?
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Patrick_McD" <PatrickMcD@.discussions.microsoft.com> wrote in message
news:3086AADF-A3F3-4698-88E1-5AE6B2689424@.microsoft.com...
> Yes. I am logged on as a member of the Administrators group. Thanks!
> "Lukasz Pawlowski [MSFT]" wrote:
> > Are you loggedin locally? Your user is a memeber of the local
> > administrators group?
> >
> > -Lukasz
> >
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> >
> > "Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in message
> > news:EC031FF7-BDCB-46B4-98E2-2E8787C030A6@.microsoft.com...
> > > No. I have everything set up very generically.
> > >
> > > "Lukasz Pawlowski [MSFT]" wrote:
> > >
> > > > Are you using a custom security extension?
> > > >
> > > > -Lukasz
> > > >
> > > > --
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > >
> > > > "Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in
message
> > > > news:56D7FB04-7279-4193-A809-E12D46827F6A@.microsoft.com...
> > > > > I am logged on as a user with administrative privileges to my
machine,
> > yet
> > > > when I go to the Report Manager, I have no tabs or Site Settings.
How
> > do I
> > > > add the necessary privileges if I'm already the administrator?
> > > >
> > > >
> > > >
> >
> >
> >|||Tudor;
There is another thread on this same issue. I wonder whether you know why
setting anonymous access would result in this behavior, and whether there is
a way to retain both the admin privileges for the local admin and anonymous
access.
Linchi
"Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
news:eyJlrcyeEHA.2848@.TK2MSFTNGP10.phx.gbl...
> Are the /reportserver and /reports virtual directories configured to use
> integrated security and *no* anonymous access?
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Patrick_McD" <PatrickMcD@.discussions.microsoft.com> wrote in message
> news:3086AADF-A3F3-4698-88E1-5AE6B2689424@.microsoft.com...
> > Yes. I am logged on as a member of the Administrators group. Thanks!
> >
> > "Lukasz Pawlowski [MSFT]" wrote:
> >
> > > Are you loggedin locally? Your user is a memeber of the local
> > > administrators group?
> > >
> > > -Lukasz
> > >
> > >
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > >
> > > "Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in message
> > > news:EC031FF7-BDCB-46B4-98E2-2E8787C030A6@.microsoft.com...
> > > > No. I have everything set up very generically.
> > > >
> > > > "Lukasz Pawlowski [MSFT]" wrote:
> > > >
> > > > > Are you using a custom security extension?
> > > > >
> > > > > -Lukasz
> > > > >
> > > > > --
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > rights.
> > > > >
> > > > >
> > > > >
> > > > > "Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in
> message
> > > > > news:56D7FB04-7279-4193-A809-E12D46827F6A@.microsoft.com...
> > > > > > I am logged on as a user with administrative privileges to my
> machine,
> > > yet
> > > > > when I go to the Report Manager, I have no tabs or Site Settings.
> How
> > > do I
> > > > > add the necessary privileges if I'm already the administrator?
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>|||Yes, allowing anonymous access would result in this behavior.
Allowing anonymous access means all users will be seen as the same user, the
server won't even ask them to provide their authentication information.
You can't have both anonymous and non anonymous on the same virtual
directories. I presume you could create two virtual directories one allowing
anonymous access, the other not.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Linchi Shea" <linchi_shea@.NOSPAM.ml.com> wrote in message
news:ebSCkhBfEHA.3520@.TK2MSFTNGP10.phx.gbl...
> Tudor;
> There is another thread on this same issue. I wonder whether you know why
> setting anonymous access would result in this behavior, and whether there
is
> a way to retain both the admin privileges for the local admin and
anonymous
> access.
> Linchi
> "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> news:eyJlrcyeEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > Are the /reportserver and /reports virtual directories configured to use
> > integrated security and *no* anonymous access?
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Patrick_McD" <PatrickMcD@.discussions.microsoft.com> wrote in message
> > news:3086AADF-A3F3-4698-88E1-5AE6B2689424@.microsoft.com...
> > > Yes. I am logged on as a member of the Administrators group. Thanks!
> > >
> > > "Lukasz Pawlowski [MSFT]" wrote:
> > >
> > > > Are you loggedin locally? Your user is a memeber of the local
> > > > administrators group?
> > > >
> > > > -Lukasz
> > > >
> > > >
> > > > --
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > >
> > > > "Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in
message
> > > > news:EC031FF7-BDCB-46B4-98E2-2E8787C030A6@.microsoft.com...
> > > > > No. I have everything set up very generically.
> > > > >
> > > > > "Lukasz Pawlowski [MSFT]" wrote:
> > > > >
> > > > > > Are you using a custom security extension?
> > > > > >
> > > > > > -Lukasz
> > > > > >
> > > > > > --
> > > > > > This posting is provided "AS IS" with no warranties, and confers
> no
> > > > rights.
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in
> > message
> > > > > > news:56D7FB04-7279-4193-A809-E12D46827F6A@.microsoft.com...
> > > > > > > I am logged on as a user with administrative privileges to my
> > machine,
> > > > yet
> > > > > > when I go to the Report Manager, I have no tabs or Site
Settings.
> > How
> > > > do I
> > > > > > add the necessary privileges if I'm already the administrator?
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
>|||Tudor;
Could you please elaborate how you can create two virtual directories and
work the way you described, when it comes to Reporting Services?
Linchi
"Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
news:uXhU5KKfEHA.140@.TK2MSFTNGP12.phx.gbl...
> Yes, allowing anonymous access would result in this behavior.
> Allowing anonymous access means all users will be seen as the same user,
the
> server won't even ask them to provide their authentication information.
> You can't have both anonymous and non anonymous on the same virtual
> directories. I presume you could create two virtual directories one
allowing
> anonymous access, the other not.
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Linchi Shea" <linchi_shea@.NOSPAM.ml.com> wrote in message
> news:ebSCkhBfEHA.3520@.TK2MSFTNGP10.phx.gbl...
> > Tudor;
> >
> > There is another thread on this same issue. I wonder whether you know
why
> > setting anonymous access would result in this behavior, and whether
there
> is
> > a way to retain both the admin privileges for the local admin and
> anonymous
> > access.
> >
> > Linchi
> >
> > "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> > news:eyJlrcyeEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > > Are the /reportserver and /reports virtual directories configured to
use
> > > integrated security and *no* anonymous access?
> > >
> > > --
> > > Tudor Trufinescu
> > > Dev Lead
> > > Sql Server Reporting Services
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > > "Patrick_McD" <PatrickMcD@.discussions.microsoft.com> wrote in message
> > > news:3086AADF-A3F3-4698-88E1-5AE6B2689424@.microsoft.com...
> > > > Yes. I am logged on as a member of the Administrators group.
Thanks!
> > > >
> > > > "Lukasz Pawlowski [MSFT]" wrote:
> > > >
> > > > > Are you loggedin locally? Your user is a memeber of the local
> > > > > administrators group?
> > > > >
> > > > > -Lukasz
> > > > >
> > > > >
> > > > > --
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > rights.
> > > > >
> > > > >
> > > > >
> > > > > "Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in
> message
> > > > > news:EC031FF7-BDCB-46B4-98E2-2E8787C030A6@.microsoft.com...
> > > > > > No. I have everything set up very generically.
> > > > > >
> > > > > > "Lukasz Pawlowski [MSFT]" wrote:
> > > > > >
> > > > > > > Are you using a custom security extension?
> > > > > > >
> > > > > > > -Lukasz
> > > > > > >
> > > > > > > --
> > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > rights.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > "Patrick_McD" <Patrick_McD@.discussions.microsoft.com> wrote in
> > > message
> > > > > > > news:56D7FB04-7279-4193-A809-E12D46827F6A@.microsoft.com...
> > > > > > > > I am logged on as a user with administrative privileges to
my
> > > machine,
> > > > > yet
> > > > > > > when I go to the Report Manager, I have no tabs or Site
> Settings.
> > > How
> > > > > do I
> > > > > > > add the necessary privileges if I'm already the administrator?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> >
> >
>

Tuesday, March 20, 2012

Advantages of using SQL Server vs Oracle for Small to Mdium Size N

Advantages of using SQL Server vs Oracle for Small to Mdium Size N

Advantages of using SQL Server vs Oracle for Small to Mdium Size N

Monday, March 19, 2012

Advantage comparison on Attach & Restore database

Advantage comparison on Attach & Restore database

Tuesday, March 6, 2012

ADOMD.Connection error

ADOMD.Connection error

Saturday, February 25, 2012

ADODB Vesion 7.0.3300.0 in vb.net

ADODB Vesion 7.0.3300.0 in vb.net

ADODB Vesion 7.0.3300.0 in vb.net

adodb connections to a linked server

ADO.NET SP throws ArgumentException after migrating to SQL 2005 Standard - UPDATE 2 - FIXED

ADO.NET SP throws ArgumentException after migrating to SQL 2005 Standard

Thursday, February 16, 2012

ADO Connection String not working when SQL on local machine

Monday, February 13, 2012

ado connection

ado "sql authentication" connections affected by loss of domain controller

ado "sql authentication" connections affected by loss of domain controller

ado "sql authentication" connections affected by loss of domain controller

Sunday, February 12, 2012

Administrator with No Report Manager Privileges

Administrator does not have any privileges

SQL Adding a User account

Blog Archive

About Me