I have created a tool using vb.net,with mssql as backend.i need to
create the database and the table in the database using some scripts or
what ever relevent methods.How can we make the database while
installing the software.you could call the following from VB.NET:
osql.exe -Usa -Ppassword -i d:\dbr\create_database_script.sql -n
-oD:\DBR\OUTPUT\SQL_SCRIPT_LOGS\outputfile.txt
--
--
Sasan Saidi
Senior DBA
MSc in CS, MCSE4, IBM Certified MQ 5.3 Administrator
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Armagadone" wrote:
> I have created a tool using vb.net,with mssql as backend.i need to
> create the database and the table in the database using some scripts or
> what ever relevent methods.How can we make the database while
> installing the software.
>
Showing posts with label net. Show all posts
Showing posts with label net. Show all posts
Wednesday, March 28, 2012
MSSQL
I have created a tool using vb.net,with mssql as backend.i need to
create the database and the table in the database using some scripts or
what ever relevent methods.How can we make the database while
installing the software.
you could call the following from VB.NET:
osql.exe -Usa -Ppassword -i d:\dbr\create_database_script.sql -n
-oD:\DBR\OUTPUT\SQL_SCRIPT_LOGS\outputfile.txt
--
Sasan Saidi
Senior DBA
MSc in CS, MCSE4, IBM Certified MQ 5.3 Administrator
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Armagadone" wrote:
> I have created a tool using vb.net,with mssql as backend.i need to
> create the database and the table in the database using some scripts or
> what ever relevent methods.How can we make the database while
> installing the software.
>
create the database and the table in the database using some scripts or
what ever relevent methods.How can we make the database while
installing the software.
you could call the following from VB.NET:
osql.exe -Usa -Ppassword -i d:\dbr\create_database_script.sql -n
-oD:\DBR\OUTPUT\SQL_SCRIPT_LOGS\outputfile.txt
--
Sasan Saidi
Senior DBA
MSc in CS, MCSE4, IBM Certified MQ 5.3 Administrator
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Armagadone" wrote:
> I have created a tool using vb.net,with mssql as backend.i need to
> create the database and the table in the database using some scripts or
> what ever relevent methods.How can we make the database while
> installing the software.
>
MSSQL
I have created a tool using vb.net,with mssql as backend.i need to
create the database and the table in the database using some scripts or
what ever relevent methods.How can we make the database while
installing the software.you could call the following from VB.NET:
osql.exe -Usa -Ppassword -i d:\dbr\create_database_script.sql -n
- oD:\DBR\OUTPUT\SQL_SCRIPT_LOGS\outputfil
e.txt
--
Sasan Saidi
Senior DBA
MSc in CS, MCSE4, IBM Certified MQ 5.3 Administrator
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Armagadone" wrote:
> I have created a tool using vb.net,with mssql as backend.i need to
> create the database and the table in the database using some scripts or
> what ever relevent methods.How can we make the database while
> installing the software.
>
create the database and the table in the database using some scripts or
what ever relevent methods.How can we make the database while
installing the software.you could call the following from VB.NET:
osql.exe -Usa -Ppassword -i d:\dbr\create_database_script.sql -n
- oD:\DBR\OUTPUT\SQL_SCRIPT_LOGS\outputfil
e.txt
--
Sasan Saidi
Senior DBA
MSc in CS, MCSE4, IBM Certified MQ 5.3 Administrator
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Armagadone" wrote:
> I have created a tool using vb.net,with mssql as backend.i need to
> create the database and the table in the database using some scripts or
> what ever relevent methods.How can we make the database while
> installing the software.
>
MSSQ server service (widnows service) account configuration --
Hi Folks,
We have some inhouse applications developed using microsoft technologies
like C#.net,asp.net and sql server 2000 and we have third party applicatio
ns
using sql server 2000.
In all our sql servers we configured as below.
we created domain level user accounts(service accounts) like SA_Server1.
we made that SA_server1 as member of local administrator group on the
server where SQLserver2000 software got installed.
we are using SA_server1 account to run mssqlserver service (windows
service).
All our proudction sql server are windows clusters with 2 nodes.
we have mixed mode authentication. And all users in Builtin/Administrators
group are sql users.
Using that domain level service account (SA_Server1) credentials,we can
login to that particualr sql server locally to check everything is working
fine.
Everything is working fine.
Recently Sarbanes-Oxley Audit conducted in our company.
One of the questions they asked is as given below.
1.why Interactive log-in is turned ON for that mssqlservice accounts? (for
SA_Server1) ?
They don't want any one to login to that server locally using that domain
account credentials.
2.Why builtin/administrators are part of sql users?
How can we prevent anyone logging in to that sql server locally using that
service account credentials?
we will be giving that credentials for the 2,3 administrative people only.
But we don't want them also to login to that server locally using service
account credentials.
They should login to that server using their own windows accounts.
How can we turn OFF that interactive log-on?
is it in group policy or local policy or Active directory member profile?
What are the best security practices for sql server 2000 configuration
mainly with service accounts?
Any kind of help is greatly appreciated.
--KumarDeny Logon locally right to the account used to start sql server services is
recommended to prevent someone from using sql server service account to logi
n
to the sql server.
Hope this hepls
"Kumar" wrote:
> Hi Folks,
> We have some inhouse applications developed using microsoft technologies
> like C#.net,asp.net and sql server 2000 and we have third party applicat
ions
> using sql server 2000.
> In all our sql servers we configured as below.
> we created domain level user accounts(service accounts) like SA_Server1.
> we made that SA_server1 as member of local administrator group on the
> server where SQLserver2000 software got installed.
> we are using SA_server1 account to run mssqlserver service (windows
> service).
> All our proudction sql server are windows clusters with 2 nodes.
> we have mixed mode authentication. And all users in Builtin/Administrators
> group are sql users.
> Using that domain level service account (SA_Server1) credentials,we can
> login to that particualr sql server locally to check everything is working
> fine.
> Everything is working fine.
>
> Recently Sarbanes-Oxley Audit conducted in our company.
> One of the questions they asked is as given below.
> 1.why Interactive log-in is turned ON for that mssqlservice accounts? (fo
r
> SA_Server1) ?
> They don't want any one to login to that server locally using that doma
in
> account credentials.
> 2.Why builtin/administrators are part of sql users?
>
> How can we prevent anyone logging in to that sql server locally using that
> service account credentials?
> we will be giving that credentials for the 2,3 administrative people only
.
> But we don't want them also to login to that server locally using service
> account credentials.
> They should login to that server using their own windows accounts.
>
> How can we turn OFF that interactive log-on?
> is it in group policy or local policy or Active directory member profile
?
>
> What are the best security practices for sql server 2000 configuration
> mainly with service accounts?
>
>
> Any kind of help is greatly appreciated.
>
> --Kumar
>
We have some inhouse applications developed using microsoft technologies
like C#.net,asp.net and sql server 2000 and we have third party applicatio
ns
using sql server 2000.
In all our sql servers we configured as below.
we created domain level user accounts(service accounts) like SA_Server1.
we made that SA_server1 as member of local administrator group on the
server where SQLserver2000 software got installed.
we are using SA_server1 account to run mssqlserver service (windows
service).
All our proudction sql server are windows clusters with 2 nodes.
we have mixed mode authentication. And all users in Builtin/Administrators
group are sql users.
Using that domain level service account (SA_Server1) credentials,we can
login to that particualr sql server locally to check everything is working
fine.
Everything is working fine.
Recently Sarbanes-Oxley Audit conducted in our company.
One of the questions they asked is as given below.
1.why Interactive log-in is turned ON for that mssqlservice accounts? (for
SA_Server1) ?
They don't want any one to login to that server locally using that domain
account credentials.
2.Why builtin/administrators are part of sql users?
How can we prevent anyone logging in to that sql server locally using that
service account credentials?
we will be giving that credentials for the 2,3 administrative people only.
But we don't want them also to login to that server locally using service
account credentials.
They should login to that server using their own windows accounts.
How can we turn OFF that interactive log-on?
is it in group policy or local policy or Active directory member profile?
What are the best security practices for sql server 2000 configuration
mainly with service accounts?
Any kind of help is greatly appreciated.
--KumarDeny Logon locally right to the account used to start sql server services is
recommended to prevent someone from using sql server service account to logi
n
to the sql server.
Hope this hepls
"Kumar" wrote:
> Hi Folks,
> We have some inhouse applications developed using microsoft technologies
> like C#.net,asp.net and sql server 2000 and we have third party applicat
ions
> using sql server 2000.
> In all our sql servers we configured as below.
> we created domain level user accounts(service accounts) like SA_Server1.
> we made that SA_server1 as member of local administrator group on the
> server where SQLserver2000 software got installed.
> we are using SA_server1 account to run mssqlserver service (windows
> service).
> All our proudction sql server are windows clusters with 2 nodes.
> we have mixed mode authentication. And all users in Builtin/Administrators
> group are sql users.
> Using that domain level service account (SA_Server1) credentials,we can
> login to that particualr sql server locally to check everything is working
> fine.
> Everything is working fine.
>
> Recently Sarbanes-Oxley Audit conducted in our company.
> One of the questions they asked is as given below.
> 1.why Interactive log-in is turned ON for that mssqlservice accounts? (fo
r
> SA_Server1) ?
> They don't want any one to login to that server locally using that doma
in
> account credentials.
> 2.Why builtin/administrators are part of sql users?
>
> How can we prevent anyone logging in to that sql server locally using that
> service account credentials?
> we will be giving that credentials for the 2,3 administrative people only
.
> But we don't want them also to login to that server locally using service
> account credentials.
> They should login to that server using their own windows accounts.
>
> How can we turn OFF that interactive log-on?
> is it in group policy or local policy or Active directory member profile
?
>
> What are the best security practices for sql server 2000 configuration
> mainly with service accounts?
>
>
> Any kind of help is greatly appreciated.
>
> --Kumar
>
MSSQ server service (widnows service) account configuration --
Hi Folks,
We have some inhouse applications developed using microsoft technologies
like C#.net,asp.net and sql server 2000 and we have third party applications
using sql server 2000.
In all our sql servers we configured as below.
we created domain level user accounts(service accounts) like SA_Server1.
we made that SA_server1 as member of local administrator group on the
server where SQLserver2000 software got installed.
we are using SA_server1 account to run mssqlserver service (windows
service).
All our proudction sql server are windows clusters with 2 nodes.
we have mixed mode authentication. And all users in Builtin/Administrators
group are sql users.
Using that domain level service account (SA_Server1) credentials,we can
login to that particualr sql server locally to check everything is working
fine.
Everything is working fine.
Recently Sarbanes-Oxley Audit conducted in our company.
One of the questions they asked is as given below.
1.why Interactive log-in is turned ON for that mssqlservice accounts? (for
SA_Server1) ?
They don't want any one to login to that server locally using that domain
account credentials.
2.Why builtin/administrators are part of sql users?
How can we prevent anyone logging in to that sql server locally using that
service account credentials?
we will be giving that credentials for the 2,3 administrative people only.
But we don't want them also to login to that server locally using service
account credentials.
They should login to that server using their own windows accounts.
How can we turn OFF that interactive log-on?
is it in group policy or local policy or Active directory member profile?
What are the best security practices for sql server 2000 configuration
mainly with service accounts?
Any kind of help is greatly appreciated.
--KumarDeny Logon locally right to the account used to start sql server services is
recommended to prevent someone from using sql server service account to login
to the sql server.
Hope this hepls
"Kumar" wrote:
> Hi Folks,
> We have some inhouse applications developed using microsoft technologies
> like C#.net,asp.net and sql server 2000 and we have third party applications
> using sql server 2000.
> In all our sql servers we configured as below.
> we created domain level user accounts(service accounts) like SA_Server1.
> we made that SA_server1 as member of local administrator group on the
> server where SQLserver2000 software got installed.
> we are using SA_server1 account to run mssqlserver service (windows
> service).
> All our proudction sql server are windows clusters with 2 nodes.
> we have mixed mode authentication. And all users in Builtin/Administrators
> group are sql users.
> Using that domain level service account (SA_Server1) credentials,we can
> login to that particualr sql server locally to check everything is working
> fine.
> Everything is working fine.
>
> Recently Sarbanes-Oxley Audit conducted in our company.
> One of the questions they asked is as given below.
> 1.why Interactive log-in is turned ON for that mssqlservice accounts? (for
> SA_Server1) ?
> They don't want any one to login to that server locally using that domain
> account credentials.
> 2.Why builtin/administrators are part of sql users?
>
> How can we prevent anyone logging in to that sql server locally using that
> service account credentials?
> we will be giving that credentials for the 2,3 administrative people only.
> But we don't want them also to login to that server locally using service
> account credentials.
> They should login to that server using their own windows accounts.
>
> How can we turn OFF that interactive log-on?
> is it in group policy or local policy or Active directory member profile?
>
> What are the best security practices for sql server 2000 configuration
> mainly with service accounts?
>
>
> Any kind of help is greatly appreciated.
>
> --Kumar
>
We have some inhouse applications developed using microsoft technologies
like C#.net,asp.net and sql server 2000 and we have third party applications
using sql server 2000.
In all our sql servers we configured as below.
we created domain level user accounts(service accounts) like SA_Server1.
we made that SA_server1 as member of local administrator group on the
server where SQLserver2000 software got installed.
we are using SA_server1 account to run mssqlserver service (windows
service).
All our proudction sql server are windows clusters with 2 nodes.
we have mixed mode authentication. And all users in Builtin/Administrators
group are sql users.
Using that domain level service account (SA_Server1) credentials,we can
login to that particualr sql server locally to check everything is working
fine.
Everything is working fine.
Recently Sarbanes-Oxley Audit conducted in our company.
One of the questions they asked is as given below.
1.why Interactive log-in is turned ON for that mssqlservice accounts? (for
SA_Server1) ?
They don't want any one to login to that server locally using that domain
account credentials.
2.Why builtin/administrators are part of sql users?
How can we prevent anyone logging in to that sql server locally using that
service account credentials?
we will be giving that credentials for the 2,3 administrative people only.
But we don't want them also to login to that server locally using service
account credentials.
They should login to that server using their own windows accounts.
How can we turn OFF that interactive log-on?
is it in group policy or local policy or Active directory member profile?
What are the best security practices for sql server 2000 configuration
mainly with service accounts?
Any kind of help is greatly appreciated.
--KumarDeny Logon locally right to the account used to start sql server services is
recommended to prevent someone from using sql server service account to login
to the sql server.
Hope this hepls
"Kumar" wrote:
> Hi Folks,
> We have some inhouse applications developed using microsoft technologies
> like C#.net,asp.net and sql server 2000 and we have third party applications
> using sql server 2000.
> In all our sql servers we configured as below.
> we created domain level user accounts(service accounts) like SA_Server1.
> we made that SA_server1 as member of local administrator group on the
> server where SQLserver2000 software got installed.
> we are using SA_server1 account to run mssqlserver service (windows
> service).
> All our proudction sql server are windows clusters with 2 nodes.
> we have mixed mode authentication. And all users in Builtin/Administrators
> group are sql users.
> Using that domain level service account (SA_Server1) credentials,we can
> login to that particualr sql server locally to check everything is working
> fine.
> Everything is working fine.
>
> Recently Sarbanes-Oxley Audit conducted in our company.
> One of the questions they asked is as given below.
> 1.why Interactive log-in is turned ON for that mssqlservice accounts? (for
> SA_Server1) ?
> They don't want any one to login to that server locally using that domain
> account credentials.
> 2.Why builtin/administrators are part of sql users?
>
> How can we prevent anyone logging in to that sql server locally using that
> service account credentials?
> we will be giving that credentials for the 2,3 administrative people only.
> But we don't want them also to login to that server locally using service
> account credentials.
> They should login to that server using their own windows accounts.
>
> How can we turn OFF that interactive log-on?
> is it in group policy or local policy or Active directory member profile?
>
> What are the best security practices for sql server 2000 configuration
> mainly with service accounts?
>
>
> Any kind of help is greatly appreciated.
>
> --Kumar
>
Monday, March 26, 2012
MSRS2000 Extension Compiled Under VS2005?
We have an MSRS2000 extension that was originally written under VS2003 (.NET
1.1). We have updated our extension and compiled it under VS2005 (.NET 2.0).
We now use the extension under MSRS2005.
We would like to use the same, .NET 2.0-compiled extension dll under
MSRS2000, but receive errors when attempting to configure the extension
(presumably because MSRS2000 uses on .NET 1.1).
Is there a way to configure MSRS2000 to use a .NET 2.0-compiled extension
(without having to maintain two separate code bases - one for the .NET 1.1
extension and one for the .NET 2.0 extension)?
Thank you in advance for any suggestions / ideas.
Bill BThe RS2000 is built on .NET1.1 and runs only under .NET1.1. So, you cannot
have code built with .NET2.0 to run inside RS2000.
If your extension is compiled under 1.1 (VS2003), it might run with RS2005,
depending what the extension does and needing to test it thoroughly, but if
compiled with 2.0, then it can only run with RS2005, not RS2000.
"Bill B" <Bill B@.discussions.microsoft.com> wrote in message
news:495A7A23-F66E-40AA-8C4E-ADA58425AEB8@.microsoft.com...
> We have an MSRS2000 extension that was originally written under VS2003
> (.NET
> 1.1). We have updated our extension and compiled it under VS2005 (.NET
> 2.0).
> We now use the extension under MSRS2005.
> We would like to use the same, .NET 2.0-compiled extension dll under
> MSRS2000, but receive errors when attempting to configure the extension
> (presumably because MSRS2000 uses on .NET 1.1).
> Is there a way to configure MSRS2000 to use a .NET 2.0-compiled extension
> (without having to maintain two separate code bases - one for the .NET 1.1
> extension and one for the .NET 2.0 extension)?
> Thank you in advance for any suggestions / ideas.
> Bill B|||Thanks Norman. I thought that was the case, but wanted to confirm that there
is no update (or planned update) to Reporting Services 2000 to run on .NET
2.0 (and hence support 2.0 extensions).
"Norman Yuan" wrote:
> The RS2000 is built on .NET1.1 and runs only under .NET1.1. So, you cannot
> have code built with .NET2.0 to run inside RS2000.
> If your extension is compiled under 1.1 (VS2003), it might run with RS2005,
> depending what the extension does and needing to test it thoroughly, but if
> compiled with 2.0, then it can only run with RS2005, not RS2000.
>
> "Bill B" <Bill B@.discussions.microsoft.com> wrote in message
> news:495A7A23-F66E-40AA-8C4E-ADA58425AEB8@.microsoft.com...
> > We have an MSRS2000 extension that was originally written under VS2003
> > (.NET
> > 1.1). We have updated our extension and compiled it under VS2005 (.NET
> > 2.0).
> > We now use the extension under MSRS2005.
> >
> > We would like to use the same, .NET 2.0-compiled extension dll under
> > MSRS2000, but receive errors when attempting to configure the extension
> > (presumably because MSRS2000 uses on .NET 1.1).
> >
> > Is there a way to configure MSRS2000 to use a .NET 2.0-compiled extension
> > (without having to maintain two separate code bases - one for the .NET 1.1
> > extension and one for the .NET 2.0 extension)?
> >
> > Thank you in advance for any suggestions / ideas.
> >
> > Bill B
>
>|||Well, the update that runs on 2.0 is RS 2005.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bill B" <BillB@.discussions.microsoft.com> wrote in message
news:F3DAFA28-E5DA-40FD-8897-8E661FC77E09@.microsoft.com...
> Thanks Norman. I thought that was the case, but wanted to confirm that
> there
> is no update (or planned update) to Reporting Services 2000 to run on .NET
> 2.0 (and hence support 2.0 extensions).
> "Norman Yuan" wrote:
>> The RS2000 is built on .NET1.1 and runs only under .NET1.1. So, you
>> cannot
>> have code built with .NET2.0 to run inside RS2000.
>> If your extension is compiled under 1.1 (VS2003), it might run with
>> RS2005,
>> depending what the extension does and needing to test it thoroughly, but
>> if
>> compiled with 2.0, then it can only run with RS2005, not RS2000.
>>
>> "Bill B" <Bill B@.discussions.microsoft.com> wrote in message
>> news:495A7A23-F66E-40AA-8C4E-ADA58425AEB8@.microsoft.com...
>> > We have an MSRS2000 extension that was originally written under VS2003
>> > (.NET
>> > 1.1). We have updated our extension and compiled it under VS2005 (.NET
>> > 2.0).
>> > We now use the extension under MSRS2005.
>> >
>> > We would like to use the same, .NET 2.0-compiled extension dll under
>> > MSRS2000, but receive errors when attempting to configure the extension
>> > (presumably because MSRS2000 uses on .NET 1.1).
>> >
>> > Is there a way to configure MSRS2000 to use a .NET 2.0-compiled
>> > extension
>> > (without having to maintain two separate code bases - one for the .NET
>> > 1.1
>> > extension and one for the .NET 2.0 extension)?
>> >
>> > Thank you in advance for any suggestions / ideas.
>> >
>> > Bill B
>>
1.1). We have updated our extension and compiled it under VS2005 (.NET 2.0).
We now use the extension under MSRS2005.
We would like to use the same, .NET 2.0-compiled extension dll under
MSRS2000, but receive errors when attempting to configure the extension
(presumably because MSRS2000 uses on .NET 1.1).
Is there a way to configure MSRS2000 to use a .NET 2.0-compiled extension
(without having to maintain two separate code bases - one for the .NET 1.1
extension and one for the .NET 2.0 extension)?
Thank you in advance for any suggestions / ideas.
Bill BThe RS2000 is built on .NET1.1 and runs only under .NET1.1. So, you cannot
have code built with .NET2.0 to run inside RS2000.
If your extension is compiled under 1.1 (VS2003), it might run with RS2005,
depending what the extension does and needing to test it thoroughly, but if
compiled with 2.0, then it can only run with RS2005, not RS2000.
"Bill B" <Bill B@.discussions.microsoft.com> wrote in message
news:495A7A23-F66E-40AA-8C4E-ADA58425AEB8@.microsoft.com...
> We have an MSRS2000 extension that was originally written under VS2003
> (.NET
> 1.1). We have updated our extension and compiled it under VS2005 (.NET
> 2.0).
> We now use the extension under MSRS2005.
> We would like to use the same, .NET 2.0-compiled extension dll under
> MSRS2000, but receive errors when attempting to configure the extension
> (presumably because MSRS2000 uses on .NET 1.1).
> Is there a way to configure MSRS2000 to use a .NET 2.0-compiled extension
> (without having to maintain two separate code bases - one for the .NET 1.1
> extension and one for the .NET 2.0 extension)?
> Thank you in advance for any suggestions / ideas.
> Bill B|||Thanks Norman. I thought that was the case, but wanted to confirm that there
is no update (or planned update) to Reporting Services 2000 to run on .NET
2.0 (and hence support 2.0 extensions).
"Norman Yuan" wrote:
> The RS2000 is built on .NET1.1 and runs only under .NET1.1. So, you cannot
> have code built with .NET2.0 to run inside RS2000.
> If your extension is compiled under 1.1 (VS2003), it might run with RS2005,
> depending what the extension does and needing to test it thoroughly, but if
> compiled with 2.0, then it can only run with RS2005, not RS2000.
>
> "Bill B" <Bill B@.discussions.microsoft.com> wrote in message
> news:495A7A23-F66E-40AA-8C4E-ADA58425AEB8@.microsoft.com...
> > We have an MSRS2000 extension that was originally written under VS2003
> > (.NET
> > 1.1). We have updated our extension and compiled it under VS2005 (.NET
> > 2.0).
> > We now use the extension under MSRS2005.
> >
> > We would like to use the same, .NET 2.0-compiled extension dll under
> > MSRS2000, but receive errors when attempting to configure the extension
> > (presumably because MSRS2000 uses on .NET 1.1).
> >
> > Is there a way to configure MSRS2000 to use a .NET 2.0-compiled extension
> > (without having to maintain two separate code bases - one for the .NET 1.1
> > extension and one for the .NET 2.0 extension)?
> >
> > Thank you in advance for any suggestions / ideas.
> >
> > Bill B
>
>|||Well, the update that runs on 2.0 is RS 2005.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bill B" <BillB@.discussions.microsoft.com> wrote in message
news:F3DAFA28-E5DA-40FD-8897-8E661FC77E09@.microsoft.com...
> Thanks Norman. I thought that was the case, but wanted to confirm that
> there
> is no update (or planned update) to Reporting Services 2000 to run on .NET
> 2.0 (and hence support 2.0 extensions).
> "Norman Yuan" wrote:
>> The RS2000 is built on .NET1.1 and runs only under .NET1.1. So, you
>> cannot
>> have code built with .NET2.0 to run inside RS2000.
>> If your extension is compiled under 1.1 (VS2003), it might run with
>> RS2005,
>> depending what the extension does and needing to test it thoroughly, but
>> if
>> compiled with 2.0, then it can only run with RS2005, not RS2000.
>>
>> "Bill B" <Bill B@.discussions.microsoft.com> wrote in message
>> news:495A7A23-F66E-40AA-8C4E-ADA58425AEB8@.microsoft.com...
>> > We have an MSRS2000 extension that was originally written under VS2003
>> > (.NET
>> > 1.1). We have updated our extension and compiled it under VS2005 (.NET
>> > 2.0).
>> > We now use the extension under MSRS2005.
>> >
>> > We would like to use the same, .NET 2.0-compiled extension dll under
>> > MSRS2000, but receive errors when attempting to configure the extension
>> > (presumably because MSRS2000 uses on .NET 1.1).
>> >
>> > Is there a way to configure MSRS2000 to use a .NET 2.0-compiled
>> > extension
>> > (without having to maintain two separate code bases - one for the .NET
>> > 1.1
>> > extension and one for the .NET 2.0 extension)?
>> >
>> > Thank you in advance for any suggestions / ideas.
>> >
>> > Bill B
>>
Friday, March 9, 2012
MS-DTC...Some vulnerability info required
hi...
Sorry if i am putting question at wrong place, guide me.
I have tried 2 exploits (available on net) of Distributed
Transaction Coordinator at 4 different 2k machines.
But after execution of exploit, i dont see any change in
behavior of DTC. It works as it was. The target systems
do not have the required patch/service pack.
Kindly put some suggestions or take me to appropriate group.
Take care...bye
Ok, why 2000 and not 2003 R2? Why are you trying to get in? From the inside
of the network or outside? What exactly did you try? What patches did you
think would fix it?
This could be the case where a later patch fixes the issue or your testing
is a little off. Either way - move to 2003!!!!
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Umer" <Umer@.discussions.microsoft.com> wrote in message
news:DC4A6615-30F7-44C2-BD81-97D4262B14C4@.microsoft.com...
> hi...
> Sorry if i am putting question at wrong place, guide me.
> I have tried 2 exploits (available on net) of Distributed
> Transaction Coordinator at 4 different 2k machines.
> But after execution of exploit, i dont see any change in
> behavior of DTC. It works as it was. The target systems
> do not have the required patch/service pack.
> Kindly put some suggestions or take me to appropriate group.
> Take care...bye
Sorry if i am putting question at wrong place, guide me.
I have tried 2 exploits (available on net) of Distributed
Transaction Coordinator at 4 different 2k machines.
But after execution of exploit, i dont see any change in
behavior of DTC. It works as it was. The target systems
do not have the required patch/service pack.
Kindly put some suggestions or take me to appropriate group.
Take care...bye
Ok, why 2000 and not 2003 R2? Why are you trying to get in? From the inside
of the network or outside? What exactly did you try? What patches did you
think would fix it?
This could be the case where a later patch fixes the issue or your testing
is a little off. Either way - move to 2003!!!!
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Umer" <Umer@.discussions.microsoft.com> wrote in message
news:DC4A6615-30F7-44C2-BD81-97D4262B14C4@.microsoft.com...
> hi...
> Sorry if i am putting question at wrong place, guide me.
> I have tried 2 exploits (available on net) of Distributed
> Transaction Coordinator at 4 different 2k machines.
> But after execution of exploit, i dont see any change in
> behavior of DTC. It works as it was. The target systems
> do not have the required patch/service pack.
> Kindly put some suggestions or take me to appropriate group.
> Take care...bye
MSDTC, Active Diretory, DAO, And Transactions
If this is in the wrong forum, my apologies.
Here is the situation. We have a .Net application that someconsultants developed several years ago. They made use of DAO fordatabase access, using some inbuilt classes like ContextUtil to get atransation environment.
Until last weekend, the envorinment was:
Web application on IIS5 / Windows 2000 Advanced Server
Database on SQL2000 on Windows 2000 Advanced Server
We switched over to a new database server environment - a cluster oftwo Windows 2003 servers wth SQL Server 2000. This requiredActive Directory to be set up on the two database server machines.
Everything worked but this particular application - where it goes toupdate the database. It appears (but since I haven't yet beenable to rebuild the .Net solution) that the error - "Object referencenot set to an instance of object." is in fact a spurious error causedwhen the transation tries to roll back.
I have spent about 10 hours on this, and have come to the conclusionthat the fact I have MSDTC involved on a database server that is in anAD domain, while the web server that is issuing the transaction isoutside that domain is the cause of the problem. Now, I don'twant to put AD on the IIS 5 web server - we are migrating this to a newWin2k3/IIS6 server in 5 or 6 weeks time.
Any suggestions? If I have to, I can move the database for thisparticular app back to the non-clustered Windows 2000 server (which isalso outside the AD domain).
Thanks for your indulgance.
Microsoft requirement and good practice is a database Server is just a member server, it should not have anything to do with AD users. If your application is using DAO(data Access object) which was obselete in 1998 you may need MSDTC, the error could be you have not properly configured distributed transaction in SQL Server. Run a search for distributed transaction in the BOL(books online). The advice keep your application from none database users and AD. Hope this helps.
Here is the situation. We have a .Net application that someconsultants developed several years ago. They made use of DAO fordatabase access, using some inbuilt classes like ContextUtil to get atransation environment.
Until last weekend, the envorinment was:
Web application on IIS5 / Windows 2000 Advanced Server
Database on SQL2000 on Windows 2000 Advanced Server
We switched over to a new database server environment - a cluster oftwo Windows 2003 servers wth SQL Server 2000. This requiredActive Directory to be set up on the two database server machines.
Everything worked but this particular application - where it goes toupdate the database. It appears (but since I haven't yet beenable to rebuild the .Net solution) that the error - "Object referencenot set to an instance of object." is in fact a spurious error causedwhen the transation tries to roll back.
I have spent about 10 hours on this, and have come to the conclusionthat the fact I have MSDTC involved on a database server that is in anAD domain, while the web server that is issuing the transaction isoutside that domain is the cause of the problem. Now, I don'twant to put AD on the IIS 5 web server - we are migrating this to a newWin2k3/IIS6 server in 5 or 6 weeks time.
Any suggestions? If I have to, I can move the database for thisparticular app back to the non-clustered Windows 2000 server (which isalso outside the AD domain).
Thanks for your indulgance.
Microsoft requirement and good practice is a database Server is just a member server, it should not have anything to do with AD users. If your application is using DAO(data Access object) which was obselete in 1998 you may need MSDTC, the error could be you have not properly configured distributed transaction in SQL Server. Run a search for distributed transaction in the BOL(books online). The advice keep your application from none database users and AD. Hope this helps.
Subscribe to:
Posts (Atom)