Showing posts with label sp1. Show all posts
Showing posts with label sp1. Show all posts

Tuesday, March 27, 2012

Cannot edit maintenance plans post SP2

I have some maintenance plans written for SQL Server 2005 SP1. After we
upgraded to SP2 I can no longer edit them. If I select the Maintneance Plans
node in Object Explorer and double click on any plan I get "Microsoft SQL
Server Management Studio is unable to load this document: One or more error
occured."
The popup message box says "Value cannot be null. Parameter name: component
(System.Design)"
Details are:"
Program Location:
at
System.ComponentModel.Design.DesignerHost.System.C omponentModel.Design.IDesignerHost.GetDesigner(ICo mponent component)
at
Microsoft.DataTransformationServices.VsIntegration .DtsDesignerService.OpenDesigner(String connectionString, Object connection, String objectUrn)
at
Microsoft.SqlServer.Management.DatabaseMaintenance .MaintDesignerMenuHandler.Invoke()"
I saw one post that sugget there is a fix that ought to be in cumulative
update package 4, but I can't see any items in that which match this problem.
The maintenance plans appear to run when called by the SQl Agent Jobs they
were initially set up with. However, I am calling one of them from another
Job and this has started throwing this error since SP2:
"Error: 2007-11-04 18:00:01.81 Code: 0xC0024104 Source: Reporting
Task for subplan-{03E683E8-5A40-4697-BF2F-E93EBA6E96E7} Description: The
Execute method on the task returned error code 0x80131904 (Conversion failed
when converting from a character string to uniqueidentifier.). The Execute
method must succeed<c/> and indicate the result using an "out" parameter.
End Error"
but when I went to look at the plan, I couldn't edit it!
Any advice on how to edit the maintenance plans or fix the second error
would be great.
Thanks,
Charles
Yes. From Help -> about:
"Microsoft SQL Server Management Studio9.00.3042.00
Microsoft Analysis Services Client Tools2005.090.3042.00
Microsoft Data Access Components (MDAC)2000.085.1117.00
(xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer6.0.2900.2180
Microsoft .NET Framework2.0.50727.832
Operating System5.1.2600"
"Tibor Karaszi" wrote:

> Did you install sp2 for the clients components (SSMS) on the machine where you try to edit the plan?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "CharlesB1" <CharlesB1@.discussions.microsoft.com> wrote in message
> news:CC70B322-EBCB-4D2E-B1DA-98AAEDDBF86A@.microsoft.com...
>
>
sql

Cannot edit maintenance plans post SP2

I have some maintenance plans written for SQL Server 2005 SP1. After we
upgraded to SP2 I can no longer edit them. If I select the Maintneance Plans
node in Object Explorer and double click on any plan I get "Microsoft SQL
Server Management Studio is unable to load this document: One or more error
occured."
The popup message box says "Value cannot be null. Parameter name: component
(System.Design)"
Details are:"
Program Location:
at
System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesi
gnerHost.GetDesigner(IComponent component)
at
Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDe
signer(String connectionString, Object connection, String objectUrn)
at
Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.
Invoke()"
I saw one post that sugget there is a fix that ought to be in cumulative
update package 4, but I can't see any items in that which match this problem
.
The maintenance plans appear to run when called by the SQl Agent Jobs they
were initially set up with. However, I am calling one of them from another
Job and this has started throwing this error since SP2:
"Error: 2007-11-04 18:00:01.81 Code: 0xC0024104 Source: Reporting
Task for subplan-{03E683E8-5A40-4697-BF2F-E93EBA6E96E7} Descriptio
n: The
Execute method on the task returned error code 0x80131904 (Conversion failed
when converting from a character string to uniqueidentifier.). The Execute
method must succeed<c/> and indicate the result using an "out" parameter.
End Error"
but when I went to look at the plan, I couldn't edit it!
Any advice on how to edit the maintenance plans or fix the second error
would be great.
Thanks,
CharlesDid you install sp2 for the clients components (SSMS) on the machine where y
ou try to edit the plan?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"CharlesB1" <CharlesB1@.discussions.microsoft.com> wrote in message
news:CC70B322-EBCB-4D2E-B1DA-98AAEDDBF86A@.microsoft.com...
>I have some maintenance plans written for SQL Server 2005 SP1. After we
> upgraded to SP2 I can no longer edit them. If I select the Maintneance Pla
ns
> node in Object Explorer and double click on any plan I get "Microsoft SQL
> Server Management Studio is unable to load this document: One or more erro
r
> occured."
> The popup message box says "Value cannot be null. Parameter name: componen
t
> (System.Design)"
> Details are:"
> Program Location:
> at
> System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDe
signerHost.GetDesigner(IComponent
> component)
> at
> Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.Open
Designer(String
> connectionString, Object connection, String objectUrn)
> at
> Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandle
r.Invoke()"
> I saw one post that sugget there is a fix that ought to be in cumulative
> update package 4, but I can't see any items in that which match this probl
em.
> The maintenance plans appear to run when called by the SQl Agent Jobs they
> were initially set up with. However, I am calling one of them from another
> Job and this has started throwing this error since SP2:
> "Error: 2007-11-04 18:00:01.81 Code: 0xC0024104 Source: Reporting
> Task for subplan-{03E683E8-5A40-4697-BF2F-E93EBA6E96E7} Descript
ion: The
> Execute method on the task returned error code 0x80131904 (Conversion fail
ed
> when converting from a character string to uniqueidentifier.). The Execute
> method must succeed<c/> and indicate the result using an "out" parameter.
> End Error"
> but when I went to look at the plan, I couldn't edit it!
> Any advice on how to edit the maintenance plans or fix the second error
> would be great.
> Thanks,
> Charles
>|||Yes. From Help -> about :
"Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00
(xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.832
Operating System 5.1.2600"
"Tibor Karaszi" wrote:

> Did you install sp2 for the clients components (SSMS) on the machine where
you try to edit the plan?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "CharlesB1" <CharlesB1@.discussions.microsoft.com> wrote in message
> news:CC70B322-EBCB-4D2E-B1DA-98AAEDDBF86A@.microsoft.com...
>
>

Cannot edit maintenance plans post SP2

I have some maintenance plans written for SQL Server 2005 SP1. After we
upgraded to SP2 I can no longer edit them. If I select the Maintneance Plans
node in Object Explorer and double click on any plan I get "Microsoft SQL
Server Management Studio is unable to load this document: One or more error
occured."
The popup message box says "Value cannot be null. Parameter name: component
(System.Design)"
Details are:"
Program Location:
at
System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.GetDesigner(IComponent component)
at
Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDesigner(String connectionString, Object connection, String objectUrn)
at
Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()"
I saw one post that sugget there is a fix that ought to be in cumulative
update package 4, but I can't see any items in that which match this problem.
The maintenance plans appear to run when called by the SQl Agent Jobs they
were initially set up with. However, I am calling one of them from another
Job and this has started throwing this error since SP2:
"Error: 2007-11-04 18:00:01.81 Code: 0xC0024104 Source: Reporting
Task for subplan-{03E683E8-5A40-4697-BF2F-E93EBA6E96E7} Description: The
Execute method on the task returned error code 0x80131904 (Conversion failed
when converting from a character string to uniqueidentifier.). The Execute
method must succeed<c/> and indicate the result using an "out" parameter.
End Error"
but when I went to look at the plan, I couldn't edit it!
Any advice on how to edit the maintenance plans or fix the second error
would be great.
Thanks,
CharlesDid you install sp2 for the clients components (SSMS) on the machine where you try to edit the plan?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"CharlesB1" <CharlesB1@.discussions.microsoft.com> wrote in message
news:CC70B322-EBCB-4D2E-B1DA-98AAEDDBF86A@.microsoft.com...
>I have some maintenance plans written for SQL Server 2005 SP1. After we
> upgraded to SP2 I can no longer edit them. If I select the Maintneance Plans
> node in Object Explorer and double click on any plan I get "Microsoft SQL
> Server Management Studio is unable to load this document: One or more error
> occured."
> The popup message box says "Value cannot be null. Parameter name: component
> (System.Design)"
> Details are:"
> Program Location:
> at
> System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.GetDesigner(IComponent
> component)
> at
> Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDesigner(String
> connectionString, Object connection, String objectUrn)
> at
> Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()"
> I saw one post that sugget there is a fix that ought to be in cumulative
> update package 4, but I can't see any items in that which match this problem.
> The maintenance plans appear to run when called by the SQl Agent Jobs they
> were initially set up with. However, I am calling one of them from another
> Job and this has started throwing this error since SP2:
> "Error: 2007-11-04 18:00:01.81 Code: 0xC0024104 Source: Reporting
> Task for subplan-{03E683E8-5A40-4697-BF2F-E93EBA6E96E7} Description: The
> Execute method on the task returned error code 0x80131904 (Conversion failed
> when converting from a character string to uniqueidentifier.). The Execute
> method must succeed<c/> and indicate the result using an "out" parameter.
> End Error"
> but when I went to look at the plan, I couldn't edit it!
> Any advice on how to edit the maintenance plans or fix the second error
> would be great.
> Thanks,
> Charles
>|||Yes. From Help -> About:
"Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00
(xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.832
Operating System 5.1.2600"
"Tibor Karaszi" wrote:
> Did you install sp2 for the clients components (SSMS) on the machine where you try to edit the plan?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "CharlesB1" <CharlesB1@.discussions.microsoft.com> wrote in message
> news:CC70B322-EBCB-4D2E-B1DA-98AAEDDBF86A@.microsoft.com...
> >I have some maintenance plans written for SQL Server 2005 SP1. After we
> > upgraded to SP2 I can no longer edit them. If I select the Maintneance Plans
> > node in Object Explorer and double click on any plan I get "Microsoft SQL
> > Server Management Studio is unable to load this document: One or more error
> > occured."
> >
> > The popup message box says "Value cannot be null. Parameter name: component
> > (System.Design)"
> > Details are:"
> > Program Location:
> >
> > at
> > System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.GetDesigner(IComponent
> > component)
> > at
> > Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDesigner(String
> > connectionString, Object connection, String objectUrn)
> > at
> > Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()"
> >
> > I saw one post that sugget there is a fix that ought to be in cumulative
> > update package 4, but I can't see any items in that which match this problem.
> >
> > The maintenance plans appear to run when called by the SQl Agent Jobs they
> > were initially set up with. However, I am calling one of them from another
> > Job and this has started throwing this error since SP2:
> > "Error: 2007-11-04 18:00:01.81 Code: 0xC0024104 Source: Reporting
> > Task for subplan-{03E683E8-5A40-4697-BF2F-E93EBA6E96E7} Description: The
> > Execute method on the task returned error code 0x80131904 (Conversion failed
> > when converting from a character string to uniqueidentifier.). The Execute
> > method must succeed<c/> and indicate the result using an "out" parameter.
> > End Error"
> >
> > but when I went to look at the plan, I couldn't edit it!
> >
> > Any advice on how to edit the maintenance plans or fix the second error
> > would be great.
> >
> > Thanks,
> >
> > Charles
> >
>
>

Cannot edit maintenance plan created in SQL 2005, SP1

Hello,

I have created a simple maintenance plan in SQL Studio. When I double-click on the task boxes (ie 'Rebuild Index', 'Backup') to just make changes or to look, I get the following message:

Cannot show editor for this task

Additional information:

Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)

I also cannot save any change that I make in the schedule of the plan.

I HAVE installed Integration Services, which at least enabled me to initially SAVE the plan. I just can't edit the tasks or change the schedule.

Any help is most appreciated!

Eunice Griffin

I get the same thing - I finally solved all the integration services got to create a backup maint. plan now I can't edit it - what a pain.

Cannot edit maintenance plan created in SQL 2005, SP1

Hello,

I have created a simple maintenance plan in SQL Studio. When I double-click on the task boxes (ie 'Rebuild Index', 'Backup') to just make changes or to look, I get the following message:

Cannot show editor for this task

Additional information:

Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)

I also cannot save any change that I make in the schedule of the plan.

I HAVE installed Integration Services, which at least enabled me to initially SAVE the plan. I just can't edit the tasks or change the schedule.

Any help is most appreciated!

Eunice Griffin

I get the same thing - I finally solved all the integration services got to create a backup maint. plan now I can't edit it - what a pain.

Tuesday, March 20, 2012

Cannot create publication after SP1 upgrade

After upgrading SQL Server 2005 with the recent service pack, I am unable to create a publication. When I right-click on [INSTANCE]/Replication/Local Publications and select "New Publication...," the mouse cursor turns into an hourglass, but the wizard never shows up, nor is any error displayed.

There is a logged error that's been showing up that may or may not be related. The error message is "Replication-(null): agent (null) scheduled for retry. Could not clean up the distribution history tables."

Any ideas on how we can restore replication functionality on our SQL Server instance?

Can you run profiler before invoking New Publication wizard to trace which statement is causing the problem? What kind of publications do you have before upgrade to SP1? Is distributor on the same machine as publisher?

Thanks,

Zhiqiang Feng

This posting is provided "AS IS" with no warranties, and confers no rights.

|||I ran the profiler, and I'm getting some strange output. Apparently, the command "select * from sysdatabases where name=N'distribution'" is being run over and over again. Strangely enough, there is a row returned from that command that points to where our distribution database was located, but the database isn't shown under the system databases in Management Studio.

Before upgrading to SP1, we were using merge publications with the distributor on the same machine as the publisher.

|||

Can you send sp1 upgrade log files and profiler trace to me? I will send you a separate email.

Thanks,

Zhiqiang Feng

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

From the sp1 upgrade log file, looks like you have run SP1 upgrade twice, the first time it runs, SQLDEV01 machine is treated as a distributor and distribution database is upgrade successfully(from what the log file says). The 2nd time the sp1 upgrade runs, it didn't treat this machine as distributor and didn't upgrade distribution database (also you mentioned distribution database is no longer marked as system database, which is suspicious, we need to figure out why). Did you notice any error during sp1 upgrade? Why you run sp1 upgrade twice? Did you drop distributor or change replication settings after first sp1 upgrade?

Please also email a profiler trace for the New publication wizard so we can further diagnose the issue. When using profiler, make sure select following options (and unselect any options not mentioned below):

Error and Warnings --> ErrorLog, Exceptions, User Error Message

Stored Procedures --> RPC Starting, RPC Completed, SP Starting, SP Completed, SP Stmt Starting

TSQL --> SQL: Batch Starting, SQL: Batch Completed, SQL: StmtStarting

Thanks,

Zhiqiang Feng

This posting is provided "AS IS" with no warranties, and confers no rights.

|||It's finally working! I suspect that all the problems stemmed from there being an inconsistency in the sysdatabases table. I ran "DROP DATABASE distributor" under the master database, and afterward, I was able to set up the distributor, publishers, and subscribers without any problems.

Thank you, Zhiqiang Feng, for your email assistance.

Monday, March 19, 2012

Cannot create diagrams in Upgraded SQL Server 2000 Database

Dear all,

I am trying to save a newly created diagram in SQL Server 2005 SP1.

The error message is:
-Beginning of pasted error message

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

Cannot insert the value NULL into column 'diagram_id', table 'adt_db.dbo.sysdiagrams'; column does not allow nulls. INSERT fails.
The statement has been terminated.
The 'sp_creatediagram' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead. (.Net SqlClient Data Provider)

Program Location:

at Microsoft.VisualStudio.DataTools.Interop.IDTDocTool.Save(Object dsRef, String path, Boolean okToOverwrite)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DatabaseDesignerNode.Save(VSSAVEFLAGS dwSave, String strSilentSaveAsName, IVsUIShell pIVsUIShell, IntPtr punkDocDataIntPtr, String& strMkDocumentNew, Int32& pfCanceled)

-End of pasted error message

The database I use has been upgraded from SQL Server 2000.

I am running in SQL Server 2000 Compatibility Mode (80) but changing the compatibility mode to SQL Server 2050 (90) does not make any difference with regards to this error.I solved the problem by deleting the table dbo.sysdiagrams and letting SQL Server 2005 re-create it. Apparently, its schema was different.|||

????CONGRATULATIONS!!!!

And thank you very, very much. I had desesperated to resolve this problem with my diagram of forty three tables, that i think that i don′t save it, but you resolve my problem with a simple solution, the eternal "restart", or recreate the table in this case.

Thank you very much another time,

Zapa

Cannot create diagrams in Upgraded SQL Server 2000 Database

Dear all,

I am trying to save a newly created diagram in SQL Server 2005 SP1.

The error message is:
-Beginning of pasted error message

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

Cannot insert the value NULL into column 'diagram_id', table 'adt_db.dbo.sysdiagrams'; column does not allow nulls. INSERT fails.
The statement has been terminated.
The 'sp_creatediagram' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead. (.Net SqlClient Data Provider)

Program Location:

at Microsoft.VisualStudio.DataTools.Interop.IDTDocTool.Save(Object dsRef, String path, Boolean okToOverwrite)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DatabaseDesignerNode.Save(VSSAVEFLAGS dwSave, String strSilentSaveAsName, IVsUIShell pIVsUIShell, IntPtr punkDocDataIntPtr, String& strMkDocumentNew, Int32& pfCanceled)

-End of pasted error message

The database I use has been upgraded from SQL Server 2000.

I am running in SQL Server 2000 Compatibility Mode (80) but changing the compatibility mode to SQL Server 2050 (90) does not make any difference with regards to this error.I solved the problem by deleting the table dbo.sysdiagrams and letting SQL Server 2005 re-create it. Apparently, its schema was different.|||

????CONGRATULATIONS!!!!

And thank you very, very much. I had desesperated to resolve this problem with my diagram of forty three tables, that i think that i don′t save it, but you resolve my problem with a simple solution, the eternal "restart", or recreate the table in this case.

Thank you very much another time,

Zapa

Thursday, March 8, 2012

Cannot create a connection to data source

I am running SQL Server 2005, SP2 on a Windows Server 2003, SP1.
When I open a report in the Report Server I get the following error:
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'ASCCSP'. (rsErrorOpeningConnection)
The ConnectionString property has not been initialized.
I am connecting to an Oracle database (using the Oracle client).
I have run into the problem before and have always been able to fix it by
giving the Web Service Identity, ASP.NET Service Account read/execute
permissions on the Oracle driver folder. This is not fixing the issue in
this case. The ASP.NET Service Account that I see in the Reporting Services
Configuration Manager is "NT Authority\Network Service". When I am adding
permissions to the security of the Oracle driver folder, I don't find an
exact match for this user (NT Authority\Network Service), I only find NETWORK
SERVICE. I gave NETWORK SERVICE read/execute rights to the Oracle client
folder. But no luck.
Any suggestions?
Thank you.
--
LaurieTCan you create a read-only user on the Oracle side and then enter those
credentials in the report connection?
"LaurieT" wrote:
> I am running SQL Server 2005, SP2 on a Windows Server 2003, SP1.
> When I open a report in the Report Server I get the following error:
> An error has occurred during report processing. (rsProcessingAborted)
> Cannot create a connection to data source 'ASCCSP'. (rsErrorOpeningConnection)
> The ConnectionString property has not been initialized.
> I am connecting to an Oracle database (using the Oracle client).
> I have run into the problem before and have always been able to fix it by
> giving the Web Service Identity, ASP.NET Service Account read/execute
> permissions on the Oracle driver folder. This is not fixing the issue in
> this case. The ASP.NET Service Account that I see in the Reporting Services
> Configuration Manager is "NT Authority\Network Service". When I am adding
> permissions to the security of the Oracle driver folder, I don't find an
> exact match for this user (NT Authority\Network Service), I only find NETWORK
> SERVICE. I gave NETWORK SERVICE read/execute rights to the Oracle client
> folder. But no luck.
> Any suggestions?
> Thank you.
> --
> LaurieT|||The issue is not with accessing the report data in Oracle (this works fine in
the business intelligence development studio, I can preview the reports here
with no issue) ... it is just with getting the Oracle client to run. When I
try to run reports through the Report Manager, I believe that Reporting
Services uses the Web Service Identity account to access and run the Oracle
client and in my case, it does not have the correct permissions to access and
run the client ... but I can't figure out how to change it.
--
LaurieT
"lonnye" wrote:
> Can you create a read-only user on the Oracle side and then enter those
> credentials in the report connection?
> "LaurieT" wrote:
> > I am running SQL Server 2005, SP2 on a Windows Server 2003, SP1.
> >
> > When I open a report in the Report Server I get the following error:
> > An error has occurred during report processing. (rsProcessingAborted)
> > Cannot create a connection to data source 'ASCCSP'. (rsErrorOpeningConnection)
> > The ConnectionString property has not been initialized.
> >
> > I am connecting to an Oracle database (using the Oracle client).
> >
> > I have run into the problem before and have always been able to fix it by
> > giving the Web Service Identity, ASP.NET Service Account read/execute
> > permissions on the Oracle driver folder. This is not fixing the issue in
> > this case. The ASP.NET Service Account that I see in the Reporting Services
> > Configuration Manager is "NT Authority\Network Service". When I am adding
> > permissions to the security of the Oracle driver folder, I don't find an
> > exact match for this user (NT Authority\Network Service), I only find NETWORK
> > SERVICE. I gave NETWORK SERVICE read/execute rights to the Oracle client
> > folder. But no luck.
> >
> > Any suggestions?
> >
> > Thank you.
> > --
> > LaurieT|||You can change the service accounts by using the Reporting Services
Configuration Tool... Here is a link to more info on how to do this:
http://technet.microsoft.com/en-us/library/bb326419.aspx
--
~lb
"LaurieT" wrote:
> The issue is not with accessing the report data in Oracle (this works fine in
> the business intelligence development studio, I can preview the reports here
> with no issue) ... it is just with getting the Oracle client to run. When I
> try to run reports through the Report Manager, I believe that Reporting
> Services uses the Web Service Identity account to access and run the Oracle
> client and in my case, it does not have the correct permissions to access and
> run the client ... but I can't figure out how to change it.
> --
> LaurieT
>
> "lonnye" wrote:
> > Can you create a read-only user on the Oracle side and then enter those
> > credentials in the report connection?
> >
> > "LaurieT" wrote:
> >
> > > I am running SQL Server 2005, SP2 on a Windows Server 2003, SP1.
> > >
> > > When I open a report in the Report Server I get the following error:
> > > An error has occurred during report processing. (rsProcessingAborted)
> > > Cannot create a connection to data source 'ASCCSP'. (rsErrorOpeningConnection)
> > > The ConnectionString property has not been initialized.
> > >
> > > I am connecting to an Oracle database (using the Oracle client).
> > >
> > > I have run into the problem before and have always been able to fix it by
> > > giving the Web Service Identity, ASP.NET Service Account read/execute
> > > permissions on the Oracle driver folder. This is not fixing the issue in
> > > this case. The ASP.NET Service Account that I see in the Reporting Services
> > > Configuration Manager is "NT Authority\Network Service". When I am adding
> > > permissions to the security of the Oracle driver folder, I don't find an
> > > exact match for this user (NT Authority\Network Service), I only find NETWORK
> > > SERVICE. I gave NETWORK SERVICE read/execute rights to the Oracle client
> > > folder. But no luck.
> > >
> > > Any suggestions?
> > >
> > > Thank you.
> > > --
> > > LaurieT

Cannot create a connection to data source

Windows 2003 Enterprise SP1, Sql Server 2005 June CTP.
I created a report on data from another server. I can run the report just
fine on the server with Reporting Services.
When I try to run the report from my computer I get the cannot create
connection error. I have full rights to the server and sa privilages to SQL
Server on the RS server and the remote server on which the data is located.
I have checked with the Network administrator and kerberos is enabled.
I really need to get this working and prove to management that RS will do
all we need in the way of a reporting tool.
Your help will be apprecited.
RoyWith the June CTP comes the Surface Area Configuration tool. Launch the
tool and makes sure that remote connections are enabled for your SQL
Server. By default, SQL is much tighter on security and remote connections
are off after initial install.
--
| Thread-Topic: Cannot create a connection to data source
| thread-index: AcWsvM7xh3SUrYS9QcCFLHwzj12wwg==| X-WBNR-Posting-Host: 65.118.63.88
| From: =?Utf-8?B?Um95?= <Roy@.discussions.microsoft.com>
| Subject: Cannot create a connection to data source
| Date: Mon, 29 Aug 2005 10:12:17 -0700
| Lines: 12
| Message-ID: <EB5CC7FC-F898-48AC-A8CD-E9B6668EF797@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:51349
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Windows 2003 Enterprise SP1, Sql Server 2005 June CTP.
| I created a report on data from another server. I can run the report just
| fine on the server with Reporting Services.
| When I try to run the report from my computer I get the cannot create
| connection error. I have full rights to the server and sa privilages to
SQL
| Server on the RS server and the remote server on which the data is
located.
| I have checked with the Network administrator and kerberos is enabled.
| I really need to get this working and prove to management that RS will do
| all we need in the way of a reporting tool.
| Your help will be apprecited.
| Roy
|
||||Brad,
I did set the server to allow remote connections.
Roy
""Brad Syputa - MS"" wrote:
> With the June CTP comes the Surface Area Configuration tool. Launch the
> tool and makes sure that remote connections are enabled for your SQL
> Server. By default, SQL is much tighter on security and remote connections
> are off after initial install.
> --
> | Thread-Topic: Cannot create a connection to data source
> | thread-index: AcWsvM7xh3SUrYS9QcCFLHwzj12wwg==> | X-WBNR-Posting-Host: 65.118.63.88
> | From: =?Utf-8?B?Um95?= <Roy@.discussions.microsoft.com>
> | Subject: Cannot create a connection to data source
> | Date: Mon, 29 Aug 2005 10:12:17 -0700
> | Lines: 12
> | Message-ID: <EB5CC7FC-F898-48AC-A8CD-E9B6668EF797@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:51349
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | Windows 2003 Enterprise SP1, Sql Server 2005 June CTP.
> | I created a report on data from another server. I can run the report just
> | fine on the server with Reporting Services.
> | When I try to run the report from my computer I get the cannot create
> | connection error. I have full rights to the server and sa privilages to
> SQL
> | Server on the RS server and the remote server on which the data is
> located.
> | I have checked with the Network administrator and kerberos is enabled.
> | I really need to get this working and prove to management that RS will do
> | all we need in the way of a reporting tool.
> | Your help will be apprecited.
> | Roy
> |
> |
>

Saturday, February 25, 2012

Cannot connect using TCP/IP protocol

Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
any advice?
What is the error number and error message?
There are some TCP/IP issues with older MDAC versions - did
you check/try updating the MDAC version on the 98 client?
-Sue
On Mon, 24 Oct 2005 01:50:02 -0700, "alex"
<alex@.discussions.microsoft.com> wrote:

>Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
>TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
>any advice?

Cannot connect using TCP/IP protocol

Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
any advice?What is the error number and error message?
There are some TCP/IP issues with older MDAC versions - did
you check/try updating the MDAC version on the 98 client?
-Sue
On Mon, 24 Oct 2005 01:50:02 -0700, "alex"
<alex@.discussions.microsoft.com> wrote:
>Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
>TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
>any advice?

Cannot connect using TCP/IP protocol

Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem
.
any advice?What is the error number and error message?
There are some TCP/IP issues with older MDAC versions - did
you check/try updating the MDAC version on the 98 client?
-Sue
On Mon, 24 Oct 2005 01:50:02 -0700, "alex"
<alex@.discussions.microsoft.com> wrote:

>Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
>TCP/IP protocol. NamePipe is OK. Other XP client can connect without proble
m.
>any advice?

Cannot connect to to the other server when setting up replication in SQL 2005

Im trying to setup replication between two 2005 standard editions. They are on the same LAN and installed equally + SP1. They are installed as named instances (with the same instance name MSSQL01). Remote access is allowed and TCP/IP and shared memory and I can connect between them.

SQL1\MSSQL01 is configured as the publisher & distributor and the snapshot is done. When Im using the subscriber wizard from SQL1 to create the subscriptions and add SQL2\MSSQL01 as a subscriber the connection fails to the remote server.

The error message is:

TITLE: Connect to Server

Cannot connect to SQL2\MSSQL01.


ADDITIONAL INFORMATION:

Failed to connect to server SQL2\MSSQL01. (Microsoft.SqlServer.ConnectionInfo)

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

When I do a manual connection to SQL2 using the server managemnet studio on SQL1 I cannot connect using the instance name e.g. SQL2\MSSQL01, it works only when only using the server name e.g. SQL2. Then I have full access both when using a windows or SQL user.

When trying with using the server name only when setting up the subscription, I got a error saying that I need to use the full name.

TITLE: Connect to Server

Cannot connect to TFMHQARNDE07.


ADDITIONAL INFORMATION:

SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, ' SQL2\MSSQL01'. (Replication.Utilities)

I can also mention that theese servers are cloned from another server and I needed to drop the old servername and add the new servername (sp_addserver) on both servers to get the publisher to work.

When I try to setup the subscription from SQL2 and add SQL1 as a publisher I get the same error.

Any one have any idea what it can be?

I found the problem. I didnt have the SQL Browser service runnning which looks to be needed when using instances. After starting it, it works to connect.

Friday, February 24, 2012

Cannot connect to SQL Server or MSDE when enable ICF

Hi,
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I have installed both MSDE and SQL server on my machine, while I test my application from another machine my App cannot connect to my machine. Then I think the problem is because the I
CF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPH
Hi,
when you look in the properties of your server there you can see the port,
the server is using.
I dont know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH

Cannot connect to SQL Server or MSDE when enable ICF

Hi,
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I have installed both MSDE and SQL server on my machine, while I test my application from another machine my App cannot connect to my machine. Then I think the problem is because the ICF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPHHi,
when you look in the properties of your server there you can see the port,
the server is using.
I don´t know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH

Cannot connect to SQL Server or MSDE when enable ICF

Hi,
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I hav
e installed both MSDE and SQL server on my machine, while I test my applicat
ion from another machine my App cannot connect to my machine. Then I think t
he problem is because the I
CF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPHHi,
when you look in the properties of your server there you can see the port,
the server is using.
I dont know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH

Cannot connect to SQL Server 2005 June CTP

We just install SQL Server 2005 June CTP on a Windows
2003 with SP1 and probably all the additional patches.
We just simply cannot connect to the SQL Server at all.
The SQL Server service is running. When we try to
register and click on Test button, we will just get
Timeout expired. We're using SQL Server Authentication.

We have used the June CTP to do an upgrade from SQL
Server 2000 on a Windows 2003 SP1 but without any additional patch
and we don't have any problem.

By the way, beside this forum, are there any other place in MS website to post questions related SQL Server 2005? So far, I only find this
http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005&slcid=us

Thanks for any help,

Peter

Are you trying to connect from a tool (SQL Server Management Studio, for example) that is local to the same server SQL Server 2005 is running on? Or from a different server/client?

By default, SQL Server 2005 now installs with remote connections turned off (secure by default initiative). So, after installing, you have to enable remote connections before you will be able to connect from a different server/client. To do this, use the SQL Server Surface Area Configuration tool.

Dave Fackler

|||

Hi Dave,

I'm trying to connect from SQL Server Management Studio on the same server SQL Server 2005 June CTP is running on.

I just also tried to use osql and I get the following error:

[SQL Native Client]TCP Provider: No connection could be made because the target machine actively refused it.
[SQL Native Client]Client unable to establish connection.
[SQL Native Client]Login timeout expired.

Thanks,

Peter
Peter

Cannot connect to SQL Server 2005 April CTP from remote computer

Hi,

I am trying to connect to a SQL Server on a Windows2003 w/sp1 Server from a remote computer but always seem to get the infamous "Access is denied or Server Does Not Exist" error. However, if I try to connect from the machine that is running the server, there is no problem. (Used sql account, server=mixed authentication)

The windows 2003 Server is a single server installation with .Net 2005 Beta 2 Team Suite, Team Foundation Server and Sql Server - Installing these items took me a while, but eventually I managed to install from scatch to end without any installation errors.

I have triple checked that both TCP 1433 and UDP 1434 is open on my router and under windows firewall.

I have ensured that TCP/IP is enabled in SQL Server Configuration Manager for both "SQL Native Client Configuration" AND "Protocals for MSSQLServer". The default in the registry is DNETLIB (thus the appropriate protocal should be used based on the client)

I have set no Alias' in "SQL Native Client Configuration"

SQL Server is setup for mixed Authentication and I am trying to connect via a sql account.

SQL Server Browser is not running.

Below I have attached the results of running netstat -n, a sql log file and the results of a ipconfig /all

If there is any other information that one might need to help me figure out this problem, just ask.

Thanks for your help!

-Brian

Running netstat -n gives the following results
--
Proto Local Address Foreign Address State
TCP 127.0.0.1:135 127.0.0.1:4760 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1034 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1035 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1036 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1042 ESTABLISHED
TCP 127.0.0.1:1025 127.0.0.1:4761 ESTABLISHED
TCP 127.0.0.1:1034 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1035 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1036 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1042 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:4760 127.0.0.1:135 ESTABLISHED
TCP 127.0.0.1:4761 127.0.0.1:1025 ESTABLISHED
TCP 192.168.0.164:389 192.168.0.164:1145 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1147 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1640 ESTABLISHED
TCP 192.168.0.164:1145 192.168.0.164:389 ESTABLISHED
TCP 192.168.0.164:1147 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:1150 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3705 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3706 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3707 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3708 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3720 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3811 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6187 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6188 ESTABLISHED
TCP 192.168.0.164:1640 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:3187 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:3705 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3706 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3707 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3708 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3720 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3811 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:5891 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:5896 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:6157 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6158 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6174 192.168.0.164:2383 TIME_WAIT
TCP 192.168.0.164:6187 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:6188 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:1150 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:3187 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5891 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5896 ESTABLISHED
The following is one of my sql Logs.

Date,Source,Severity,Message
06/17/2005 07:24:14,spid20s,Unknown,Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpstar90.dll' version '2000.90.1116' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpsqlbot.dll' version '2000.90.1116' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
06/17/2005 07:19:40,spid11s,Unknown,Service Broker manager has started.
06/17/2005 07:19:40,spid11s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid11s,Unknown,The Service Broker protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid4s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
06/17/2005 07:19:38,spid8s,Unknown,Starting up database 'tempdb'.
06/17/2005 07:19:33,spid13s,Unknown,Starting up database 'rlbss'.
06/17/2005 07:19:32,spid11s,Unknown,Starting up database 'BisDWDB'.
06/17/2005 07:19:32,spid4s,Unknown,Recovery is writing a checkpoint in database 'BisDB' (8). This is an informational message only. No user action is required.
06/17/2005 07:19:26,spid14s,Unknown,Starting up database 'VSTEAMTeamBuild'.
06/17/2005 07:19:23,spid13s,Unknown,Starting up database 'VSTEAMSCCAdmin'.
06/17/2005 07:19:23,spid11s,Unknown,Starting up database 'VSTEAMSCC'.
06/17/2005 07:19:22,spid12s,Unknown,Starting up database 'BisDB'.
06/17/2005 07:19:22,spid12s,Unknown,Recovery is writing a checkpoint in database 'CurrituckDB' (7). This is an informational message only. No user action is required.
06/17/2005 07:19:22,spid8s,Unknown,Clearing tempdb database.
06/17/2005 07:19:20,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 192.168.0.164]
06/17/2005 07:19:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 1.
06/17/2005 07:19:17,spid14s,Unknown,Starting up database 'CurrituckDB'.
06/17/2005 07:19:17,spid13s,Unknown,Starting up database 'ReportServerTempDB'.
06/17/2005 07:19:17,spid12s,Unknown,Starting up database 'ReportServer'.
06/17/2005 07:19:16,spid11s,Unknown,Starting up database 'msdb'.
06/17/2005 07:19:16,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
06/17/2005 07:19:16,Server,Unknown,The SQL Network Interface library was unable to register SPN. Error: 0x54b.
06/17/2005 07:19:16,Server,Unknown,Error: 26037<c/> Severity: 16<c/> State: 1.
06/17/2005 07:19:16,Server,Unknown,Dedicated admin connection support was established for listening locally on port 1434.
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4> 1434].
06/17/2005 07:19:16,Server,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
06/17/2005 07:19:16,Server,Unknown,Server shared memory provider is ready for clients to connect to [ \\.\pipe\SQLSm\MSSQLSERVER ].
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 'any' <ipv4> 1433].
06/17/2005 07:19:16,spid8s,Unknown,Starting up database 'model'.
06/17/2005 07:19:16,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
06/17/2005 07:19:16,spid4s,Unknown,Server name is 'BRIAN-SRV'. This is an informational message only. No user action is required.
06/17/2005 07:19:14,spid4s,Unknown,Starting up database 'mssqlsystemresource'.
06/17/2005 07:19:14,spid4s,Unknown,SQL Trace ID 1 was started by login "sa".
06/17/2005 07:19:14,spid4s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
06/17/2005 07:19:12,spid4s,Unknown,Starting up database 'master'.
06/17/2005 07:19:12,Server,Unknown,Database mirroring has been enabled on this instance of SQL Server.
06/17/2005 07:19:12,Server,Unknown,Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.
06/17/2005 07:19:10,Server,Unknown,Detected 1 CPUs. This is an informational message; no user action is required.
06/17/2005 07:19:10,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
06/17/2005 07:19:10,Server,Unknown,-l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
06/17/2005 07:19:10,Server,Unknown,-e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
06/17/2005 07:19:10,Server,Unknown,-d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
06/17/2005 07:19:10,Server,Unknown,Registry startup parameters:
06/17/2005 07:19:10,Server,Unknown,This instance of SQL Server last reported using a process ID of 640 at 6/17/2005 3:23:15 AM (local) 6/17/2005 7:23:15 AM (UTC). This is an informational message only; no user action is required.
06/17/2005 07:19:10,Server,Unknown,Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
06/17/2005 07:19:10,Server,Unknown,Server process ID is 736.
06/17/2005 07:19:10,Server,Unknown,All rights reserved.
06/17/2005 07:19:10,Server,Unknown,(c) 2004 Microsoft Corporation.
06/17/2005 07:19:10,Server,Unknown,Microsoft SQL Server 2005 - 9.00.1116 (Intel X86) Apr 9 2005 20:56:37 Copyright (c) 1988-2004 Microsoft Corporation Beta Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
results of IPCONFIG /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : brian-srv
Primary Dns Suffix . . . . . . . : brianfurner.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : brianfurner.local
cityxx.phub.net.cable.rogers.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : cityxx.phub.net.cable.rogers.com
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0B-6A-2E-44-A4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.164
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
192.168.0.164
Lease Obtained. . . . . . . . . . : Friday, June 17, 2005 7:18:35 AM
Lease Expires . . . . . . . . . . : Friday, June 24, 2005 7:18:35 AM

Also, if you wish to see a list of the services running on my server, please click this link.

http://hoser.hopto.org:97/test.htm

Thanks

|||

I am still trying to get this working, I am pleading, if someone has any ideas, please let me know.

Thanks

|||Is there a reason you chose not to start SQL Browser?

What is the instance name and what are you typing in the connection string of the app.

-Euan|||

Hi,

I did not start SQL Browser, as I read it is not necessary so long as you specifically set the port in TCP/IP settings in Configuration Manager.

I believe the instance name as the same as the computer name. When I hold my mouse over the sql server icon in the taskbar it shows this

BRIAN-SRV - MSSQLServer

The connection string is irrelevant at this point. I was trying to connect using VS.NET 2005 Server explorer. I chose to "Add a Data Connection"

Entered my IP Address as my server name.
my SQL user account and Password and my initial catalog.

THanks.

|||The instance name may be the same as the computer name. Did you install as a named instance or default instance?

You can tell this by looking in the registry for the SQL Server services, if they have something in () after the service name then you have a named instance.

In that case you must run SQL Browser for port resolution or you must fix the port number of the instance(by default named instance ports are dynamic, on the default instance is statically assigned and by default this is 1433).|||Another thought, does the server have a valid IP address, at one point in the log it is listening on 127.0.0.1, thats the loopback connection.

Can you connect locally using sqlcmd?

-Euan|||Hey Euan,

Thanks for your help.

Yes, I can connect locally using sqlcmd.

IN
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

I see a key named InstalledInstances. ITs value is MSSQLSERVER SHAREPOINT

I had also wondered if the server was only loopingback. But I do not know how to change this within SQL Server.

Thanks Euan.|||Hey Euan,

Here is my ip configuration for SQL SERVER.

http://hoser.hopto.org:97/ip1.jpg

http://hoser.hopto.org:97/ip2.jpg

http://hoser.hopto.org:97/ipall.jpg

Thanks again!

-Brian|||Try going to www.grc.com and using shields up to test port 1433 to see if your firewall is open on that port and forwarding it to SQL server.|||Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian|||For those still grappling with this problem, I needed to run SQL Server Configuration Manager and expand the node "SQL Server 2005 Network Configuration/Protocols for <instance name>". I then enabled the TCP/IP protocol and voila! I was able to connect to the 2005 SQL Server using a remote device.|||

I have just installed the ssme ctp on the machine I am running vs2005c#Express and it cant find the connection either. I am not accessing it remotely, although I would like to be able to in the future, but for now I would just like to do all my work on this same machine. Any ideas why I can not get a connection?

Roger

|||I had the same problem, and those jerks at rogers swore up and down

they weren't blocking port 1433, but after changing the port, mine

worked too!

I'm so pissed I'd like to complain to one of their vp's, but that old

saying about &%#^ rolling downhill was probably started at in the

context of rogers.|||

Brian Furner wrote:

Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian

Thank you so much! I had the exact same problem as you, and I was about to tear my hair off, but now I changed the port and it all works like it should.
Indeed your post helps others, and I marked it as such :)

Again, thank you.

Cannot connect to SQL Server 2005 April CTP from remote computer

Hi,

I am trying to connect to a SQL Server on a Windows2003 w/sp1 Server from a remote computer but always seem to get the infamous "Access is denied or Server Does Not Exist" error. However, if I try to connect from the machine that is running the server, there is no problem. (Used sql account, server=mixed authentication)

The windows 2003 Server is a single server installation with .Net 2005 Beta 2 Team Suite, Team Foundation Server and Sql Server - Installing these items took me a while, but eventually I managed to install from scatch to end without any installation errors.

I have triple checked that both TCP 1433 and UDP 1434 is open on my router and under windows firewall.

I have ensured that TCP/IP is enabled in SQL Server Configuration Manager for both "SQL Native Client Configuration" AND "Protocals for MSSQLServer". The default in the registry is DNETLIB (thus the appropriate protocal should be used based on the client)

I have set no Alias' in "SQL Native Client Configuration"

SQL Server is setup for mixed Authentication and I am trying to connect via a sql account.

SQL Server Browser is not running.

Below I have attached the results of running netstat -n, a sql log file and the results of a ipconfig /all

If there is any other information that one might need to help me figure out this problem, just ask.

Thanks for your help!

-Brian

Running netstat -n gives the following results
--
Proto Local Address Foreign Address State
TCP 127.0.0.1:135 127.0.0.1:4760 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1034 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1035 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1036 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1042 ESTABLISHED
TCP 127.0.0.1:1025 127.0.0.1:4761 ESTABLISHED
TCP 127.0.0.1:1034 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1035 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1036 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1042 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:4760 127.0.0.1:135 ESTABLISHED
TCP 127.0.0.1:4761 127.0.0.1:1025 ESTABLISHED
TCP 192.168.0.164:389 192.168.0.164:1145 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1147 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1640 ESTABLISHED
TCP 192.168.0.164:1145 192.168.0.164:389 ESTABLISHED
TCP 192.168.0.164:1147 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:1150 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3705 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3706 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3707 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3708 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3720 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3811 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6187 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6188 ESTABLISHED
TCP 192.168.0.164:1640 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:3187 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:3705 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3706 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3707 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3708 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3720 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3811 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:5891 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:5896 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:6157 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6158 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6174 192.168.0.164:2383 TIME_WAIT
TCP 192.168.0.164:6187 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:6188 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:1150 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:3187 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5891 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5896 ESTABLISHED
The following is one of my sql Logs.

Date,Source,Severity,Message
06/17/2005 07:24:14,spid20s,Unknown,Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpstar90.dll' version '2000.90.1116' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpsqlbot.dll' version '2000.90.1116' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
06/17/2005 07:19:40,spid11s,Unknown,Service Broker manager has started.
06/17/2005 07:19:40,spid11s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid11s,Unknown,The Service Broker protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid4s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
06/17/2005 07:19:38,spid8s,Unknown,Starting up database 'tempdb'.
06/17/2005 07:19:33,spid13s,Unknown,Starting up database 'rlbss'.
06/17/2005 07:19:32,spid11s,Unknown,Starting up database 'BisDWDB'.
06/17/2005 07:19:32,spid4s,Unknown,Recovery is writing a checkpoint in database 'BisDB' (8). This is an informational message only. No user action is required.
06/17/2005 07:19:26,spid14s,Unknown,Starting up database 'VSTEAMTeamBuild'.
06/17/2005 07:19:23,spid13s,Unknown,Starting up database 'VSTEAMSCCAdmin'.
06/17/2005 07:19:23,spid11s,Unknown,Starting up database 'VSTEAMSCC'.
06/17/2005 07:19:22,spid12s,Unknown,Starting up database 'BisDB'.
06/17/2005 07:19:22,spid12s,Unknown,Recovery is writing a checkpoint in database 'CurrituckDB' (7). This is an informational message only. No user action is required.
06/17/2005 07:19:22,spid8s,Unknown,Clearing tempdb database.
06/17/2005 07:19:20,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 192.168.0.164]
06/17/2005 07:19:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 1.
06/17/2005 07:19:17,spid14s,Unknown,Starting up database 'CurrituckDB'.
06/17/2005 07:19:17,spid13s,Unknown,Starting up database 'ReportServerTempDB'.
06/17/2005 07:19:17,spid12s,Unknown,Starting up database 'ReportServer'.
06/17/2005 07:19:16,spid11s,Unknown,Starting up database 'msdb'.
06/17/2005 07:19:16,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
06/17/2005 07:19:16,Server,Unknown,The SQL Network Interface library was unable to register SPN. Error: 0x54b.
06/17/2005 07:19:16,Server,Unknown,Error: 26037<c/> Severity: 16<c/> State: 1.
06/17/2005 07:19:16,Server,Unknown,Dedicated admin connection support was established for listening locally on port 1434.
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4> 1434].
06/17/2005 07:19:16,Server,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
06/17/2005 07:19:16,Server,Unknown,Server shared memory provider is ready for clients to connect to [ \\.\pipe\SQLSm\MSSQLSERVER ].
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 'any' <ipv4> 1433].
06/17/2005 07:19:16,spid8s,Unknown,Starting up database 'model'.
06/17/2005 07:19:16,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
06/17/2005 07:19:16,spid4s,Unknown,Server name is 'BRIAN-SRV'. This is an informational message only. No user action is required.
06/17/2005 07:19:14,spid4s,Unknown,Starting up database 'mssqlsystemresource'.
06/17/2005 07:19:14,spid4s,Unknown,SQL Trace ID 1 was started by login "sa".
06/17/2005 07:19:14,spid4s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
06/17/2005 07:19:12,spid4s,Unknown,Starting up database 'master'.
06/17/2005 07:19:12,Server,Unknown,Database mirroring has been enabled on this instance of SQL Server.
06/17/2005 07:19:12,Server,Unknown,Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.
06/17/2005 07:19:10,Server,Unknown,Detected 1 CPUs. This is an informational message; no user action is required.
06/17/2005 07:19:10,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
06/17/2005 07:19:10,Server,Unknown,-l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
06/17/2005 07:19:10,Server,Unknown,-e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
06/17/2005 07:19:10,Server,Unknown,-d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
06/17/2005 07:19:10,Server,Unknown,Registry startup parameters:
06/17/2005 07:19:10,Server,Unknown,This instance of SQL Server last reported using a process ID of 640 at 6/17/2005 3:23:15 AM (local) 6/17/2005 7:23:15 AM (UTC). This is an informational message only; no user action is required.
06/17/2005 07:19:10,Server,Unknown,Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
06/17/2005 07:19:10,Server,Unknown,Server process ID is 736.
06/17/2005 07:19:10,Server,Unknown,All rights reserved.
06/17/2005 07:19:10,Server,Unknown,(c) 2004 Microsoft Corporation.
06/17/2005 07:19:10,Server,Unknown,Microsoft SQL Server 2005 - 9.00.1116 (Intel X86) Apr 9 2005 20:56:37 Copyright (c) 1988-2004 Microsoft Corporation Beta Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
results of IPCONFIG /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : brian-srv
Primary Dns Suffix . . . . . . . : brianfurner.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : brianfurner.local
cityxx.phub.net.cable.rogers.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : cityxx.phub.net.cable.rogers.com
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0B-6A-2E-44-A4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.164
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
192.168.0.164
Lease Obtained. . . . . . . . . . : Friday, June 17, 2005 7:18:35 AM
Lease Expires . . . . . . . . . . : Friday, June 24, 2005 7:18:35 AM

Also, if you wish to see a list of the services running on my server, please click this link.

http://hoser.hopto.org:97/test.htm

Thanks

|||

I am still trying to get this working, I am pleading, if someone has any ideas, please let me know.

Thanks

|||Is there a reason you chose not to start SQL Browser?

What is the instance name and what are you typing in the connection string of the app.

-Euan|||

Hi,

I did not start SQL Browser, as I read it is not necessary so long as you specifically set the port in TCP/IP settings in Configuration Manager.

I believe the instance name as the same as the computer name. When I hold my mouse over the sql server icon in the taskbar it shows this

BRIAN-SRV - MSSQLServer

The connection string is irrelevant at this point. I was trying to connect using VS.NET 2005 Server explorer. I chose to "Add a Data Connection"

Entered my IP Address as my server name.
my SQL user account and Password and my initial catalog.

THanks.

|||The instance name may be the same as the computer name. Did you install as a named instance or default instance?

You can tell this by looking in the registry for the SQL Server services, if they have something in () after the service name then you have a named instance.

In that case you must run SQL Browser for port resolution or you must fix the port number of the instance(by default named instance ports are dynamic, on the default instance is statically assigned and by default this is 1433).|||Another thought, does the server have a valid IP address, at one point in the log it is listening on 127.0.0.1, thats the loopback connection.

Can you connect locally using sqlcmd?

-Euan|||Hey Euan,

Thanks for your help.

Yes, I can connect locally using sqlcmd.

IN
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

I see a key named InstalledInstances. ITs value is MSSQLSERVER SHAREPOINT

I had also wondered if the server was only loopingback. But I do not know how to change this within SQL Server.

Thanks Euan.|||Hey Euan,

Here is my ip configuration for SQL SERVER.

http://hoser.hopto.org:97/ip1.jpg

http://hoser.hopto.org:97/ip2.jpg

http://hoser.hopto.org:97/ipall.jpg

Thanks again!

-Brian|||Try going to www.grc.com and using shields up to test port 1433 to see if your firewall is open on that port and forwarding it to SQL server.|||Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian|||For those still grappling with this problem, I needed to run SQL Server Configuration Manager and expand the node "SQL Server 2005 Network Configuration/Protocols for <instance name>". I then enabled the TCP/IP protocol and voila! I was able to connect to the 2005 SQL Server using a remote device.|||

I have just installed the ssme ctp on the machine I am running vs2005c#Express and it cant find the connection either. I am not accessing it remotely, although I would like to be able to in the future, but for now I would just like to do all my work on this same machine. Any ideas why I can not get a connection?

Roger

|||I had the same problem, and those jerks at rogers swore up and down

they weren't blocking port 1433, but after changing the port, mine

worked too!

I'm so pissed I'd like to complain to one of their vp's, but that old

saying about &%#^ rolling downhill was probably started at in the

context of rogers.|||

Brian Furner wrote:

Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian

Thank you so much! I had the exact same problem as you, and I was about to tear my hair off, but now I changed the port and it all works like it should.
Indeed your post helps others, and I marked it as such :)

Again, thank you.