Showing posts with label mode. Show all posts
Showing posts with label mode. Show all posts

Friday, March 30, 2012

Problem in installing SQLSERVER2000 Developer Edition

You have a TCP/IP alias established created on your computer. Remove it and
setup should complete successfully. Setup starts SQL Server in a mode to
accept only shared memory connections. The alias is preventing setup from
connecting.
Run cliconfg from Start - Run. Go to the ALias tab and delete the alias for
this server, You do not need it. Or should not need it. If you do then
there is another problem that needs to be addressed.
Rand
This posting is provided "as is" with no warranties and confers no rights.Rand!
You the man! I was about to have a heart attack when i had uninstalled our
SQL Developer server and could not install Standard edition. Your suggestio
n worked like a charm! Your advice is excellent even 6 months later.

Monday, March 26, 2012

problem in connecting to MSDE database from the same domain

Hi!
I have installed MSDE 2000 in "Mixed Windows and SQL mode authentication with network access" .following is the command:

setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="password" INSTANCENAME="TempInstance" SECURITYMODE=SQL

Then I created the database TempDB in it.

When I try to connect this database from my program running on my machine , it works fine. But when i try to connect to it from the same program running on a different machine on the same domain.It gives error:

"SQL Server does not exist or access denied ."

Even when i run the same program in my machine to access the same TempDB database on a remote machine that is not in my domain, it works fine.

this is my connection string:
Data Source={Database server's IP Address}\TempInstance;Initial Catalog=TempDB;User ID=sa;PWD=password;

Please help.

KT.What's the operating system for the client from which you are unsuccessfully attempting to connect? What version of MDAC is running on it?

Also, be aware that a named instance install of MSDE will set up to run on a non-default port (ie, not 1433). You can verify your connectivity by determining what port the SQL listener is running on and then using telnet {ip address} {port} from your client machine. You may need to account for the alternate port on your client machine. You can set up an alias for it by running cliconfg at a command prompt on your client machine.

Regards,

hmscott|||Thanks hmscott!

Actually my problem was caused by windows firewall.

regards.
Kuldeep.

Friday, March 9, 2012

Problem deploying custom report item. Items shows in preview screen in VS, but not in server dep

I have developed a custom report item that works fine in design and preview mode while in Visual Studio. I cannot get it to show up on my deployed reports. Here's what I have done so far:

1. Deployed the report using Visual Studio

2. updated the rsreportserver.config file with the following entry:

<ReportItems>
<ReportItem Name="PedigreeChart" Type="Uabr.Rap.PedigreeChart.PedigreeChartRenderer, Uabr.Rap.PedigreeChart" />
</ReportItems>

3. Updated the rssrvpolicy.config file with the following entry.

<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Description="This code group grants Uabr.Rap.PedigreeChart.dll FUllTrust permission. ">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Uabr.Rap.PedigreeChart.dll" />
</CodeGroup>

I've also tried using the StrongNameMembershipCondition with no better results.

4. The dll and its dependencies are copied to the bin directory of the report server.

5. When I load a report with this custom report item on it, the report loads fine with no errors or warnings in the log file (even with verbose tracing). The area where the custom item should be is just white. It's almost like Reporting Services isn't registering the item correctly.

This is particularly frustrating because the report works fine in Visual Studio - apparently I configured that correctly. Any suggestions would be greatly appreciated. I'm stumped.

Hello,

I'm having the exact same problem that you describe. I am also stumped and was wondering if you've found a solution to this problem?

Thanks

|||I got it working, but I'm honestly not sure what I did to get it to work. I ended up granting all assemblies on the server fulltrust, which wasn't my preference but seemed to take care of the issue. However I'm still not sure if that was the item that fixed things. What I am sure about was that is was some configuration issue and not an assembly problem in my case because all I did was srcrew with the configuration for a while. It was a frustrating experience and I'm sorry I can't help more.|||

Hi,

I hab the same problem in the beginning. What solved it for me was that ALL assemblies being used by the CRI have to be trusted, including unmanaged C++ DLLs if there are any. First I listed each DLL but then I gave all my DLLs a strong name and now it works with only the strong name membership condition.

For debugging I enabled something named like 'assembly load logging' on the local report server. I also tried attaching to the worker process in order to read the debugging messages in VS if I remember that right.

Hth,

Thomas

Problem deploying custom report item. Items shows in preview screen in VS, but not in server dep

I have developed a custom report item that works fine in design and preview mode while in Visual Studio. I cannot get it to show up on my deployed reports. Here's what I have done so far:

1. Deployed the report using Visual Studio

2. updated the rsreportserver.config file with the following entry:

<ReportItems>
<ReportItem Name="PedigreeChart" Type="Uabr.Rap.PedigreeChart.PedigreeChartRenderer, Uabr.Rap.PedigreeChart" />
</ReportItems>

3. Updated the rssrvpolicy.config file with the following entry.

<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Description="This code group grants Uabr.Rap.PedigreeChart.dll FUllTrust permission. ">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Uabr.Rap.PedigreeChart.dll" />
</CodeGroup>

I've also tried using the StrongNameMembershipCondition with no better results.

4. The dll and its dependencies are copied to the bin directory of the report server.

5. When I load a report with this custom report item on it, the report loads fine with no errors or warnings in the log file (even with verbose tracing). The area where the custom item should be is just white. It's almost like Reporting Services isn't registering the item correctly.

This is particularly frustrating because the report works fine in Visual Studio - apparently I configured that correctly. Any suggestions would be greatly appreciated. I'm stumped.

Hello,

I'm having the exact same problem that you describe. I am also stumped and was wondering if you've found a solution to this problem?

Thanks

|||I got it working, but I'm honestly not sure what I did to get it to work. I ended up granting all assemblies on the server fulltrust, which wasn't my preference but seemed to take care of the issue. However I'm still not sure if that was the item that fixed things. What I am sure about was that is was some configuration issue and not an assembly problem in my case because all I did was srcrew with the configuration for a while. It was a frustrating experience and I'm sorry I can't help more.|||

Hi,

I hab the same problem in the beginning. What solved it for me was that ALL assemblies being used by the CRI have to be trusted, including unmanaged C++ DLLs if there are any. First I listed each DLL but then I gave all my DLLs a strong name and now it works with only the strong name membership condition.

For debugging I enabled something named like 'assembly load logging' on the local report server. I also tried attaching to the worker process in order to read the debugging messages in VS if I remember that right.

Hth,

Thomas

Problem deploying custom report item. Items shows in preview screen in VS, but not in server dep

I have developed a custom report item that works fine in design and preview mode while in Visual Studio. I cannot get it to show up on my deployed reports. Here's what I have done so far:

1. Deployed the report using Visual Studio

2. updated the rsreportserver.config file with the following entry:

<ReportItems>
<ReportItem Name="PedigreeChart" Type="Uabr.Rap.PedigreeChart.PedigreeChartRenderer, Uabr.Rap.PedigreeChart" />
</ReportItems>

3. Updated the rssrvpolicy.config file with the following entry.

<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Description="This code group grants Uabr.Rap.PedigreeChart.dll FUllTrust permission. ">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Uabr.Rap.PedigreeChart.dll" />
</CodeGroup>

I've also tried using the StrongNameMembershipCondition with no better results.

4. The dll and its dependencies are copied to the bin directory of the report server.

5. When I load a report with this custom report item on it, the report loads fine with no errors or warnings in the log file (even with verbose tracing). The area where the custom item should be is just white. It's almost like Reporting Services isn't registering the item correctly.

This is particularly frustrating because the report works fine in Visual Studio - apparently I configured that correctly. Any suggestions would be greatly appreciated. I'm stumped.

Hello,

I'm having the exact same problem that you describe. I am also stumped and was wondering if you've found a solution to this problem?

Thanks

|||I got it working, but I'm honestly not sure what I did to get it to work. I ended up granting all assemblies on the server fulltrust, which wasn't my preference but seemed to take care of the issue. However I'm still not sure if that was the item that fixed things. What I am sure about was that is was some configuration issue and not an assembly problem in my case because all I did was srcrew with the configuration for a while. It was a frustrating experience and I'm sorry I can't help more.|||

Hi,

I hab the same problem in the beginning. What solved it for me was that ALL assemblies being used by the CRI have to be trusted, including unmanaged C++ DLLs if there are any. First I listed each DLL but then I gave all my DLLs a strong name and now it works with only the strong name membership condition.

For debugging I enabled something named like 'assembly load logging' on the local report server. I also tried attaching to the worker process in order to read the debugging messages in VS if I remember that right.

Hth,

Thomas