Can't Add New Report

In Visual Studio when I create a new Report Project, once it's created I go
into Solution Explorer, right click on the "Reports" folder and select "Add
New Report", and I get the following error:
Exception from HRESULT: 0x8013141A
I've re-installed Visual Studio, the .NET framework, and Reporting Services,
and after all that it still gives me the error.
Any suggestions?
Michael BodnarSome DLL is failing to load. The only sure way to diagnose the problem is
to attach a debugger and see what exceptions it's throwing.
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Bodnar" <blah@.blah.com> wrote in message
news:eX63pJHWEHA.4064@.TK2MSFTNGP11.phx.gbl...
> In Visual Studio when I create a new Report Project, once it's created I
go
> into Solution Explorer, right click on the "Reports" folder and select
"Add
> New Report", and I get the following error:
> Exception from HRESULT: 0x8013141A
> I've re-installed Visual Studio, the .NET framework, and Reporting
Services,
> and after all that it still gives me the error.
> Any suggestions?
> Michael Bodnar
>|||Can you dump out a list of DLLs that are loaded into the VS process when the
error occurs? You can either use a tool like procexp.exe
(http://www.sysinternals.com/ntw2k/freeware/procexp.shtml) or attach another
instance of VS as a debugger. Using VS, display the Modules window, select
all rows, copy, and paste into a text file.
--
Albert Yen
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Bodnar" <blah@.blah.com> wrote in message
news:eX63pJHWEHA.4064@.TK2MSFTNGP11.phx.gbl...
> In Visual Studio when I create a new Report Project, once it's created I
go
> into Solution Explorer, right click on the "Reports" folder and select
"Add
> New Report", and I get the following error:
> Exception from HRESULT: 0x8013141A
> I've re-installed Visual Studio, the .NET framework, and Reporting
Services,
> and after all that it still gives me the error.
> Any suggestions?
> Michael Bodnar
>|||The whole problem was I was trying to install it off a network drive. It
must not have been seeing some files over the network or something, or maybe
some files got corrupt. I installed it with the CD and it works fine now.
"Michael Bodnar" <blah@.blah.com> wrote in message
news:eX63pJHWEHA.4064@.TK2MSFTNGP11.phx.gbl...
> In Visual Studio when I create a new Report Project, once it's created I
go
> into Solution Explorer, right click on the "Reports" folder and select
"Add
> New Report", and I get the following error:
> Exception from HRESULT: 0x8013141A
> I've re-installed Visual Studio, the .NET framework, and Reporting
Services,
> and after all that it still gives me the error.
> Any suggestions?
> Michael Bodnar
>

Cant Access a Database via the Database Explorer

Hi,

I have been able to view the databases and all of their tables but now when I cilck the "+" next to the database or try to connect a new one i get an error message:

"Generating user instances in SQL Server is disabled. Use sp_configure 'user Instances enabled' to generate user instances"

I don't know what I have done and I don't know how to fix it, Please help me!

Best regards,

Elliot

I would do a backup first, before trying anything! Two backups!

It sounds like Sql Server wants you to enter the following command in a query window:

exec sp_configure 'user Instances enabled'

But you might want to google on that first...

|||

Thanks you didn't answer it 100% but I googled it and found the answer in another forum:http://www.mydatabasesupport.com/forums/sqlserver-faq/339672-generating-user-instances-sql-server-disabled.html

Thanks for your help,

Elliot

Cannot use Windows Authentification over VPN

Hi,
I'm trying to connect to my SQL Server 2000 over a VPN IPsec. The VPN
connects succesfully, I can browse with the Windows Explorer the shared
folders of my SQL Server.
When I ping the server the servername is resolved, and when I use ping
-a also resolve the dns.
My problem is the connection to the SQL Server with Windows
Authentification, the following error is throwed:
"Unable to connecto to server...
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Dirver] Cannot generate SSPI context"
But when I use SQL Authentication works fine.
Can anyone help me please?
Thanks in advance,
David SHi guys...
Doing some test I think I know where is the problem.
As I describe in the past post, I'm using a Client VPN aplication to
communicate a mobile user to the main app in the hq. The things is that the
mobile user log in to his domain account when the VPN is not yet established
,
so the DC doesn’t finds out when the user log in.
Once the VPN is up a running the user can access the different shared
folders. But when I try to connect to my app with SQL Server and Windows
Authentication, the app throws the following error: “Cannot generate SSPI
context”.
Is there any way to re-login once you have log onto your account or
just to establish a connection with the DC?
Thanks for your help,
David S|||Working on exactly the same problem. Have you been able to resolve the
issue?
Maybe changing to named pipes? It did not work for me. Also, you can
use sql authentication and you should connect - unfortunately it is
not an option for me. Need to use windows authentication over ipsec.|||Are you signing in to Windows through a VPN or starting a VPN connection
after you're signed in? You could try creating a User with the same
usercode and password as the user you use to sign in to the VPN, then sign
in to Windows with that user and then make your VPN connection and
connection to SQL that May work..
Mike Bulava, MCDBA
"dk77" <dk77@.aa-dot-com.no-spam.invalid> wrote in message
news:e5qdnXM6DIJiKgvfRVn_vg@.giganews.com...
> Working on exactly the same problem. Have you been able to resolve the
> issue?
> Maybe changing to named pipes? It did not work for me. Also, you can
> use sql authentication and you should connect - unfortunately it is
> not an option for me. Need to use windows authentication over ipsec.
>

Cannot use Windows Authentification over VPN

Hi,
I'm trying to connect to my SQL Server 2000 over a VPN IPsec. The VPN
connects succesfully, I can browse with the Windows Explorer the shared
folders of my SQL Server.
When I ping the server the servername is resolved, and when I use ping
-a also resolve the dns.
My problem is the connection to the SQL Server with Windows
Authentification, the following error is throwed:
"Unable to connecto to server...
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Dirver] Cannot generate SSPI context"
But when I use SQL Authentication works fine.
Can anyone help me please?
Thanks in advance,
David S
Hi guys...
Doing some test I think I know where is the problem.
As I describe in the past post, I'm using a Client VPN aplication to
communicate a mobile user to the main app in the hq. The things is that the
mobile user log in to his domain account when the VPN is not yet established,
so the DC doesn’t finds out when the user log in.
Once the VPN is up a running the user can access the different shared
folders. But when I try to connect to my app with SQL Server and Windows
Authentication, the app throws the following error: “Cannot generate SSPI
context”.
Is there any way to re-login once you have log onto your account or
just to establish a connection with the DC?
Thanks for your help,
David S
|||Working on exactly the same problem. Have you been able to resolve the
issue?
Maybe changing to named pipes? It did not work for me. Also, you can
use sql authentication and you should connect - unfortunately it is
not an option for me. Need to use windows authentication over ipsec.
|||Are you signing in to Windows through a VPN or starting a VPN connection
after you're signed in? You could try creating a User with the same
usercode and password as the user you use to sign in to the VPN, then sign
in to Windows with that user and then make your VPN connection and
connection to SQL that May work..
Mike Bulava, MCDBA
"dk77" <dk77@.aa-dot-com.no-spam.invalid> wrote in message
news:e5qdnXM6DIJiKgvfRVn_vg@.giganews.com...
> Working on exactly the same problem. Have you been able to resolve the
> issue?
> Maybe changing to named pipes? It did not work for me. Also, you can
> use sql authentication and you should connect - unfortunately it is
> not an option for me. Need to use windows authentication over ipsec.
>

Cannot see index in Object Explorer on Replicated Database

I have replicated all the tables from the Business Data database to my instance of SQL Server 2005. They did not create primary keys on the tables, so I am adding them on the replicated database. I was trying to save one of the tables after adding a new primary key and got this error message:

'BuildingValues' table
- Unable to create index 'PK_BuildingValues'. CREATE UNIQUE INDEX terminated because a duplicate key was found for object name 'dbo.BuildingValues' and index name 'PK_BuildingValues'. The duplicate key value is (2). Could not create constraint. See previous errors. The statement has been terminated.

The problem is that there is nothing displayed in the Indexes folder for this table in Object Viewer (or any of the other folders for this table), so how would I know an index already existed? The index shows up for this table on the Publisher database, but not the Replicated database. Is this normal?

Sounds like you only replicated the data over without transfering other objects (i.e. pk, constraints, indexes, etc.). The error here is that your current data is not qualified for a pk constraint - pk creates an unique key/constraint underneath, thus, the values cannot be duplicated.
To find the dupes, try:
select [your_pk_col]
from tb
group by [your_pk_col]
having count(*)>1
Resolve that and you should be able to create your pk.
Indexes should get created on the subscriber if you configure it during publication creation - go to the object properties.|||

Thank you very much for your answer. The articles at the Publisher were configured to replicate all the keys and constraints to the Subscriber. You were right about the cause of the problem. The index could not be created, because of duplicate values in the column on the Subscriber. Once I added another column to make it unique, the primary key worked fine. Thanks again.