Sunday, March 25, 2012
connectivity to the databse in SQL server 7
Connection failed
SQL state'28000'
SQL server driver'18456'
[Microsoft ][ODBC SQL server driver ][SQL server] Login failed for user 'faraidba']
do I need check my login ID for the database I have created or my ODBC driver is obsolete. Please help as I'm new with it.Did you select NT authentication or Server authentication?
I suspect it was server authentication, You have either supplied an invalid username, an invalid password, or some combination of both.
If you used NT authentication, your problem is that your network id has not been setup as a valid login.
If you wish to test your login you can always use I/OSQL.EXE. If you are using NT authentication you should be able to login in using "OSQL -S <your server name> -E", and if using Server authentication try "OSQL -S <your server name> -U <your user id> -P <your password>". If either of these work then you have a problem with ODBC.
give this some thought and let me know what you find.|||Thanx.
I've followed ur suggestion. I used the correct login name and password. The network library: I chose 'name pipes' connection in ODBC to connect to the server and this message propmted;
Connection failed
SQL state:'08004'
SQL serve error:4062
Server rejected the connection;
Access to selected database has been denied
Should I use TCP/IP(network libraries) instead?|||Thanx.
I've followed ur suggestion. I used the correct login name and password. The network library: I chose 'name pipes' connection in ODBC to connect to the server and this message propmted;
Connection failed
SQL state:'08004'
SQL serve error:4062
Server rejected the connection;
Access to selected database has been denied
Should I use TCP/IP(network libraries) instead?
I try to connect using server authentication.|||Okay, I think your problem is that the usreid you are using has not been granted access to the DB you are trying to connect to.
Again if you use I/OSQL.EXE to try and connect as I outlined before you would have connected to your default database. Most of the time this is the master db. If you try usng I/OSQL again but add "-d <your db name>" and see if you don't get a similar message or connect as before and issue the T-SQL command "use <your db name> go".
The NETWORK Library you are using is just fine. The fact that you have connected to the SQL engine is evident by the error message.|||you're correct. now i'm able to do the connection.
hope to seek ur help next time.. ;)
thanks, freind
laziaf238
KL,
Malaysia
Monday, March 19, 2012
Connections & Single-User
As an sql novice I have created some Maintenance Plans which seemed to work
ok except for integrity checks. As I can read from the logs they could'n be
executed because the db had to be in Single-User. Ok got that.
But the problem is that other servers are running some foreground &
background programs that connect to the sql svr. When I closed the
connections on our sql, the other server keeps connecting back resulting in
the fact I couldn't close the connections. This weekend when I rebooted the
other servers they lost connection to sql resulting in 0 connections to the
db.
How can this be done then, if remote servers keep connecting ? Is there a
safe way to get my db's in single user ?
I presume my test by closing the active connections to the sql via Ent. Mgr
was also not a good thing to do?
Rgds,
T.
The way to handle it is to remove the check for the option
to repair errors on your integrity checks in the maintenance
plan. You don't really want automatic repairs happening if
your dbcc checkdbs fail. You would want to intervene
yourself, determine what caused the consistency error, fix
the underlying problem and then take whatever course of
action based on what the underlying problem is.
-Sue
On Mon, 20 Sep 2004 19:21:26 GMT, "TieTo" <nobody@.home.net>
wrote:
>Hello all,
>As an sql novice I have created some Maintenance Plans which seemed to work
>ok except for integrity checks. As I can read from the logs they could'n be
>executed because the db had to be in Single-User. Ok got that.
>But the problem is that other servers are running some foreground &
>background programs that connect to the sql svr. When I closed the
>connections on our sql, the other server keeps connecting back resulting in
>the fact I couldn't close the connections. This weekend when I rebooted the
>other servers they lost connection to sql resulting in 0 connections to the
>db.
>How can this be done then, if remote servers keep connecting ? Is there a
>safe way to get my db's in single user ?
>I presume my test by closing the active connections to the sql via Ent. Mgr
>was also not a good thing to do?
>Rgds,
>T.
>
>
|||"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:4h5vk0l1mvrer6h775b6dgb2slkg5441r0@.4ax.com...
> The way to handle it is to remove the check for the option
> to repair errors on your integrity checks in the maintenance
> plan. You don't really want automatic repairs happening if
> your dbcc checkdbs fail. You would want to intervene
> yourself, determine what caused the consistency error, fix
> the underlying problem and then take whatever course of
> action based on what the underlying problem is.
> -Sue
>
Ok Sue, I will do so. Thank you for your help!!
Rgds,
T.
Thursday, March 8, 2012
Connection to sql server 2000
webpage for user to use as front end application ? Pls advise. Thanks
Rgds
DanielYou have to do some coding in the coding language of your choice.
-jens Suessmeyer.|||What language/ platform are you using?
--
Jack Vamvas
__________________________________________________ ________________
Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
New article by Jack Vamvas - SQL and Markov Chains -
www.ciquery.com/articles/art_04.asp
<Danieltbt05@.gmail.com> wrote in message
news:1138725750.293962.191770@.g49g2000cwa.googlegr oups.com...
> Hi, I've created database in sql server 2000 but how to i link it to
> webpage for user to use as front end application ? Pls advise. Thanks
> Rgds
> Daniel|||Now using SQL Server 2000 on win2003 and using QA/enterprise manager
to connect in intranet now. Is it normal for user to connect to sql
server using QA or enterprise manager ? I mean do you consider it user
friendly ? So i intend to design it to become a webpage for end user to
view the data. I've been using DAO or ADO quite some time ago. is it ok
? what abt ODBC ? what do you recommend ? pls advise. thanks
Rgds
Daniel
Jack Vamvas wrote:
> What language/ platform are you using?
> --
> Jack Vamvas
> __________________________________________________ ________________
> Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> New article by Jack Vamvas - SQL and Markov Chains -
> www.ciquery.com/articles/art_04.asp
> <Danieltbt05@.gmail.com> wrote in message
> news:1138725750.293962.191770@.g49g2000cwa.googlegr oups.com...
> > Hi, I've created database in sql server 2000 but how to i link it to
> > webpage for user to use as front end application ? Pls advise. Thanks
> > Rgds
> > Daniel|||ya correct but i not sure which language should i use. ADO, DAO or ODBC
? pls advise. Thanks|||(Danieltbt05@.gmail.com) writes:
> Now using SQL Server 2000 on win2003 and using QA/enterprise manager
> to connect in intranet now. Is it normal for user to connect to sql
> server using QA or enterprise manager ? I mean do you consider it user
> friendly ? So i intend to design it to become a webpage for end user to
> view the data. I've been using DAO or ADO quite some time ago. is it ok
> ? what abt ODBC ? what do you recommend ? pls advise. thanks
End-users normally don't use tools like Query Analyzer or Enterprise
Manager, but rather they access the database through an application
or a web page.
If I understand things right, you are looking into the latter. There
are several tools on the market: ASP, ASP .Net, Cold Fusion, and
probably more. I don't know any of them myself. Once you've chosen
a tool for your web site, then you have more or less also settled on
a client API. For ASP that would be ADO, for ASP .Net that would
be ADO .Net. (Which is very different from ADO, and also a lot better.)
I don't know if DAO can connect to SQL Server, but anyway that's really
old stuff that you should not use.
Sorry if the answer is not crystal clear, but this is not really the
best newsgrop to ask questions about building a web site.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Erland, if i want to build it into like VB do i have to use ASP or
others tools u mentioned ? Only ADO.net can be used in webpage ? DAO or
ADO cannot be used ? Anywhere can learn step by step of it whether
build into VB app. or webpage ? Thanks
Rgds
Daniel|||(Danieltbt05@.gmail.com) writes:
> Erland, if i want to build it into like VB do i have to use ASP or
> others tools u mentioned ? Only ADO.net can be used in webpage ? DAO or
> ADO cannot be used ? Anywhere can learn step by step of it whether
> build into VB app. or webpage ? Thanks
As I said, this is not really the right place to ask question on how to
build web pages.
But, no, ADO .Net is not sufficient. ADO .Net - as well as ADO and DAO - is
a client API for access data sources. For building a web site, you can
use ASP. Net or ASP. I believe that they use some variation of VB script,
but exactly what this ASP thing is, I'm quite in the dark myself. I would
recommend you to look for newsgroups with "aspnet" in the name.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
Connection to Oracle
I have created reports in SQl Server 2005 Reporting Services using an Oracle Data Sources. When I Preview the report in VS 2005, It runs fine but when I deploy it, it fails to make a coonection to the oracle data source.
Reports off the SQL Server Data Sources arerunning fine.
Can any one out there help me out on this. I will really appreaciate.
Regards,
Sam.
Assuming Oracle's client software is installed on the report server machine, it is most likely a directory permissions issue with Oracle's client software installation - see http://support.microsoft.com/?kbid=870668
-- Robert
|||Hi Robert,
Thanks for the guideline but I have done what is required as stated in the link and I still get the same error.
|||Do you deploy the reports on the same PC? Maybe your Server has a different Oracle installation or tnsnames.ora..For TESTING!! you could give "everyone" read/execute -access to your oracle-directory to eliminate permission-problems.
|||
It seems Permissions were my problem.
I assigned read/execute access to each of the Oracle Home Directory Folders and Subfolder to Network Service and it sorted out the problem
Thanks for all the Advise.
|||Hi there,
I have the same issue as described earlier in this thread. I have applied the security (Read and Execute) to all known Oracle instance directories to the Network Service account (which is being used for starting the Reporting Service) and I am still receiving the following error message:
I'm trying to use the Oracle instant client on my report server. it is setup correctly and I can connect via SQL+. I've modified reporting services to use Network Service as account for both windows and web services. And I've set permission on the OIC directory appropriately according to MS guidelines.
But same error, will not connect to the Oracle data source.
Connection to Oracle
Hi,
I have created a simple report that reads data from Oracle within Visual Studio. I have no problem with previewing the report within Visual Studio. When I deploy the report to the Report Server (same machine) and try to open the report through Report Manager, I get the following error message:
I am aware of the following issue that requires extra security to be assigned to the Oracle directories: http://support.microsoft.com/Default.aspx?kbid=870668
Even after applying the Read/Execute access to the Network Service account that is running the Reporting Service, I still get the error message.
Can anyone help me with the debugging of this issue?
Thanks,
Ben
To me, that error could mean a couple of things, not necessarily just read/execute problems.
Is the version of Oracle client equal to or greater than 8i? Do you have your Oracle homes set correctly (especially as you may have multiple clients installed on the same machine)? Did you propagate the read/execute permissions down the directory structure, including to the <oracle install dir>/network/admin folder and its contents? What account is IIS running under? Does your tns file have the correct entry in it? And lastly, are you running Win2K3 or a prior version - IIRC the NETWORKSERVICE account only started being used from 2K3 onwards, prior to that there may have been other identities that IIS and SSRS run under.
HTH!
|||Try updating the oracle client to 10.2.01|||Hi sluggy,
I am currently running Windows XP Prof.
On this machine, I have 3 different Oracle clients (8.1, 9.2, and 10). Read/Execute has been propagated to all 3 directories starting from each of the Oracle_Home directory.
IIS (World Wide Web Publishing Service) is running under Local System.
TNS is correct. Both Visual Studio and the Report Server are running on the same machine.
How can you tell which Oracle Client the Reporting Service will use? I tried to direct it to Oracle 9.2 by modifying the both System Variables (ORACLE_HOME) and the registry (My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ORACLE_HOME=C:\ORACLE\ORA92). Neither of these seems to work.
Thanks,
Ben
|||Hi ghw123,
I currently have Oracle Client 10.2.1 on the machine. Unfortunately, I am not sure how to force the Report Service to use this client over the 2 clients that I have on the machine.
Any suggestions?
Thanks,
Ben
|||Make sure that the 10.2.01 client is listed first in the local enviroment variable 'Path'|||Hi ghw123,
Thanks for your help. I think my problem is related to Oracle client installation.
I have reinstalled everything on a separate machine and everything works fine when I apply the proper Read/Exec rights for the account running the Reporting Service.
Thanks,
Ben
Connection to Oracle
I have created reports in SQl Server 2005 Reporting Services using an Oracle Data Sources. When I Preview the report in VS 2005, It runs fine but when I deploy it, it fails to make a coonection to the oracle data source.
Reports off the SQL Server Data Sources arerunning fine.
Can any one out there help me out on this. I will really appreaciate.
Regards,
Sam.
Assuming Oracle's client software is installed on the report server machine, it is most likely a directory permissions issue with Oracle's client software installation - see http://support.microsoft.com/?kbid=870668
-- Robert
|||Hi Robert,
Thanks for the guideline but I have done what is required as stated in the link and I still get the same error.
|||Do you deploy the reports on the same PC? Maybe your Server has a different Oracle installation or tnsnames.ora..For TESTING!! you could give "everyone" read/execute -access to your oracle-directory to eliminate permission-problems.
|||
It seems Permissions were my problem.
I assigned read/execute access to each of the Oracle Home Directory Folders and Subfolder to Network Service and it sorted out the problem
Thanks for all the Advise.
|||Hi there,
I have the same issue as described earlier in this thread. I have applied the security (Read and Execute) to all known Oracle instance directories to the Network Service account (which is being used for starting the Reporting Service) and I am still receiving the following error message:
I'm trying to use the Oracle instant client on my report server. it is setup correctly and I can connect via SQL+. I've modified reporting services to use Network Service as account for both windows and web services. And I've set permission on the OIC directory appropriately according to MS guidelines.
But same error, will not connect to the Oracle data source.
Connection to Oracle
I have created reports in SQl Server 2005 Reporting Services using an Oracle Data Sources. When I Preview the report in VS 2005, It runs fine but when I deploy it, it fails to make a coonection to the oracle data source.
Reports off the SQL Server Data Sources arerunning fine.
Can any one out there help me out on this. I will really appreaciate.
Regards,
Sam.
Assuming Oracle's client software is installed on the report server machine, it is most likely a directory permissions issue with Oracle's client software installation - see http://support.microsoft.com/?kbid=870668
-- Robert
|||Hi Robert,
Thanks for the guideline but I have done what is required as stated in the link and I still get the same error.
|||Do you deploy the reports on the same PC? Maybe your Server has a different Oracle installation or tnsnames.ora..For TESTING!! you could give "everyone" read/execute -access to your oracle-directory to eliminate permission-problems.
|||
It seems Permissions were my problem.
I assigned read/execute access to each of the Oracle Home Directory Folders and Subfolder to Network Service and it sorted out the problem
Thanks for all the Advise.
|||Hi there,
I have the same issue as described earlier in this thread. I have applied the security (Read and Execute) to all known Oracle instance directories to the Network Service account (which is being used for starting the Reporting Service) and I am still receiving the following error message:
I'm trying to use the Oracle instant client on my report server. it is setup correctly and I can connect via SQL+. I've modified reporting services to use Network Service as account for both windows and web services. And I've set permission on the OIC directory appropriately according to MS guidelines.
But same error, will not connect to the Oracle data source.
Connection to Oracle
I have created reports in SQl Server 2005 Reporting Services using an Oracle Data Sources. When I Preview the report in VS 2005, It runs fine but when I deploy it, it fails to make a coonection to the oracle data source.
Reports off the SQL Server Data Sources arerunning fine.
Can any one out there help me out on this. I will really appreaciate.
Regards,
Sam.
Assuming Oracle's client software is installed on the report server machine, it is most likely a directory permissions issue with Oracle's client software installation - see http://support.microsoft.com/?kbid=870668
-- Robert
|||Hi Robert,
Thanks for the guideline but I have done what is required as stated in the link and I still get the same error.
|||Do you deploy the reports on the same PC? Maybe your Server has a different Oracle installation or tnsnames.ora..For TESTING!! you could give "everyone" read/execute -access to your oracle-directory to eliminate permission-problems.
|||
It seems Permissions were my problem.
I assigned read/execute access to each of the Oracle Home Directory Folders and Subfolder to Network Service and it sorted out the problem
Thanks for all the Advise.
|||Hi there,
I have the same issue as described earlier in this thread. I have applied the security (Read and Execute) to all known Oracle instance directories to the Network Service account (which is being used for starting the Reporting Service) and I am still receiving the following error message:
I'm trying to use the Oracle instant client on my report server. it is setup correctly and I can connect via SQL+. I've modified reporting services to use Network Service as account for both windows and web services. And I've set permission on the OIC directory appropriately according to MS guidelines.
But same error, will not connect to the Oracle data source.
Saturday, February 25, 2012
Connection Strings
I have created a SSIS package, and got it to perform as I want.
I am having a problem though with connecting to my data source (OLE DB Source) using SQL Server Authentication.
If I use Integrated security, I have no problems. If I use SQL Server Authentication, I get errors.
Here is the connection string that works:
Provider=SQLNCLI.1;Data Source=.\SqlExpress;Integrated Security=SSPI;Initial Catalog=MyDataBase
Here is the connection string that fails:
Provider=SQLNCLI.1;Data Source=.\SqlExpress;Persist Security Info=True;Password=**********;User ID=myUserid;Initial Catalog=MyDataBase
The strange thing is that when I use the Connection Manager dialog screen and click on "Test Connection", I get the response that the connection succeeded. It is only when I try to run the task that I get an error.
Here is the error I am getting:
[OLE DB Source [1]] Error: The AcquireConnection method call to the connection manager "MyDataBase" failed with error code 0xC0202009.
[DTS.Pipeline] Error: component "MyDataBase" (1) failed validation and returned error code 0xC020801C.
I have eliminated the obvious errors (incorrect Userid or password). Also, I am unable to use Integrated Security as this package needs to be distributed to various systems that may or may not be on our company's primary domain.
It seems I am missing something really basic here, but am not seeing it.
Any thoughts?
Has this ever worked for you? Are you able to create a brand new package and it still fails? Are you using package configurations?|||Has this ever worked for you? Yes, using integrated security
Are you able to create a brand new package and it still fails? No, actually I tried a new simple package, and it works.
Are you using package configurations? No
I think the key here is your second point. I created a new package, and the connection now works. So, the question is how do I fix my original package? I'm not really thrilled about creating a brand new package being that this one is quite complicated.
Suggestions?
|||Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.|||WRBehning,
Welcome to the new world of SSIS! I have had similar problems, especially when you copy and paste items. Basically I think the internal Ids in SSIS get messed up somehow. Alot of times if you delete and re-add an item it fixes the problem. Doesn't give me great confidence when an "enterprise solution" has so many strange problems. Good Luck! (to us all)
|||WRBehning wrote:
Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.
If you have a RFE (Request for Enhancement) then file it at http://connect.microsoft.com with a detailed write-up.
Only thru doing this will SSIS get closer to being the product that people want it to be.
-Jamie
|||
WRBehning wrote:
Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.
Can you explain exactly what the problem was in the original. Its not clear from this?
If its something that people need to know then I'd like to add it here: http://blogs.conchango.com/jamiethomson/archive/2006/10/18/SSIS_3A00_-Random-information-for-beginners.aspx
Thanks
-Jamie
|||The issue I had was that I created the SSIS package using Windows Authentication for my OLEDB connections. After I had completed the package, I tried to switch to SQL Server Authentication and even though the "Test Connection" responded with "Test Connection Succeeded", the package would not run. Finally, like I stated earlier, I created a new package, using Sql Server Authentication from the beginning, and the issue was resloved.|||
WRBehning wrote:
The issue I had was that I created the SSIS package using Windows Authentication for my OLEDB connections. After I had completed the package, I tried to switch to SQL Server Authentication and even though the "Test Connection" responded with "Test Connection Succeeded", the package would not run. Finally, like I stated earlier, I created a new package, using Sql Server Authentication from the beginning, and the issue was resloved.
That's worrying if it didn't work. However I have previously had no problems with changing connection strings (for that is what we're talking about here).
One thing that can cause problems is if (for example) the ServerName property doesn't marry up with the server name that you are setting in the ConenctioNString property although in your case the only difference is in authentication mode so I shouldn't expect it to be a problem.
I've also tried your repro steps as above and didn't experience any problems.
What version/service pack are you on?
-Jmie
|||
Here you go...
A couple of things I should mention.
I tried deleting and re-creating the connections and this did not solve the problem.
The connections are connecting to SQL Express, not standard SQL, though I do not see where this would be a consideration.
SQLExpress (SQL Server 9.0.2047)
Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: Professional
Microsoft Visual Basic 2005 77626-009-0000007-41520
Microsoft Visual Basic 2005
Microsoft Visual C# 2005 77626-009-0000007-41520
Microsoft Visual C# 2005
Microsoft Visual C++ 2005 77626-009-0000007-41520
Microsoft Visual C++ 2005
Microsoft Visual J# 2005 77626-009-0000007-41520
Microsoft Visual J# 2005
Microsoft Visual Web Developer 2005 77626-009-0000007-41520
Microsoft Visual Web Developer 2005
Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005
SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00
SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00
SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00
WRBehning wrote:
Here you go...
A couple of things I should mention.
I tried deleting and re-creating the connections and this did not solve the problem.
The connections are connecting to SQL Express, not standard SQL, though I do not see where this would be a consideration.
SQLExpress (SQL Server 9.0.2047)
Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727Installed Edition: Professional
Microsoft Visual Basic 2005 77626-009-0000007-41520
Microsoft Visual Basic 2005Microsoft Visual C# 2005 77626-009-0000007-41520
Microsoft Visual C# 2005Microsoft Visual C++ 2005 77626-009-0000007-41520
Microsoft Visual C++ 2005Microsoft Visual J# 2005 77626-009-0000007-41520
Microsoft Visual J# 2005Microsoft Visual Web Developer 2005 77626-009-0000007-41520
Microsoft Visual Web Developer 2005Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005
SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00
Seems we're on the same. Strange.
Oh well. Let's chalk it up to experience. If it happens again, let us know.
Thanks
Jamie
|||
I am experiencing the same behaviour.
The package was first created using EncryptWithUserKey setting, and the connection credentials was for a trusted connection to a SQL Server.
We changed the package security to use EncryptWithPassword, and the connection credentials stayed the same and continued to work properly.
When we changed the connection credentials to use a Standard SQL login, I would set the login and password and check the "Remember password" option. The Test Connection button was successful. Then after closing the connection manager properties, I would immediately reopen the properties and the password was gone, but the checkbox was still there, and the Test Connection would fail.
Mike
Connection Strings
I have created a SSIS package, and got it to perform as I want.
I am having a problem though with connecting to my data source (OLE DB Source) using SQL Server Authentication.
If I use Integrated security, I have no problems. If I use SQL Server Authentication, I get errors.
Here is the connection string that works:
Provider=SQLNCLI.1;Data Source=.\SqlExpress;Integrated Security=SSPI;Initial Catalog=MyDataBase
Here is the connection string that fails:
Provider=SQLNCLI.1;Data Source=.\SqlExpress;Persist Security Info=True;Password=**********;User ID=myUserid;Initial Catalog=MyDataBase
The strange thing is that when I use the Connection Manager dialog screen and click on "Test Connection", I get the response that the connection succeeded. It is only when I try to run the task that I get an error.
Here is the error I am getting:
[OLE DB Source [1]] Error: The AcquireConnection method call to the connection manager "MyDataBase" failed with error code 0xC0202009.
[DTS.Pipeline] Error: component "MyDataBase" (1) failed validation and returned error code 0xC020801C.
I have eliminated the obvious errors (incorrect Userid or password). Also, I am unable to use Integrated Security as this package needs to be distributed to various systems that may or may not be on our company's primary domain.
It seems I am missing something really basic here, but am not seeing it.
Any thoughts?
Has this ever worked for you? Are you able to create a brand new package and it still fails? Are you using package configurations?|||Has this ever worked for you? Yes, using integrated security
Are you able to create a brand new package and it still fails? No, actually I tried a new simple package, and it works.
Are you using package configurations? No
I think the key here is your second point. I created a new package, and the connection now works. So, the question is how do I fix my original package? I'm not really thrilled about creating a brand new package being that this one is quite complicated.
Suggestions?
|||Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.|||WRBehning,
Welcome to the new world of SSIS! I have had similar problems, especially when you copy and paste items. Basically I think the internal Ids in SSIS get messed up somehow. Alot of times if you delete and re-add an item it fixes the problem. Doesn't give me great confidence when an "enterprise solution" has so many strange problems. Good Luck! (to us all)
|||WRBehning wrote:
Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.
If you have a RFE (Request for Enhancement) then file it at http://connect.microsoft.com with a detailed write-up.
Only thru doing this will SSIS get closer to being the product that people want it to be.
-Jamie
|||
WRBehning wrote:
Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.
Can you explain exactly what the problem was in the original. Its not clear from this?
If its something that people need to know then I'd like to add it here: http://blogs.conchango.com/jamiethomson/archive/2006/10/18/SSIS_3A00_-Random-information-for-beginners.aspx
Thanks
-Jamie
|||The issue I had was that I created the SSIS package using Windows Authentication for my OLEDB connections. After I had completed the package, I tried to switch to SQL Server Authentication and even though the "Test Connection" responded with "Test Connection Succeeded", the package would not run. Finally, like I stated earlier, I created a new package, using Sql Server Authentication from the beginning, and the issue was resloved.|||
WRBehning wrote:
The issue I had was that I created the SSIS package using Windows Authentication for my OLEDB connections. After I had completed the package, I tried to switch to SQL Server Authentication and even though the "Test Connection" responded with "Test Connection Succeeded", the package would not run. Finally, like I stated earlier, I created a new package, using Sql Server Authentication from the beginning, and the issue was resloved.
That's worrying if it didn't work. However I have previously had no problems with changing connection strings (for that is what we're talking about here).
One thing that can cause problems is if (for example) the ServerName property doesn't marry up with the server name that you are setting in the ConenctioNString property although in your case the only difference is in authentication mode so I shouldn't expect it to be a problem.
I've also tried your repro steps as above and didn't experience any problems.
What version/service pack are you on?
-Jmie
|||
Here you go...
A couple of things I should mention.
I tried deleting and re-creating the connections and this did not solve the problem.
The connections are connecting to SQL Express, not standard SQL, though I do not see where this would be a consideration.
SQLExpress (SQL Server 9.0.2047)
Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: Professional
Microsoft Visual Basic 2005 77626-009-0000007-41520
Microsoft Visual Basic 2005
Microsoft Visual C# 2005 77626-009-0000007-41520
Microsoft Visual C# 2005
Microsoft Visual C++ 2005 77626-009-0000007-41520
Microsoft Visual C++ 2005
Microsoft Visual J# 2005 77626-009-0000007-41520
Microsoft Visual J# 2005
Microsoft Visual Web Developer 2005 77626-009-0000007-41520
Microsoft Visual Web Developer 2005
Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005
SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00
SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00
SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00
WRBehning wrote:
Here you go...
A couple of things I should mention.
I tried deleting and re-creating the connections and this did not solve the problem.
The connections are connecting to SQL Express, not standard SQL, though I do not see where this would be a consideration.
SQLExpress (SQL Server 9.0.2047)
Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727Installed Edition: Professional
Microsoft Visual Basic 2005 77626-009-0000007-41520
Microsoft Visual Basic 2005Microsoft Visual C# 2005 77626-009-0000007-41520
Microsoft Visual C# 2005Microsoft Visual C++ 2005 77626-009-0000007-41520
Microsoft Visual C++ 2005Microsoft Visual J# 2005 77626-009-0000007-41520
Microsoft Visual J# 2005Microsoft Visual Web Developer 2005 77626-009-0000007-41520
Microsoft Visual Web Developer 2005Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005
SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00
Seems we're on the same. Strange.
Oh well. Let's chalk it up to experience. If it happens again, let us know.
Thanks
Jamie
|||
I am experiencing the same behaviour.
The package was first created using EncryptWithUserKey setting, and the connection credentials was for a trusted connection to a SQL Server.
We changed the package security to use EncryptWithPassword, and the connection credentials stayed the same and continued to work properly.
When we changed the connection credentials to use a Standard SQL login, I would set the login and password and check the "Remember password" option. The Test Connection button was successful. Then after closing the connection manager properties, I would immediately reopen the properties and the password was gone, but the checkbox was still there, and the Test Connection would fail.
Mike
Friday, February 24, 2012
Connection string problem
Hi people,
I have my web application running on my machine and it works on the current machine where I have created the project when I type localhost on the web browser. I tried running the application from another machine within the same network by typing the IP address of the machine where my asp.net project is located, the application works, but SQL Server wouldn't allow connection to be made when I start calling data from the database. I have set Impersonate="true" in the web.config file. Am I doing something wrong here?
Here's the configuration on the web.config file
<identityimpersonate="true"/>
<appSettings>
<addkey="Connection"
value="Server=SQLOLEDB.1;Data Source=SQLServer;Initial Catalog=myDatabase;Trusted_Connection=True;"/>
</appSettings>
Please help....
Kero
I think you may have to use Sql Server authentication and pass a userid/pwd pair in your conn string.
|||Thanks ChicoUser,
I have sort out my impersonate problem by following one of the tutorials from microsoft website. I have set up a Customer user instead using Aspnet account on the machine and given appropriate permissions to access the files. In the Web.config file I have added impersonate =true and provided username and password which allows the created account to get access to my SQL SERVER. It's working now.
kero :)
Sunday, February 19, 2012
Connection string for reporting model
Hi,
I've just created a reporting model to use with my reports.
I have deployed the model to my localhost reporting server.
The name of my model is : mod_agentreporting
Can someone give me the right connection string that i have to use ?
Is there any advantage for using reporting models as datasources for reports
or a shared data sources ?
Thanks already in advance for your remarks.
Vincent
http://msdn2.microsoft.com/en-us/library/ms345238.aspx
btw, that's the top result you get by googling:
site:msdn2.microsoft.com +"report model" +"connection string"
Connection string Error
Hello I need some help please.
I created a connection string in my web config. I then tried to call it in one of my c# pages but I get a "System.InvalidOperationException: Instance failure" every time I run it.
Please review my code and let me know what I am doing wrong.
Thank you in advance for all the help
Web Config
<
appSettings><
addkey="AVConnection"value="Server=Server; Database=DB; User ID=sa; Password=PWD" /></appSettings>
//////calling connection and running a simple SQL statment///////
protected void Page_Load(object sender, EventArgs e)
{
string ConnApp;
ConnApp = System.Configuration.ConfigurationManager.AppSettings["AVConnection"];
Response.Write(ConnApp);//the string is being passed this far
SqlConnection objConn = new SqlConnection(ConnApp);
SqlCommand sqlCMD = new SqlCommand("Select * FROM Employee", objConn);
objConn.Open();//this is where the error occures
SqlDataReader objRdr = sqlCMD.ExecuteReader();
Repeater1.DataSource = objRdr;
Repeater1.DataBind();
objConn.Close();
objRdr.Close();
}
ERROR PAGE
Line 29: SqlCommand sqlCMD = new SqlCommand("Select * FROM Employee", objConn);
Line 30:
Line 31: objConn.Open();
Line 32: SqlDataReader objRdr = sqlCMD.ExecuteReader();
Line 33: Repeater1.DataSource = objRdr;
[InvalidOperationException: Instance failure.]
System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +683775
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +359
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
employeelist.Page_Load(Object sender, EventArgs e) in c:\Inetpub\wwwroot\FAUAV\employeelist.aspx.cs:31
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +34
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061
Don't know how much of a difference this might make, but have you tried putting the connection string in the connectionStrings node of web.config? If not you might as well do that as that's why it exists.
Ryan
|||I tried that but it did not change anything.
Thanks for the advice
Sunday, February 12, 2012
Connection Problems
Hi,
I am new to SQL Server 2005 but have a pretty good understanding of 2000, but I am struggling with connections! I have created a .Net Windows application (installed on an XP box) that should talk to a SQL Server 2005 database which is installed on a 2003 server. The desktop app is installed is in one domain (DOM1), and the SQL server 2005 is in another domain (DOM2). I have created a active directory user in DOM2 which will be a service account which manages the connections between the app and the db. I am using the following connection string:-
Server=ZZLUKGKK1M1J\INST2005;Database=PublicationWizard;User ID=DOM2\zzPubWizardDBUser;Password=password;Network Library=DBMSSOCN;Trusted_Connection=False;
When I try and connect an error is thrown, and I get the following in the SQL log
Error: 18456, Severity: 14, State: 5.
Login failed for user 'DOM2\zzPubWizardDBUser'. [CLIENT: 10.80.150.121]
I know that the user name and password are correct and that it exists with the DOM2 domain. I have also included "Network Library=DBMSSOCN" as I was getting problems with it trying to connect via Named Pipes. As I am really used to SQL Server 2000 I might be missing something obvious but I cannot for the life of me figure this out.
Any suggestions will be most welcome as this is driving me nuts
by setting trusted_connection=false you are implying you wish to use SQL Authentication not Windows. Thus your user must be created on the destination sql server and sql authentication must be enabled on the server itself.Friday, February 10, 2012
Connection Problem VB.Net 2003 to SQL 2000
I have a webservice created in VB.NET 2003 hosted on a Windows 2003
server. This service inserts data into a SQL Server 2000 database also
hosted on a Windows 2003 server. The webserver is in a closed DMZ and
the Database Sever is on the internal network. The firewall is
configured to allow traffic to the DB Server on port 1433. Form the
outside world the request get passed throught to the webserver as it
should be. However when the request from the webserver is passed to
the DB server the request on port 1433 is being passed but two
requests one on port 137 and one on port 445 are being dropped. Can
anyone tell me why a simple sqlCommand.ExecuteNonQuery() would need to
use 137 and 445?
Many thanks
FredFred,
These articles don't apply directly to your situation, but they do explain
those additional ports:
http://support.microsoft.com/kb/841251/
http://support.microsoft.com/kb/841249/
Kerry Moorman
"Fred" wrote:
> Hi,
> I have a webservice created in VB.NET 2003 hosted on a Windows 2003
> server. This service inserts data into a SQL Server 2000 database also
> hosted on a Windows 2003 server. The webserver is in a closed DMZ and
> the Database Sever is on the internal network. The firewall is
> configured to allow traffic to the DB Server on port 1433. Form the
> outside world the request get passed throught to the webserver as it
> should be. However when the request from the webserver is passed to
> the DB server the request on port 1433 is being passed but two
> requests one on port 137 and one on port 445 are being dropped. Can
> anyone tell me why a simple sqlCommand.ExecuteNonQuery() would need to
> use 137 and 445?
> Many thanks
> Fred
>
Connection Problem VB.Net 2003 to SQL 2000
I have a webservice created in VB.NET 2003 hosted on a Windows 2003
server. This service inserts data into a SQL Server 2000 database also
hosted on a Windows 2003 server. The webserver is in a closed DMZ and
the Database Sever is on the internal network. The firewall is
configured to allow traffic to the DB Server on port 1433. Form the
outside world the request get passed throught to the webserver as it
should be. However when the request from the webserver is passed to
the DB server the request on port 1433 is being passed but two
requests one on port 137 and one on port 445 are being dropped. Can
anyone tell me why a simple sqlCommand.ExecuteNonQuery() would need to
use 137 and 445?
Many thanks
Fred
Fred,
These articles don't apply directly to your situation, but they do explain
those additional ports:
http://support.microsoft.com/kb/841251/
http://support.microsoft.com/kb/841249/
Kerry Moorman
"Fred" wrote:
> Hi,
> I have a webservice created in VB.NET 2003 hosted on a Windows 2003
> server. This service inserts data into a SQL Server 2000 database also
> hosted on a Windows 2003 server. The webserver is in a closed DMZ and
> the Database Sever is on the internal network. The firewall is
> configured to allow traffic to the DB Server on port 1433. Form the
> outside world the request get passed throught to the webserver as it
> should be. However when the request from the webserver is passed to
> the DB server the request on port 1433 is being passed but two
> requests one on port 137 and one on port 445 are being dropped. Can
> anyone tell me why a simple sqlCommand.ExecuteNonQuery() would need to
> use 137 and 445?
> Many thanks
> Fred
>
Connection problem to Informix from SQL Server 2005 with Unicode data
DB_LOCALE in Informix DB is en_US.utf8 (en_US.57372).
First, I created DSN to Informix. Then tried to get data with WinSql
tool and it works fine.
But when I created linked server in SQL Server 2005 I have problems
with languages other than English.
I get a string like:
' -|工 1/4 1/43/4
It seems to me that SQL Server splits 2-byte characters in 2 1-byte
characters.
If in options of linked server we set Collation Name to exact
language
we want --then string data will be correct (of course only of
language that we choose).
Do you have any suggestions???
P.S. I don't want to use SSIS (DTS) for extraction from Informix DB(denis.carabadjac@.gmail.com) writes:
Quote:
Originally Posted by
I have Informix 9.4TC6 and SQL Server 2005.
DB_LOCALE in Informix DB is en_US.utf8 (en_US.57372).
>
First, I created DSN to Informix. Then tried to get data with WinSql
tool and it works fine.
But when I created linked server in SQL Server 2005 I have problems
with languages other than English.
I get a string like:
' ?-|工 1/4 1/4?3/4
>
It seems to me that SQL Server splits 2-byte characters in 2 1-byte
characters.
If in options of linked server we set Collation Name to exact
language
we want --then string data will be correct (of course only of
language that we choose).
>
Do you have any suggestions???
This looks like a difficult case. SQL Server does not support UTF-8.
You can set a server option, "Collation name" as you found, but that
should be a collation that exists in SQL Server, but SQL Server does
not have any UTF-8 collations.
I have no experience with Informix, but it seems to me that either you
need to find a way to convert UTF-8 to UTF-16, or you will have to
go over the file system. The tool BCP as well as the command BULK INSERT
is able to handle files with UTF-8 data.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
Connection problem SQL Server 2005
After searching the Internet and this forum a still have a question.
I'm struggling already a few days with the following problem
I created a site in VS2005 on a virtual directory (http://server01/test) on a local network app server with also SQL 2005 installed.
The problem seems to occur with the SQL server. When I open the site somewhere within my local network it all works fine.
It's should however also be accessibly from a public ip address. When I access a normal html/aspx page without any SQL content behind it works ok from outside, but when I try to access a page with SQL content it just hangs (time out). In the profiler of SQL server I see that it's accessing the table to get the content with the correct SQL userid. I checked the settings of SQL server and "remote connections" is allowed and named pipes is enabled.
Any help where to investigate further would be appreciated!
<configurationxmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
<appSettings/>
<connectionStrings>
<addname="testConnectionString"connectionString="Data Source=SERVER01;Initial Catalog=database_name;User ID=User_;Password=Pass_;Encrypt=False;Context Connection=False" providerName="System.Data.SqlClient" />
</connectionStrings>
<system.web>
</system.web>
Are you sure you want to connect to SQL Server with named pipes protocol? Then make sure from the client machine you can pass the Windows Authentication on the SQL server machine. In command prompt execute the following commands to test IPC sharing:
net view\\servername
net use\\servername\IPC$
No i'm not wan't to connect via named pipes, but just was out off idea's so tried everything.
SQL works fine now via remote, but seems that i have another issue now. Don't think it in the right place now in this forum but maybe you have an answer.
As i mentioned everything works fine via the local network, but when i try to access the pages from an outside connection (public IP adress) i got strange errors.
2006-05-14 10:33:56 W3SVC1 192.168.1.6 GET /bo - 80 - 192.168.1.10 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+1.0.3705;+InfoPath.1;+.NET+CLR+2.0.50727) 301 0 0
2006-05-14 10:33:59 W3SVC1 192.168.1.6 GET /bo/default.aspx - 80 - 192.168.1.10 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+1.0.3705;+InfoPath.1;+.NET+CLR+2.0.50727) 200 0 0
2006-05-14 10:33:59 W3SVC1 192.168.1.6 GET /bo/css/lightbox.css - 80 - 192.168.1.10 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+1.0.3705;+InfoPath.1;+.NET+CLR+2.0.50727) 200 0 0
2006-05-14 10:33:59 W3SVC1 192.168.1.6 GET /bo/images/5.jpg - 80 - 192.168.1.10 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+1.0.3705;+InfoPath.1;+.NET+CLR+2.0.50727) 200 0 0
2006-05-14 10:33:59 W3SVC1 192.168.1.6 GET /bo/css/site.css - 80 - 192.168.1.10 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+1.0.3705;+InfoPath.1;+.NET+CLR+2.0.50727) 200 0 0
2006-05-14 10:33:59 W3SVC1 192.168.1.6 GET /bo/images/back.gif - 80 - 192.168.1.10 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+1.0.3705;+InfoPath.1;+.NET+CLR+2.0.50727) 200 0 0
2006-05-14 10:34:09 W3SVC1 192.168.1.6 GET /bo - 80 - 134.146.0.6 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322) 301 0 0
2006-05-14 10:34:37 W3SVC1 192.168.1.6 GET /bo/default.aspx - 80 - 134.146.0.6 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322) 200 0 1236
2006-05-14 10:34:41 W3SVC1 192.168.1.6 GET /bo/images/5.jpg - 80 - 134.146.0.6 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322) 200 0 64
2006-05-14 10:35:01 W3SVC1 192.168.1.6 GET /bo/images/5.jpg - 80 - 134.146.0.6 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322) 200 0 64
When i look in the Network Monitor log i see the from the local network i get a response to client "HTTP/1.1status code = 305 - Not modified"
But remote IP request get an: "HTTP/1.1status code = 206 - Partial Content" when the try to open a page with images (jpg /gif)
|||Sorry I have no idea on your new issue, and I think you'd better post the new issue to some other forum such asHttpHandlers and HttpModules