Seem to not be able to get set up right. Have split-brain dns (Server2003
with AD) natted at the firewall with 5 domains - one internal only and
dynamic; all others static for basically websites and email pointers.
Websites, email, sql, asp pages are working fine - EXCEPT REPORTING
SERVICES!!!
I have uninstalled, reinstalled, added IUSR_MachineName to users and role
assignment as browse in RS. Gave IUSR_MachineName read permissions to folder
and have the following to report:
With
<ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl> not added.
Within IIS Reports set to no anonymous and winAuthen on and ReportServer set
to no anonymous and winAuth on: Security options and reports display
appropriately. Not viewable using interal ip address. Viewable from outside
the firewall using external ip address only after login prompt.
With
<ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl> added.
Within IIS Reports set to no anonymous and winAuthen on and ReportServer set
to anonymous and winAuth on:
Using Internal IP: Login, then Folder Listing, Security options do not
display and reports give page not found. Report server - report viewable
Using ServerName: Login, Folder Listing, Security options do not display and
reports give page not found. Report server - report viewable.
Using External IP outside Firewall: Login, Folder Listing, Security options
do not display and reports give page not found under Reports. Report server
- report viewable.
Using domain name: Reports - page not found, ReportServer - page not found.
With
<ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl> added.
Within IIS Reports set to no anonymous and winAuthen on and ReportServer set
to anonymous and winAuth on AND virtual directories added under website AND
home.aspx added and moved to top under documents for virtual directory:
Using Internal IP: Folder Listing (no login), Security options do not
display and reports give 403.8. Report server - report viewable
Using ServerName: Folder Listing (no login), Security options do not display
and reports give 403.8. Report server - report viewable.
Using External IP outside Firewall: Login, Folder Listing, Security options
do not display and reports give page 403.8. Report server - report viewable.
Using domain name url: Reports - 403.8; ReportServer - 403.8
Next?
JanetHello Janet,
If the Report Manager and Report Server are on the same machine then remove
the <ReportServerExternalUrl> and the <ReportServerUrl> from the <UI> node
in the config file - and replace with this:
<UI>
<ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
</UI>
Peter Blackburn
Author: Hitchhiker's Guide to SQL Server 2000 Reporting Services
http://www.sqlreportingservices.net
"janetb" <janetb@.discussions.microsoft.com> wrote in message
news:EB70D3CE-FA1F-4445-9B52-48F0FCA11096@.microsoft.com...
> Seem to not be able to get set up right. Have split-brain dns (Server2003
> with AD) natted at the firewall with 5 domains - one internal only and
> dynamic; all others static for basically websites and email pointers.
> Websites, email, sql, asp pages are working fine - EXCEPT REPORTING
> SERVICES!!!
> I have uninstalled, reinstalled, added IUSR_MachineName to users and role
> assignment as browse in RS. Gave IUSR_MachineName read permissions to
> folder
> and have the following to report:
> With
> <ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl>
> not added.
> Within IIS Reports set to no anonymous and winAuthen on and ReportServer
> set
> to no anonymous and winAuth on: Security options and reports display
> appropriately. Not viewable using interal ip address. Viewable from
> outside
> the firewall using external ip address only after login prompt.
> With
> <ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl>
> added.
> Within IIS Reports set to no anonymous and winAuthen on and ReportServer
> set
> to anonymous and winAuth on:
> Using Internal IP: Login, then Folder Listing, Security options do not
> display and reports give page not found. Report server - report viewable
> Using ServerName: Login, Folder Listing, Security options do not display
> and
> reports give page not found. Report server - report viewable.
> Using External IP outside Firewall: Login, Folder Listing, Security
> options
> do not display and reports give page not found under Reports. Report
> server
> - report viewable.
> Using domain name: Reports - page not found, ReportServer - page not
> found.
> With
> <ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl>
> added.
> Within IIS Reports set to no anonymous and winAuthen on and ReportServer
> set
> to anonymous and winAuth on AND virtual directories added under website
> AND
> home.aspx added and moved to top under documents for virtual directory:
> Using Internal IP: Folder Listing (no login), Security options do not
> display and reports give 403.8. Report server - report viewable
> Using ServerName: Folder Listing (no login), Security options do not
> display
> and reports give 403.8. Report server - report viewable.
> Using External IP outside Firewall: Login, Folder Listing, Security
> options
> do not display and reports give page 403.8. Report server - report
> viewable.
> Using domain name url: Reports - 403.8; ReportServer - 403.8
> Next?
> Janet|||Peter,
Thanks so much for replying. I made the change, but unfortunately there was
no change. When I try to use the url with the domain name instead of the ip
address or machineName, I still get the 403.8 dns error. I even tried
removing the virtual directories for reports and reports server from the
website - no change.
Any other ideas?
Thanks,
Janet
"Peter Blackburn (www.sqlreportingservice" wrote:
> Hello Janet,
> If the Report Manager and Report Server are on the same machine then remove
> the <ReportServerExternalUrl> and the <ReportServerUrl> from the <UI> node
> in the config file - and replace with this:
> <UI>
> <ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
> </UI>
> Peter Blackburn
> Author: Hitchhiker's Guide to SQL Server 2000 Reporting Services
> http://www.sqlreportingservices.net
>
> "janetb" <janetb@.discussions.microsoft.com> wrote in message
> news:EB70D3CE-FA1F-4445-9B52-48F0FCA11096@.microsoft.com...
> > Seem to not be able to get set up right. Have split-brain dns (Server2003
> > with AD) natted at the firewall with 5 domains - one internal only and
> > dynamic; all others static for basically websites and email pointers.
> > Websites, email, sql, asp pages are working fine - EXCEPT REPORTING
> > SERVICES!!!
> >
> > I have uninstalled, reinstalled, added IUSR_MachineName to users and role
> > assignment as browse in RS. Gave IUSR_MachineName read permissions to
> > folder
> > and have the following to report:
> >
> > With
> > <ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl>
> > not added.
> > Within IIS Reports set to no anonymous and winAuthen on and ReportServer
> > set
> > to no anonymous and winAuth on: Security options and reports display
> > appropriately. Not viewable using interal ip address. Viewable from
> > outside
> > the firewall using external ip address only after login prompt.
> >
> > With
> > <ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl>
> > added.
> > Within IIS Reports set to no anonymous and winAuthen on and ReportServer
> > set
> > to anonymous and winAuth on:
> > Using Internal IP: Login, then Folder Listing, Security options do not
> > display and reports give page not found. Report server - report viewable
> > Using ServerName: Login, Folder Listing, Security options do not display
> > and
> > reports give page not found. Report server - report viewable.
> > Using External IP outside Firewall: Login, Folder Listing, Security
> > options
> > do not display and reports give page not found under Reports. Report
> > server
> > - report viewable.
> > Using domain name: Reports - page not found, ReportServer - page not
> > found.
> >
> > With
> > <ReportServerExternalUrl>http://domainName/ReportServer</ReportServerExternalUrl>
> > added.
> > Within IIS Reports set to no anonymous and winAuthen on and ReportServer
> > set
> > to anonymous and winAuth on AND virtual directories added under website
> > AND
> > home.aspx added and moved to top under documents for virtual directory:
> > Using Internal IP: Folder Listing (no login), Security options do not
> > display and reports give 403.8. Report server - report viewable
> > Using ServerName: Folder Listing (no login), Security options do not
> > display
> > and reports give 403.8. Report server - report viewable.
> > Using External IP outside Firewall: Login, Folder Listing, Security
> > options
> > do not display and reports give page 403.8. Report server - report
> > viewable.
> > Using domain name url: Reports - 403.8; ReportServer - 403.8
> >
> > Next?
> >
> > Janet
>
>
Showing posts with label firewall. Show all posts
Showing posts with label firewall. Show all posts
Wednesday, March 21, 2012
DMZ, MSDTC and Windows Server 2003 SP1
Hi, did somebody know a checklist or Q-Article how to configure MSDTC
between
two SQL Server in two separate DMZ (Firewall Ports) ?
Further, I must find out which impact has Windows Server SP1 on MSDTC or
better
on a BizTalk 2004 Server.
Thanks for all Infos.
Hi
Check out "INFO: Configuring Microsoft Distributed Transaction Coordinator
(DTC) to Work Through a Firewall" http://support.microsoft.com/kb/250367/
Service Pack 1 enforces tighter security, if you can test the installation
on another system it would help but not guarantee there will not be issues.
You may want to run MBSA to see what it throws before you install the service
pack as these may be potential problem areas.
John
"MV" wrote:
> Hi, did somebody know a checklist or Q-Article how to configure MSDTC
> between
> two SQL Server in two separate DMZ (Firewall Ports) ?
> Further, I must find out which impact has Windows Server SP1 on MSDTC or
> better
> on a BizTalk 2004 Server.
> Thanks for all Infos.
>
>
between
two SQL Server in two separate DMZ (Firewall Ports) ?
Further, I must find out which impact has Windows Server SP1 on MSDTC or
better
on a BizTalk 2004 Server.
Thanks for all Infos.
Hi
Check out "INFO: Configuring Microsoft Distributed Transaction Coordinator
(DTC) to Work Through a Firewall" http://support.microsoft.com/kb/250367/
Service Pack 1 enforces tighter security, if you can test the installation
on another system it would help but not guarantee there will not be issues.
You may want to run MBSA to see what it throws before you install the service
pack as these may be potential problem areas.
John
"MV" wrote:
> Hi, did somebody know a checklist or Q-Article how to configure MSDTC
> between
> two SQL Server in two separate DMZ (Firewall Ports) ?
> Further, I must find out which impact has Windows Server SP1 on MSDTC or
> better
> on a BizTalk 2004 Server.
> Thanks for all Infos.
>
>
DMZ, MSDTC and Windows Server 2003 SP1
Hi, did somebody know a checklist or Q-Article how to configure MSDTC
between
two SQL Server in two separate DMZ (Firewall Ports) ?
Further, I must find out which impact has Windows Server SP1 on MSDTC or
better
on a BizTalk 2004 Server.
Thanks for all Infos.Hi
Check out "INFO: Configuring Microsoft Distributed Transaction Coordinator
(DTC) to Work Through a Firewall" http://support.microsoft.com/kb/250367/
Service Pack 1 enforces tighter security, if you can test the installation
on another system it would help but not guarantee there will not be issues.
You may want to run MBSA to see what it throws before you install the service
pack as these may be potential problem areas.
John
"MV" wrote:
> Hi, did somebody know a checklist or Q-Article how to configure MSDTC
> between
> two SQL Server in two separate DMZ (Firewall Ports) ?
> Further, I must find out which impact has Windows Server SP1 on MSDTC or
> better
> on a BizTalk 2004 Server.
> Thanks for all Infos.
>
>
between
two SQL Server in two separate DMZ (Firewall Ports) ?
Further, I must find out which impact has Windows Server SP1 on MSDTC or
better
on a BizTalk 2004 Server.
Thanks for all Infos.Hi
Check out "INFO: Configuring Microsoft Distributed Transaction Coordinator
(DTC) to Work Through a Firewall" http://support.microsoft.com/kb/250367/
Service Pack 1 enforces tighter security, if you can test the installation
on another system it would help but not guarantee there will not be issues.
You may want to run MBSA to see what it throws before you install the service
pack as these may be potential problem areas.
John
"MV" wrote:
> Hi, did somebody know a checklist or Q-Article how to configure MSDTC
> between
> two SQL Server in two separate DMZ (Firewall Ports) ?
> Further, I must find out which impact has Windows Server SP1 on MSDTC or
> better
> on a BizTalk 2004 Server.
> Thanks for all Infos.
>
>
DMZ, MSDTC and Windows Server 2003 SP1
Hi, did somebody know a checklist or Q-Article how to configure MSDTC
between
two SQL Server in two separate DMZ (Firewall Ports) ?
Further, I must find out which impact has Windows Server SP1 on MSDTC or
better
on a BizTalk 2004 Server.
Thanks for all Infos.Hi
Check out "INFO: Configuring Microsoft Distributed Transaction Coordinator
(DTC) to Work Through a Firewall" http://support.microsoft.com/kb/250367/
Service Pack 1 enforces tighter security, if you can test the installation
on another system it would help but not guarantee there will not be issues.
You may want to run MBSA to see what it throws before you install the servic
e
pack as these may be potential problem areas.
John
"MV" wrote:
> Hi, did somebody know a checklist or Q-Article how to configure MSDTC
> between
> two SQL Server in two separate DMZ (Firewall Ports) ?
> Further, I must find out which impact has Windows Server SP1 on MSDTC or
> better
> on a BizTalk 2004 Server.
> Thanks for all Infos.
>
>
between
two SQL Server in two separate DMZ (Firewall Ports) ?
Further, I must find out which impact has Windows Server SP1 on MSDTC or
better
on a BizTalk 2004 Server.
Thanks for all Infos.Hi
Check out "INFO: Configuring Microsoft Distributed Transaction Coordinator
(DTC) to Work Through a Firewall" http://support.microsoft.com/kb/250367/
Service Pack 1 enforces tighter security, if you can test the installation
on another system it would help but not guarantee there will not be issues.
You may want to run MBSA to see what it throws before you install the servic
e
pack as these may be potential problem areas.
John
"MV" wrote:
> Hi, did somebody know a checklist or Q-Article how to configure MSDTC
> between
> two SQL Server in two separate DMZ (Firewall Ports) ?
> Further, I must find out which impact has Windows Server SP1 on MSDTC or
> better
> on a BizTalk 2004 Server.
> Thanks for all Infos.
>
>
DMZ to SQL Server 2nd instance connection issue
Hi,
We are implementing ShaprePoint Application.
SharePoint installation is completed and the server is in the DMZ (behind the firewall). Name it as SERVER1
Also, we installed SQL Server database (SHAREPOINTSQL) on a server as second instance (we already had one database). Name it as SERVER2.
I could connect SHAREPOINTSQL from any client within the domain (not from DMZ).
When I try to connect same database from SERVER1 (in DMZ), I don't see SHAREPOINTSQL listing when I am in SQL Enterprise Manager. I was hoping to see two entries (one for default database as SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could see de
fault database and connection fine.
Do I need to do any special setup to connect from SERVER1 to SERVER2\SHAREPOINTSQL ?
Hope I explained clearly
Thanks
Port 1433 was opened for firewall. As I said, I could connect SERVER1 to SERVER2 (default database) with out any problem.
Thanks,
Bob
"Bob Robert" wrote:
> Hi,
> We are implementing ShaprePoint Application.
> SharePoint installation is completed and the server is in the DMZ (behind the firewall). Name it as SERVER1
> Also, we installed SQL Server database (SHAREPOINTSQL) on a server as second instance (we already had one database). Name it as SERVER2.
> I could connect SHAREPOINTSQL from any client within the domain (not from DMZ).
> When I try to connect same database from SERVER1 (in DMZ), I don't see SHAREPOINTSQL listing when I am in SQL Enterprise Manager. I was hoping to see two entries (one for default database as SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could see
default database and connection fine.
> Do I need to do any special setup to connect from SERVER1 to SERVER2\SHAREPOINTSQL ?
> Hope I explained clearly
> Thanks
|||Any update from Guru's. I am still having problem
"Bob Robert" wrote:
> Hi,
> We are implementing ShaprePoint Application.
> SharePoint installation is completed and the server is in the DMZ (behind the firewall). Name it as SERVER1
> Also, we installed SQL Server database (SHAREPOINTSQL) on a server as second instance (we already had one database). Name it as SERVER2.
> I could connect SHAREPOINTSQL from any client within the domain (not from DMZ).
> When I try to connect same database from SERVER1 (in DMZ), I don't see SHAREPOINTSQL listing when I am in SQL Enterprise Manager. I was hoping to see two entries (one for default database as SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could see
default database and connection fine.
> Do I need to do any special setup to connect from SERVER1 to SERVER2\SHAREPOINTSQL ?
> Hope I explained clearly
> Thanks
|||I found some thing interesting. After opening all the ports, I could able to connect named instance even though named instance was using port 1434.
"Bob Robert" wrote:
[vbcol=seagreen]
> Any update from Guru's. I am still having problem
> "Bob Robert" wrote:
e default database and connection fine.[vbcol=seagreen]
|||Bob, to connect to instances of SQL there are more ports required, 1434 from memory, you'll find info on this on TechNet if you search under SQL.
Steven Collier
SharePoint Portal Server MVP
http://mvp.support.microsoft.com
"Bob Robert" wrote:
[vbcol=seagreen]
> I found some thing interesting. After opening all the ports, I could able to connect named instance even though named instance was using port 1434.
> "Bob Robert" wrote:
see default database and connection fine.[vbcol=seagreen]
|||Run "Server Network Utility" on the server machine (the one you cannot connect to, probably the
named instance), and check what port number it is using, Open for that port in the firewalls. Also,
You might want to fix the port number by typing ion the port number...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bob Robert" <BobRobert@.discussions.microsoft.com> wrote in message
news:955A498C-6CFA-46F1-B9A1-53075DA9AD42@.microsoft.com...
> I found some thing interesting. After opening all the ports, I could able to connect named
instance even though named instance was using port 1434.[vbcol=seagreen]
> "Bob Robert" wrote:
it as SERVER1[vbcol=seagreen]
already had one database). Name it as SERVER2.[vbcol=seagreen]
when I am in SQL Enterprise Manager. I was hoping to see two entries (one for default database as
SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could see default database and connection fine.[vbcol=seagreen]
We are implementing ShaprePoint Application.
SharePoint installation is completed and the server is in the DMZ (behind the firewall). Name it as SERVER1
Also, we installed SQL Server database (SHAREPOINTSQL) on a server as second instance (we already had one database). Name it as SERVER2.
I could connect SHAREPOINTSQL from any client within the domain (not from DMZ).
When I try to connect same database from SERVER1 (in DMZ), I don't see SHAREPOINTSQL listing when I am in SQL Enterprise Manager. I was hoping to see two entries (one for default database as SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could see de
fault database and connection fine.
Do I need to do any special setup to connect from SERVER1 to SERVER2\SHAREPOINTSQL ?
Hope I explained clearly
Thanks
Port 1433 was opened for firewall. As I said, I could connect SERVER1 to SERVER2 (default database) with out any problem.
Thanks,
Bob
"Bob Robert" wrote:
> Hi,
> We are implementing ShaprePoint Application.
> SharePoint installation is completed and the server is in the DMZ (behind the firewall). Name it as SERVER1
> Also, we installed SQL Server database (SHAREPOINTSQL) on a server as second instance (we already had one database). Name it as SERVER2.
> I could connect SHAREPOINTSQL from any client within the domain (not from DMZ).
> When I try to connect same database from SERVER1 (in DMZ), I don't see SHAREPOINTSQL listing when I am in SQL Enterprise Manager. I was hoping to see two entries (one for default database as SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could see
default database and connection fine.
> Do I need to do any special setup to connect from SERVER1 to SERVER2\SHAREPOINTSQL ?
> Hope I explained clearly
> Thanks
|||Any update from Guru's. I am still having problem
"Bob Robert" wrote:
> Hi,
> We are implementing ShaprePoint Application.
> SharePoint installation is completed and the server is in the DMZ (behind the firewall). Name it as SERVER1
> Also, we installed SQL Server database (SHAREPOINTSQL) on a server as second instance (we already had one database). Name it as SERVER2.
> I could connect SHAREPOINTSQL from any client within the domain (not from DMZ).
> When I try to connect same database from SERVER1 (in DMZ), I don't see SHAREPOINTSQL listing when I am in SQL Enterprise Manager. I was hoping to see two entries (one for default database as SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could see
default database and connection fine.
> Do I need to do any special setup to connect from SERVER1 to SERVER2\SHAREPOINTSQL ?
> Hope I explained clearly
> Thanks
|||I found some thing interesting. After opening all the ports, I could able to connect named instance even though named instance was using port 1434.
"Bob Robert" wrote:
[vbcol=seagreen]
> Any update from Guru's. I am still having problem
> "Bob Robert" wrote:
e default database and connection fine.[vbcol=seagreen]
|||Bob, to connect to instances of SQL there are more ports required, 1434 from memory, you'll find info on this on TechNet if you search under SQL.
Steven Collier
SharePoint Portal Server MVP
http://mvp.support.microsoft.com
"Bob Robert" wrote:
[vbcol=seagreen]
> I found some thing interesting. After opening all the ports, I could able to connect named instance even though named instance was using port 1434.
> "Bob Robert" wrote:
see default database and connection fine.[vbcol=seagreen]
|||Run "Server Network Utility" on the server machine (the one you cannot connect to, probably the
named instance), and check what port number it is using, Open for that port in the firewalls. Also,
You might want to fix the port number by typing ion the port number...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bob Robert" <BobRobert@.discussions.microsoft.com> wrote in message
news:955A498C-6CFA-46F1-B9A1-53075DA9AD42@.microsoft.com...
> I found some thing interesting. After opening all the ports, I could able to connect named
instance even though named instance was using port 1434.[vbcol=seagreen]
> "Bob Robert" wrote:
it as SERVER1[vbcol=seagreen]
already had one database). Name it as SERVER2.[vbcol=seagreen]
when I am in SQL Enterprise Manager. I was hoping to see two entries (one for default database as
SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could see default database and connection fine.[vbcol=seagreen]
DMZ to SQL Server 2nd instance connection issue
Hi,
We are implementing ShaprePoint Application.
SharePoint installation is completed and the server is in the DMZ (behind th
e firewall). Name it as SERVER1
Also, we installed SQL Server database (SHAREPOINTSQL) on a server as second
instance (we already had one database). Name it as SERVER2.
I could connect SHAREPOINTSQL from any client within the domain (not from DM
Z).
When I try to connect same database from SERVER1 (in DMZ), I don't see SHARE
POINTSQL listing when I am in SQL Enterprise Manager. I was hoping to see tw
o entries (one for default database as SERVER2 and second one as SERVER2\SHA
REPOINTSQL). I could see de
fault database and connection fine.
Do I need to do any special setup to connect from SERVER1 to SERVER2\SHAREPO
INTSQL ?
Hope I explained clearly
ThanksPort 1433 was opened for firewall. As I said, I could connect SERVER1 to SER
VER2 (default database) with out any problem.
Thanks,
Bob
"Bob Robert" wrote:
> Hi,
> We are implementing ShaprePoint Application.
> SharePoint installation is completed and the server is in the DMZ (behind
the firewall). Name it as SERVER1
> Also, we installed SQL Server database (SHAREPOINTSQL) on a server as seco
nd instance (we already had one database). Name it as SERVER2.
> I could connect SHAREPOINTSQL from any client within the domain (not from
DMZ).
> When I try to connect same database from SERVER1 (in DMZ), I don't see SHAREPOINTS
QL listing when I am in SQL Enterprise Manager. I was hoping to see two entries (one
for default database as SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could s
ee
default database and connection fine.
> Do I need to do any special setup to connect from SERVER1 to SERVER2\SHARE
POINTSQL ?
> Hope I explained clearly
> Thanks|||Any update from Guru's. I am still having problem
"Bob Robert" wrote:
> Hi,
> We are implementing ShaprePoint Application.
> SharePoint installation is completed and the server is in the DMZ (behind
the firewall). Name it as SERVER1
> Also, we installed SQL Server database (SHAREPOINTSQL) on a server as seco
nd instance (we already had one database). Name it as SERVER2.
> I could connect SHAREPOINTSQL from any client within the domain (not from
DMZ).
> When I try to connect same database from SERVER1 (in DMZ), I don't see SHAREPOINTS
QL listing when I am in SQL Enterprise Manager. I was hoping to see two entries (one
for default database as SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could s
ee
default database and connection fine.
> Do I need to do any special setup to connect from SERVER1 to SERVER2\SHARE
POINTSQL ?
> Hope I explained clearly
> Thanks|||I found some thing interesting. After opening all the ports, I could able to
connect named instance even though named instance was using port 1434.
"Bob Robert" wrote:
[vbcol=seagreen]
> Any update from Guru's. I am still having problem
> "Bob Robert" wrote:
>
e default database and connection fine.[vbcol=seagreen]|||Bob, to connect to instances of SQL there are more ports required, 1434 from
memory, you'll find info on this on technet if you search under SQL.
Steven Collier
SharePoint Portal Server MVP
http://mvp.support.microsoft.com
"Bob Robert" wrote:
[vbcol=seagreen]
> I found some thing interesting. After opening all the ports, I could able
to connect named instance even though named instance was using port 1434.
> "Bob Robert" wrote:
>
see default database and connection fine.[vbcol=seagreen]|||Run "Server Network Utility" on the server machine (the one you cannot conne
ct to, probably the
named instance), and check what port number it is using, Open for that port
in the firewalls. Also,
You might want to fix the port number by typing ion the port number...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bob Robert" <BobRobert@.discussions.microsoft.com> wrote in message
news:955A498C-6CFA-46F1-B9A1-53075DA9AD42@.microsoft.com...
> I found some thing interesting. After opening all the ports, I could able to conne
ct named
instance even though named instance was using port 1434.[vbcol=seagreen]
> "Bob Robert" wrote:
>
it as SERVER1[vbcol=seagreen]
already had one database). Name it as SERVER2.[vbcol=seagreen]
when I am in SQL Enterprise Manager. I was hoping to see two entries (one fo
r default database as
SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could see default database and connectio
n fine.[vbcol=seagreen]
We are implementing ShaprePoint Application.
SharePoint installation is completed and the server is in the DMZ (behind th
e firewall). Name it as SERVER1
Also, we installed SQL Server database (SHAREPOINTSQL) on a server as second
instance (we already had one database). Name it as SERVER2.
I could connect SHAREPOINTSQL from any client within the domain (not from DM
Z).
When I try to connect same database from SERVER1 (in DMZ), I don't see SHARE
POINTSQL listing when I am in SQL Enterprise Manager. I was hoping to see tw
o entries (one for default database as SERVER2 and second one as SERVER2\SHA
REPOINTSQL). I could see de
fault database and connection fine.
Do I need to do any special setup to connect from SERVER1 to SERVER2\SHAREPO
INTSQL ?
Hope I explained clearly
ThanksPort 1433 was opened for firewall. As I said, I could connect SERVER1 to SER
VER2 (default database) with out any problem.
Thanks,
Bob
"Bob Robert" wrote:
> Hi,
> We are implementing ShaprePoint Application.
> SharePoint installation is completed and the server is in the DMZ (behind
the firewall). Name it as SERVER1
> Also, we installed SQL Server database (SHAREPOINTSQL) on a server as seco
nd instance (we already had one database). Name it as SERVER2.
> I could connect SHAREPOINTSQL from any client within the domain (not from
DMZ).
> When I try to connect same database from SERVER1 (in DMZ), I don't see SHAREPOINTS
QL listing when I am in SQL Enterprise Manager. I was hoping to see two entries (one
for default database as SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could s
ee
default database and connection fine.
> Do I need to do any special setup to connect from SERVER1 to SERVER2\SHARE
POINTSQL ?
> Hope I explained clearly
> Thanks|||Any update from Guru's. I am still having problem
"Bob Robert" wrote:
> Hi,
> We are implementing ShaprePoint Application.
> SharePoint installation is completed and the server is in the DMZ (behind
the firewall). Name it as SERVER1
> Also, we installed SQL Server database (SHAREPOINTSQL) on a server as seco
nd instance (we already had one database). Name it as SERVER2.
> I could connect SHAREPOINTSQL from any client within the domain (not from
DMZ).
> When I try to connect same database from SERVER1 (in DMZ), I don't see SHAREPOINTS
QL listing when I am in SQL Enterprise Manager. I was hoping to see two entries (one
for default database as SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could s
ee
default database and connection fine.
> Do I need to do any special setup to connect from SERVER1 to SERVER2\SHARE
POINTSQL ?
> Hope I explained clearly
> Thanks|||I found some thing interesting. After opening all the ports, I could able to
connect named instance even though named instance was using port 1434.
"Bob Robert" wrote:
[vbcol=seagreen]
> Any update from Guru's. I am still having problem
> "Bob Robert" wrote:
>
e default database and connection fine.[vbcol=seagreen]|||Bob, to connect to instances of SQL there are more ports required, 1434 from
memory, you'll find info on this on technet if you search under SQL.
Steven Collier
SharePoint Portal Server MVP
http://mvp.support.microsoft.com
"Bob Robert" wrote:
[vbcol=seagreen]
> I found some thing interesting. After opening all the ports, I could able
to connect named instance even though named instance was using port 1434.
> "Bob Robert" wrote:
>
see default database and connection fine.[vbcol=seagreen]|||Run "Server Network Utility" on the server machine (the one you cannot conne
ct to, probably the
named instance), and check what port number it is using, Open for that port
in the firewalls. Also,
You might want to fix the port number by typing ion the port number...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bob Robert" <BobRobert@.discussions.microsoft.com> wrote in message
news:955A498C-6CFA-46F1-B9A1-53075DA9AD42@.microsoft.com...
> I found some thing interesting. After opening all the ports, I could able to conne
ct named
instance even though named instance was using port 1434.[vbcol=seagreen]
> "Bob Robert" wrote:
>
it as SERVER1[vbcol=seagreen]
already had one database). Name it as SERVER2.[vbcol=seagreen]
when I am in SQL Enterprise Manager. I was hoping to see two entries (one fo
r default database as
SERVER2 and second one as SERVER2\SHAREPOINTSQL). I could see default database and connectio
n fine.[vbcol=seagreen]
Friday, February 17, 2012
Distributed transaction error, Help pls
I post this in ASP incase too.. thanks for any help pinning this one
anyone
My hosting recently upgraded their firewall , file server
and sql server and now my existing code fails whenever
I use
then you normal ASP webpage,
with odbc and sql calls , html and
and bottom of the page, the abort procedure to produce nice error to end user
if one occurs.
' The Transacted Script Abort Handler. This sub-routine
' will be called if the script transacted aborts
Sub OnTransactionAbort()
Dim objErrorInfo
Set objErrorInfo = Server.GetLastError
response.clear
Response.write "FULL ERROR DETAILS"
Response.Write("ASPCode = " & objErrorInfo.ASPCode&"")
Response.Write("ASPDescription = " & objErrorInfo.ASPDescription&"")
Response.Write("Category = " & objErrorInfo.Category&"")
Response.Write("Column = " & objErrorInfo.Column&"")
Response.Write("Description = " & objErrorInfo.Description&"")
Response.Write("File = " & objErrorInfo.File&"")
Response.Write("Line = " & objErrorInfo.Line&"")
Response.Write("Number = " & objErrorInfo.Number&"")
Response.Write("Source = " & objErrorInfo.Source&"")
Response.Write ""
then some ifs to redirect to alternative
page one specified errors.
Worked very well for 8months on their
old server using sql7 and IIS5
assume it was still Win2000 fileserver/webserver
I have reduce some of the code above.
Now they dont understand this piece of
code. But I got the code from a developer network who said was only
way to trap all errors including SQL,ODBC,JET,ASP calls.
Now my pages that use this on their new web server, firewall, SQL2000 setup
gives the following output instead of
processing and working as it used too,
FULL ERROR DETAILS
ASPCode =
ASPDescription =
Category = Microsoft OLE DB Provider for SQL Server
Column = -1
Description = Distributed transaction error
File = /anypagethatdoesa-sqlserveropen.asp
Line = 44
Number = -2147168246
Source =
They seem to think its my coding.. which it is not..
it seems to me a problem with the transactional service setup
and sql setup permissions or maybe firewall blocking..
have you any clues where i can direct them to look to
so we can fix this issue cheers.As far as I know MS DTC service will assign a port dynamically (different from 1433) so it won't pass through firewall...
Originally posted by pss2010
I post this in ASP incase too.. thanks for any help pinning this one
anyone
My hosting recently upgraded their firewall , file server
and sql server and now my existing code fails whenever
I use
then you normal ASP webpage,
with odbc and sql calls , html and
and bottom of the page, the abort procedure to produce nice error to end user
if one occurs.
' The Transacted Script Abort Handler. This sub-routine
' will be called if the script transacted aborts
Sub OnTransactionAbort()
Dim objErrorInfo
Set objErrorInfo = Server.GetLastError
response.clear
Response.write "FULL ERROR DETAILS"
Response.Write("ASPCode = " & objErrorInfo.ASPCode&"")
Response.Write("ASPDescription = " & objErrorInfo.ASPDescription&"")
Response.Write("Category = " & objErrorInfo.Category&"")
Response.Write("Column = " & objErrorInfo.Column&"")
Response.Write("Description = " & objErrorInfo.Description&"")
Response.Write("File = " & objErrorInfo.File&"")
Response.Write("Line = " & objErrorInfo.Line&"")
Response.Write("Number = " & objErrorInfo.Number&"")
Response.Write("Source = " & objErrorInfo.Source&"")
Response.Write ""
then some ifs to redirect to alternative
page one specified errors.
Worked very well for 8months on their
old server using sql7 and IIS5
assume it was still Win2000 fileserver/webserver
I have reduce some of the code above.
Now they dont understand this piece of
code. But I got the code from a developer network who said was only
way to trap all errors including SQL,ODBC,JET,ASP calls.
Now my pages that use this on their new web server, firewall, SQL2000 setup
gives the following output instead of
processing and working as it used too,
FULL ERROR DETAILS
ASPCode =
ASPDescription =
Category = Microsoft OLE DB Provider for SQL Server
Column = -1
Description = Distributed transaction error
File = /anypagethatdoesa-sqlserveropen.asp
Line = 44
Number = -2147168246
Source =
They seem to think its my coding.. which it is not..
it seems to me a problem with the transactional service setup
and sql setup permissions or maybe firewall blocking..
have you any clues where i can direct them to look to
so we can fix this issue cheers.
anyone
My hosting recently upgraded their firewall , file server
and sql server and now my existing code fails whenever
I use
then you normal ASP webpage,
with odbc and sql calls , html and
and bottom of the page, the abort procedure to produce nice error to end user
if one occurs.
' The Transacted Script Abort Handler. This sub-routine
' will be called if the script transacted aborts
Sub OnTransactionAbort()
Dim objErrorInfo
Set objErrorInfo = Server.GetLastError
response.clear
Response.write "FULL ERROR DETAILS"
Response.Write("ASPCode = " & objErrorInfo.ASPCode&"")
Response.Write("ASPDescription = " & objErrorInfo.ASPDescription&"")
Response.Write("Category = " & objErrorInfo.Category&"")
Response.Write("Column = " & objErrorInfo.Column&"")
Response.Write("Description = " & objErrorInfo.Description&"")
Response.Write("File = " & objErrorInfo.File&"")
Response.Write("Line = " & objErrorInfo.Line&"")
Response.Write("Number = " & objErrorInfo.Number&"")
Response.Write("Source = " & objErrorInfo.Source&"")
Response.Write ""
then some ifs to redirect to alternative
page one specified errors.
Worked very well for 8months on their
old server using sql7 and IIS5
assume it was still Win2000 fileserver/webserver
I have reduce some of the code above.
Now they dont understand this piece of
code. But I got the code from a developer network who said was only
way to trap all errors including SQL,ODBC,JET,ASP calls.
Now my pages that use this on their new web server, firewall, SQL2000 setup
gives the following output instead of
processing and working as it used too,
FULL ERROR DETAILS
ASPCode =
ASPDescription =
Category = Microsoft OLE DB Provider for SQL Server
Column = -1
Description = Distributed transaction error
File = /anypagethatdoesa-sqlserveropen.asp
Line = 44
Number = -2147168246
Source =
They seem to think its my coding.. which it is not..
it seems to me a problem with the transactional service setup
and sql setup permissions or maybe firewall blocking..
have you any clues where i can direct them to look to
so we can fix this issue cheers.As far as I know MS DTC service will assign a port dynamically (different from 1433) so it won't pass through firewall...
Originally posted by pss2010
I post this in ASP incase too.. thanks for any help pinning this one
anyone
My hosting recently upgraded their firewall , file server
and sql server and now my existing code fails whenever
I use
then you normal ASP webpage,
with odbc and sql calls , html and
and bottom of the page, the abort procedure to produce nice error to end user
if one occurs.
' The Transacted Script Abort Handler. This sub-routine
' will be called if the script transacted aborts
Sub OnTransactionAbort()
Dim objErrorInfo
Set objErrorInfo = Server.GetLastError
response.clear
Response.write "FULL ERROR DETAILS"
Response.Write("ASPCode = " & objErrorInfo.ASPCode&"")
Response.Write("ASPDescription = " & objErrorInfo.ASPDescription&"")
Response.Write("Category = " & objErrorInfo.Category&"")
Response.Write("Column = " & objErrorInfo.Column&"")
Response.Write("Description = " & objErrorInfo.Description&"")
Response.Write("File = " & objErrorInfo.File&"")
Response.Write("Line = " & objErrorInfo.Line&"")
Response.Write("Number = " & objErrorInfo.Number&"")
Response.Write("Source = " & objErrorInfo.Source&"")
Response.Write ""
then some ifs to redirect to alternative
page one specified errors.
Worked very well for 8months on their
old server using sql7 and IIS5
assume it was still Win2000 fileserver/webserver
I have reduce some of the code above.
Now they dont understand this piece of
code. But I got the code from a developer network who said was only
way to trap all errors including SQL,ODBC,JET,ASP calls.
Now my pages that use this on their new web server, firewall, SQL2000 setup
gives the following output instead of
processing and working as it used too,
FULL ERROR DETAILS
ASPCode =
ASPDescription =
Category = Microsoft OLE DB Provider for SQL Server
Column = -1
Description = Distributed transaction error
File = /anypagethatdoesa-sqlserveropen.asp
Line = 44
Number = -2147168246
Source =
They seem to think its my coding.. which it is not..
it seems to me a problem with the transactional service setup
and sql setup permissions or maybe firewall blocking..
have you any clues where i can direct them to look to
so we can fix this issue cheers.
Distributed Transaction Error with SQL 2000
I have 2 SQL 2000 servers connected with network.
There is no firewall between them.
MSDTC is running on both servers.
One of the 2 servers is called locale the other is called base.
The base one is a linked server in the locale SQL server.
The base server is on Win server 2003 while the locale server is on Win XP SP1.
The distributed transaction is located in the locale server and trying to insert into the base server.
Every time I encounter this error:
Server: Msg 7391, Level 16, State 1, Procedure proc_UpdateDataFromLocalToServer, Line 8
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]
-
What are the possible causes of this error?
Thank you.
Bishoy
Can you try to define a linked server between these two servers and execute the script containing the distributed transaction?|||Take help from this KBA http://support.microsoft.com/kb/839279 & http://support.microsoft.com/kb/329332 for a solution.
Subscribe to:
Posts (Atom)