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]

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]

Distributed transaction completed. Either enlist this session in a new transaction or the NU

i have a sequence container in my my sequence container i have a script task for drop the existing tables. This seq. container connected to another seq. container. all these are in for each loop container when i run the package it's work fine for 1st looop but it gives me error for second execution.

Message is like this:

Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.

I have checked with MSDTC and timeout.

timeout is 30.

any other suggest .

thanks

Manoj Verma

Distributed transaction completed. Either enlist this session in a new transaction or the

I am getting this error :

Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.Data.OleDb.OleDbException: Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.

have anybody idea?!

Hi,

From the exception message, we can see that you're using a distributed transaction.

Are you using a TransactionScopt object? If yes, this exception is often thrown when you're trying to use a distributed trasaction that has been committed already. In this case, you can either use this transaction before it's completed or start a new one for this operation.

HTH. If anything is unclear, please feel free to mark this post as Not Answered and post your reply. Thanks!

Distributed Transaction completed error

Hello,

I am running a package that has an Execute SQL Task, a Data Flow Task, and then an Execute SQL Task.

My Data Flow Task in set to run in a transaction (ReadCommitted). The first Execute SQL Task and the Data Flow Task run successfully. When the last Execute SQL Task runs, I get the error message:
"[Execute SQL Task] Error: Executing the query "select start_time from TRD_JOB_HISTORY where job_history_id = ?" failed with the following error: "Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly."

If I set the last Execute SQL Task's TransactionOption to 'Required' (to have it run in a transaction), the package runs successfully. Unfortunately, I don't want that statement to run in a transaction. If I set the last Execute SQL Task's TransactionOption to 'NotSupported', I get the same error message.

Is there anything I can set to have it use "the NULL transaction" or ignore transactions completely?

Thanks in advance,
Jessica
This is strange, it sounds as tho it should work.

Have you tried encapsulating the first Execute SQL Task and the data-flow task in a Sequence container and running the transaction over that Sequence container.

Which container instigates the transaction?
What happens if you set TransactionOption=Supported on the second Execute SQL Task?

-Jamie