Showing posts with label version. Show all posts
Showing posts with label version. Show all posts

Tuesday, March 20, 2012

Cannot create new Subscription?

Hi,

I recently got the September CTP Enterprise version and installed it on box with Windows Server2003 os. When I go to a report and try to create a new subscription by going to SQL Server management studio, that option is disabled for me.

I have already setup the email configurations and started the sql server agent.

Anyone has ideas why this should happen?
Most likely, the credentials for the report aren't stored. What do you see in Report Manager? The same?|||

I'm having a similar problem where:

- "New Subscription" is greyed out in Server Management Studio.

- Subscribing via the browser, even as the Content Manager, allows you to fill in the form for the subscription but then reports the following error

"The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database. (rsInvalidDataSourceCredentialSetting)"

Any suggestions?

Monday, March 19, 2012

Cannot create new Subscription?

Hi,

I recently got the September CTP Enterprise version and installed it on box with Windows Server2003 os. When I go to a report and try to create a new subscription by going to SQL Server management studio, that option is disabled for me.

I have already setup the email configurations and started the sql server agent.

Anyone has ideas why this should happen?
Most likely, the credentials for the report aren't stored. What do you see in Report Manager? The same?|||

I'm having a similar problem where:

- "New Subscription" is greyed out in Server Management Studio.

- Subscribing via the browser, even as the Content Manager, allows you to fill in the form for the subscription but then reports the following error

"The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database. (rsInvalidDataSourceCredentialSetting)"

Any suggestions?

Sunday, March 11, 2012

Cannot create ADO connection to DB anymore...

I rebuilt my machine a few weeks back - re-installed the developer version...

The app in question can see all it's tables in the SQL back end via ODBC and
everything looks normal via Enterprise Manager, but I can no longer create
an ADO Connection.

Source code is unchanged, what's changed is the PC rebuild and consequent
re-installatin of SQL Server developer version.

I suspect it's something to do with the provider (at least that's the only thing
I can see in the .Connect string that's not verifiably correct...)

The error looks like this after I trap and format it:

--------------------
12/30/03 21:34:30v0.71 Userid: UPQC on SAG
Proc: basADO: ADO_ConnectionCreate
-2147467259: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does
not exist or access denied.
Errors encountered when trying to connect:
'''[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied.

----Connect String:
Provider=SQLOLEDB.1;SERVER=SAG;DATABASE=TRETS;UID= Trets;PWD=trets
--------------------

Can anybody see anything obvious to look for?

I'm thinking I need to know how to verify/validate the presence of provider
"SQLOLEDB.1"... But how?
--
PeteCresswellHi

Maybe it's a SID type problem! Have you tried a trusted connection?

John

"(Pete Cresswell)" <x@.y.z> wrote in message
news:lkd4vv89m3cdb5fnlt4rt661c47sb56jdv@.4ax.com...
> I rebuilt my machine a few weeks back - re-installed the developer
version...
> The app in question can see all it's tables in the SQL back end via ODBC
and
> everything looks normal via Enterprise Manager, but I can no longer create
> an ADO Connection.
> Source code is unchanged, what's changed is the PC rebuild and consequent
> re-installatin of SQL Server developer version.
> I suspect it's something to do with the provider (at least that's the only
thing
> I can see in the .Connect string that's not verifiably correct...)
> The error looks like this after I trap and format it:
> --------------------
> 12/30/03 21:34:30v0.71 Userid: UPQC on SAG
> Proc: basADO: ADO_ConnectionCreate
> -2147467259: [DBNETLIB][ConnectionOpen (Connect()).]SQL
Server does
> not exist or access denied.
> Errors encountered when trying to connect:
> '''[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist
or
> access denied.
> ----Connect String:
> Provider=SQLOLEDB.1;SERVER=SAG;DATABASE=TRETS;UID= Trets;PWD=trets
> --------------------
>
> Can anybody see anything obvious to look for?
> I'm thinking I need to know how to verify/validate the presence of
provider
> "SQLOLEDB.1"... But how?
> --
> PeteCresswell

Wednesday, March 7, 2012

Cannot connect with SQLCMD - VIA Provider : The specified module could not be found

I have the full version of SQL Server 2005 on my machine under XP. Installed ok and can connect with management studio, but if I try and connect with Analysis Services or even SQLCMD, I get the error below :

HResult 0x7E, Level 16, State 1
VIA Provider: The specified module could not be found.

Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

I have networking enabled, I've enabled all the protocols (apart from VIA because it doesn't start if you do that), and I have all the services running.

Any ideas what can be up ?

I have now fixed this issue and thought I'd just list what was wrong :

The VIA message was because in desperation to connect I had enabled some VIA connections - I think client side.

I disabled all connection types for both client and server except shared memory and TCP/IP.

Still didn't work - and gave a message that the server refused connection.

I then looked at the server side TCP options and found the port number, using SQLCMD tcp:servername,portnumber I could now connect !!

Finally changed the client side TCP to use this port number and now can connect with SQLCMD and no options.

My main gripe is why didn't it all work as installed and why did I have to go through all this to get it to connect !!!

Saturday, February 25, 2012

Cannot connect to SYNDIOMSVR. InternalsVisibleTo declarations cannot have a version, culture, pu

I have the following mssql2005 error when I try to connect to the object browser..


[C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.SmoEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.SmoEnum.dll] InternalsVisibleTo declarations cannot have a version, culture, public key token, or processor architecture specified. (ObjectExplorer)

Can anyone help me?

Thank you....god bless you all..

I have the same problem. I cannot connect to any of my servers. This started when the .net Framework 2.0 Beta was replaced with the newly released version.|||Yes, I have the same problem since installing Net framework 2|||Is this problem with a CTP version of SQL Server 2005, or the RTM version?

SQL Server 2005 RTM only works with the RTM version of the .NET runtime. CTP versions of SQL Server 2005 only work with the version of the .NET runtime that was installed with the CTP.|||I've had this problem as well so I uninstalled .net framework2 and reinstalled the beta version via sql2005 setup - works fine now

Andy|||

The .NET framework version has to match what SQL Server was compiled to use. CTP versions of SQL Server require the corresponding CTP version of the .NET framework. The RTM version of SQL server requires the RTM version of the framework.

Cannot connect to SYNDIOMSVR. InternalsVisibleTo declarations cannot have a version, culture, pu

I have the following mssql2005 error when I try to connect to the object browser..


[C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.SmoEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.SmoEnum.dll] InternalsVisibleTo declarations cannot have a version, culture, public key token, or processor architecture specified. (ObjectExplorer)

Can anyone help me?

Thank you....god bless you all..

I have the same problem. I cannot connect to any of my servers. This started when the .net Framework 2.0 Beta was replaced with the newly released version.|||Yes, I have the same problem since installing Net framework 2|||Is this problem with a CTP version of SQL Server 2005, or the RTM version?

SQL Server 2005 RTM only works with the RTM version of the .NET runtime. CTP versions of SQL Server 2005 only work with the version of the .NET runtime that was installed with the CTP.|||I've had this problem as well so I uninstalled .net framework2 and reinstalled the beta version via sql2005 setup - works fine now

Andy|||

The .NET framework version has to match what SQL Server was compiled to use. CTP versions of SQL Server require the corresponding CTP version of the .NET framework. The RTM version of SQL server requires the RTM version of the framework.

Cannot connect to sqlexpress from ssmse (ctp)

I have been using sqlexpress for several months and decided to upgrade the ssmse to the november ctp version. I uninstalled the old ssmse and installed the november release from ctp.

I verified that the tcp/ip and named pipes are enable in the config manager. I attempted using these connection strings:

\sqlexpress, (local)\sqlexpress, or server name\sqlexpress

All fail with the following message:

Cannot connect to WALLY1\sqlexpress

--
ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476


BUTTONS:

OK

We need a little more information to troubleshoot your problem.

Are you running SSMSE and SQLExpress on the same machine? Are you able to connect to SQLExpress using SQLCMD?

Thanks,
Dan

|||Try to connect either with TCP/IP or named-pipes enabled and not with both the options enabled.
I have had this problem before and when used named-pipes alone it resolved the problem and ensure the ALIAS is defined properly and you can ping the server.|||

Are you running everything from the same machine or are you trying to connect to a remote SQL Server?

Cheers,
Dan

Tuesday, February 14, 2012

Cannot connect to remote Sql Server 2005

Hi;
I installed the dev version of SqlServer 2005 and can access it fine on the
server it is on. And the properties say it allows remote connections.
But SqlServer Management Studio cannot connect from my workstation to the
server. And I cannot connect using ADO.NET or JDBC.
SSMS says "An error...Named Pipes Provider, error: 40 - Could not open a
connection to SQL Server)(Microsoft SQL Server, Error: 233)
The ADO.NET exception is:
System.Data.SqlClient.SqlException was unhandled
Message="An error has occurred while establishing a connection to the
server. When connecting to SQL Server 2005, this failure may be caused by
the fact that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not open a
connection to SQL Server)"
Source=".Net SqlClient Data Provider"
ErrorCode=-2146232060
Class=20
LineNumber=0
Number=233
Server="lumiere"
State=0
StackTrace:
at
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at DBConnTest.SqlServer2005Test.TestSqlServerConnecti on(Boolean
useSSPI) in C:\src\DBConnTest\DBConnTest\SqlServer2005Test.cs: line 31
at DBConnTest.Program.Main() in
C:\src\DBConnTest\DBConnTest\Program.cs:line 29
at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence
assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.Run UsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Any ideas?
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
Hello Dave,
To resolve this issue, please do the following steps on the server:
1. Start SQL Server Configuration Manager in the Start Menu -> Microsoft
SQL Server 2005 -> Configuration Tools
2. Under SQL Server 2005 Network Configuration, Enabled TCP/IP
3. Right clicked Properties on TCP/IP, on the IP Address tab, enabled the
appropriate, active IP Address and then test to connect to the server again.
If this still could not help, please do the following on the client:
1. Start SQL Server Configuration Manager
2. Under SQL Native Client Configuration, Right click Aliases, click New
Alias.
3. Add the Server name and Port No and then test to connect to the server
again.
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti.../default.aspx.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||The TCP/IP (and named pipes) was disabled. Turning that on fixed it.
I understand starting with everything locked down but boy is it a pain...
Any suggestions of a good Sql Server 2005 book for someone who knows Sql
Server 2000?
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
"Wei Lu [MSFT]" wrote:

> Hello Dave,
> To resolve this issue, please do the following steps on the server:
> 1. Start SQL Server Configuration Manager in the Start Menu -> Microsoft
> SQL Server 2005 -> Configuration Tools
> 2. Under SQL Server 2005 Network Configuration, Enabled TCP/IP
> 3. Right clicked Properties on TCP/IP, on the IP Address tab, enabled the
> appropriate, active IP Address and then test to connect to the server again.
> If this still could not help, please do the following on the client:
> 1. Start SQL Server Configuration Manager
> 2. Under SQL Native Client Configuration, Right click Aliases, click New
> Alias.
> 3. Add the Server name and Port No and then test to connect to the server
> again.
> Hope this will be helpful.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscripti...ult.aspx#notif
> ications.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscripti.../default.aspx.
> ==================================================
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
|||Here are a few books to get you started:
Microsoft SQL ServerT 2005: Database Essentials Step by Step
Solid Quality Learning
Microsoft Press
ISBN 0-7356-2207-8 (exp. 9/6/06)
Microsoft SQL ServerT 2005: Applied Techniques Step by Step
Solid Quality Learning
Microsoft Press
ISBN 0-7356-2316-3
Inside Microsoft SQL ServerT 2005: The Storage Engine
Kalen Delaney
Microsoft Press
ISBN 0-7356-2105-5 (exp. 9/27/06)
Administrator's Guide to SQL Server 2005 (Paperback)
Buck Woody
Addison-Wesley
ISBN: 0321397975
Pro SQL Server 2005
Thomas Rizzo, Julian Skinner, Adam Machanic
APress
ISBN: 1590594770
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:43747646-4865-4388-9221-0389550C410B@.microsoft.com...[vbcol=seagreen]
> The TCP/IP (and named pipes) was disabled. Turning that on fixed it.
> I understand starting with everything locked down but boy is it a pain...
> Any suggestions of a good Sql Server 2005 book for someone who knows Sql
> Server 2000?
> --
> thanks - dave
> david_at_windward_dot_net
> http://www.windwardreports.com
> Cubicle Wars - http://www.windwardreports.com/film.htm
>
>
> "Wei Lu [MSFT]" wrote: