Connectivity Issue with Vista and SQL Server 2005

Hi all;
I am unable to log into SQL Server 2005 due to a connectivity problem.
When I telnet on the port for the server, the attempt at a connection fails.
Does anyone have any ideas as to what I should do?
THANKS!!!
Wally

Closed the thread regarding: http://social.msdn.microsoft.com/Forums/en-US/sqlsecurity/thread/c20ee682-d329-4678-a8a6-6e10b746bf0e/
Using the elevated mode fixed the problem.
Jens K. Suessmeyer

Similar Messages

JPA and SQL Server 2005's Identity Don't Play Nice

I am hoping someone with a little more senior knowledge of JPASQL Server 2005 can point me in the right direction involving SQL Server 2005.
What I am discovering is JPA and SQL Server 2005 do not playing nice together when you use the IDENTITY capability for
a primary key. Let me explain. "...when using the IDENTITY as the generator type, the value for the identity field MAY NOT be
available BEFORE the entity data is saved in the database because typically it is generated when a record is committed."
My problem is this.
I have two separate entities using another entity, for example a car has a wheel and a truck has a wheel. I can go through the steps
of persisting the car and the wheel with no problem. My problem begins when I try to
find the wheel (by wheel description) for the truck. The query finds the wheel, but does not return the primary key for wheel.
Therefore, using the PK inside a query generates this error:
java.lang.IllegalArgumentException: An instance of a null PK has been incorrectly provided for this find operation. What has been my appraoch to get the entity to commit to the database is to use the following sequence for the Entity Manager.
entityManager.persist(wheel);
entityManager.flush(); I have assumed to this point this action would persist my data because I have been able to retrieve the PK immidately after these steps.
However, multiple actions taking place within the same transaction, appears to render the persist and flush steps useless. My initial thought
is to wrap the wheel creation within a new transaction so when the method/transaction completes, the data would be in the database. This
has not worked.
I hope I have explained this clear for others to follow. I apologize in advance if I have not. Any suggestions are greatly appreciated.

I am hoping someone with a little more senior knowledge of JPASQL Server 2005 can point me in the right direction involving SQL Server 2005.
What I am discovering is JPA and SQL Server 2005 do not playing nice together when you use the IDENTITY capability for
a primary key. Let me explain. "...when using the IDENTITY as the generator type, the value for the identity field MAY NOT be
available BEFORE the entity data is saved in the database because typically it is generated when a record is committed."
My problem is this.
I have two separate entities using another entity, for example a car has a wheel and a truck has a wheel. I can go through the steps
of persisting the car and the wheel with no problem. My problem begins when I try to
find the wheel (by wheel description) for the truck. The query finds the wheel, but does not return the primary key for wheel.
Therefore, using the PK inside a query generates this error:
java.lang.IllegalArgumentException: An instance of a null PK has been incorrectly provided for this find operation. What has been my appraoch to get the entity to commit to the database is to use the following sequence for the Entity Manager.
entityManager.persist(wheel);
entityManager.flush(); I have assumed to this point this action would persist my data because I have been able to retrieve the PK immidately after these steps.
However, multiple actions taking place within the same transaction, appears to render the persist and flush steps useless. My initial thought
is to wrap the wheel creation within a new transaction so when the method/transaction completes, the data would be in the database. This
has not worked.
I hope I have explained this clear for others to follow. I apologize in advance if I have not. Any suggestions are greatly appreciated.

OraOledb, Linked Servers and SQL Server 2005 issues

Some issues I've come across when using SQL Server 2005 (and SQL Server Express 2005), the OraOLEDB provider (10.2.0.1) and a linked Oracle database (8.1.7.4.0 64-bit)
1) You must set the OraOledb.Oracle\AllowInProcess value to 1 to allow the OraOledb provider to run in SQL Server's process. Without doing this I receive an 'unspecified error' from the OLE DB provider when attempting to run a query
2) When running a ' select * ' query across a linked server using the provider, I receive the following error: Msg 9803, Level 16, State 1, Line 1
Invalid data for type "numeric". I can, however, select all of the columns by name and the query completes (no error). Sometimes the 'select *' query returns a few rows before the error, sometimes it doesn't. The Microsoft Provider for Oracle does not have this problem

Okay... I've got a Win2K3 Std Ed server (x64) running 64-bit SQL Server 2005 Enterprise Edition. I've installed the Oracle 10g 10.2.1 full client and admin tools, added two named services via the NetConfig assistant, and successfully set up (and tested) a connection via the ODBC Administrator to an Oracle database.
Now... when I try to create a new connection manager in SQL Server 2005 Integration Services, the OLEDB provider for Oracle can't be found, and when I try to manually add an underlying OLEDB connection to the database, SQL Server reports:
Test connection failed because of an error in initializing provider. The 'OraOLEDB.Oracle.1' provider is not registered on the local machine.
Does anyone know what I need to do to see my ODBC Server data connections in SQL Server 2005 (64 bit)? I don't have this issue on my 32-bit SQL Server 2005 servers.

OraOledb for 64-bit, Linked Servers and SQL Server 2005 issues

Our environment is : SQL Server 2005, Windows Server 2003, 64-bit and 32-bit operating systems.
Problem on 64-bit operating system box: (32-bit works fine).
I am trying to access Oracle 10g database using linked server from our SQL Server 2005. In case of number fileds i got the following error:
Invalid data for type "numeric".
After going through one of the posting in this forumn i was able to resolve the problem by converting those column values to char while querying and then converting them back to numeric type on SQL server side.
But today i ran into another problem. There is a VARCHAR2 column. I was able to retrieve the data yesterday for that column but today i am getting a blank recordset. If i exclude the colum from the query then i am getting all the rows.
I am querying against a view and it has got a number of columns whose data type is VARCHAR2.
Again the problem is on 64-bit operating system only. We have a 32-bit operating system on which i am able to retrieve the data including this column. I looked at the data and everything looks OK. No funny characters etc.
I tried workarounds like using cast, to_char, checking for nulls etc., Nothing works.
Any help is greately appreciated. Thanks.

Did you find a resolution for this? We have similar problem. Set up a linked server in SQL 2006 to Oracle (running on Windows 64-bit) Linked server works and views I had set up were working but they added some new data in the Oracle test database I am using and now I get errors on one of the views.
Error I am getting on the view is "Cannot initialize the data source object of OLE DB Provider "OraOLDEDB.ORacle" for the linked server"
If I fine tune my queries to find the specific table or view that is at issue, then I get the error "inconsistent metadata for a column"

B1 and SQL Server 2005 performance with 3.000.000 invoice-lines per year

I would like to know if SAP Business One with SQL Server 2005 could work with the following information:
- 40.000 Business Partners
- 40.000 Invoices per month
- Aprox. 3.000.000 invoice-lines per year
Of course it will be necessary to change some forms in B1.
What do you think?
Do you know any B1 customer working with that amout of data?

> Hi,
>
> I think a good SQL2005 tuning (done by a good DBA)
> will improve performance. Number of records like that
> shouldn't hurt that kind of DB engine...
Hi,
I'm sure that MSSQL2005 can handle the amount of records & transactions in question. Even MSSQL 2000 can do it. However, any DB engine can be put on its knees with the combination of 2-tier application architecture and badly designed queries. B1 is a case in point. I wouldn't go into such a project without decent preliminary load testing and explicit commitment for support from SAP B1 dev team.
I have heard from implementation projects where B1 simply couldn't handle the amount of data. I've also participated in some presales cases for B1 where we decided not to take a project because we saw that B1 couldn't handle the amount of data (while the other features of B1 would have been more than enough for the customer). The one you're currently looking at seems like one of those.
Henry

HSODBC connectivity between ORACLE 10g and SQL Server 2008 R2

Hi,
I'm getting below error when using the DB link between Oracle (10.2.0.2 which is on Sun Sparc) and MS Sql server 2008 R2.
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Generic Connectivity Using ODBC][Microsoft][ODBC Driver Manager] Data source
name not found and no default driver specified (SQL State: IM002; SQL Code: 0)
ORA-02063: preceding 2 lines from SCOPEX.WORLD
My Config files:
On Sun Sparc 5.9 where Oracle server is running.
TelemetryDB1 =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=172.16.6.48)(PORT=1522))
(CONNECT_DATA=(SID=TelemetryDB1))
(HS=OK)
Listener.ora file on Windows machine:
TelemetryDB1 =
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=tcp)(HOST=172.16.6.48)(PORT=1522))
(ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
SID_LIST_TelemetryDB1 =
(SID_LIST=
(SID_DESC=
(SID_NAME=TelemetryDB1)
(ORACLE_HOME=C:\oracle\product\10.2.0\db_1)
(PROGRAM=hsodbc)
Tnsnames.ora file:
TelemetryDB1 =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=172.16.6.48)(PORT=1522))
(CONNECT_DATA=(SID=TelemetryDB1))
(HS=OK)
initTelemetryDB1.ora file under ORACLE_HOME\hs\admin\
HS_FDS_CONNECT_INFO = TelemetryDB1
HS_FDS_TRACE_LEVEL = OFF
We have created DNS with TelemetryDB1.
I'm getting the above error for DB links between Oracle 10.2 and SQL Server 2008 R2. But the same, when configured for MS SQL server 2000 works fine without any issues.
Please advise me to rectify the error. We've been working for the last couple of weeks.
Regards,
Sunil

Sunil,
You don't need an Oracle ODBC driver.
The way it works is that in the gateway init<sid>.ora file, in your case initTelemetryDB1.ora, the parameter HS_FDS_CONNECT_INFO points to a system DSN. This DSN should then be configured to use an ODBC driver to connect to the non-Oracle database. So, in your setup when you want to access the SQL*Server 2008 database then the DSN should use an ODBC driver that can connect to a SQL*Server 2008 database. If you still use the initTelemetryDB1.ora file for the connection then the TelemetryDB1 DSN should be configured to access the SQL*Server 2008 database.
However, there are a couple of problems with your actual setup -
- the configuration you have - 10.2 RDBMS on a Sun machine and HSODBC on Windows - is not supported. HSODBC should only be used from a RDBMS that is in the same ORACLE_HOME as HSODBC.
- 10.2 HSODBC is now desupported and has been replaced by the 11g Database Gateway for ODBC (DG4ODBC) and the configuration you want is supported. That is because unlike HSODBC the DG4ODBC gateway can be installed standalone with a RDBMS being installed.
I recommend that you download and install 11.20.2 DG4ODBC on your Windows machine in a new Oracle_home and access that from the 10.2 RDBMS on Sun - which is a supported configuration. But to do this, you will need to apply either the 10.2.0.4 or 10.2.0.5 patchset to your RDBMS.
There is more information in the following note available on My Oracle Support (MOS) -
Note.1083703.1 Master Note for Oracle Gateway Products
The 11.2.0.2 DG4ODBC can be downloaded from MOS as patch and for the gateways on Windows 32-bit you just need to download -
p10098816_112020_platform_4of6.zip
However, to check the HSODBC ou need to confirm that the DSN used by HSODBC points to a System DSN configured to access SQL*Server 2008.
Have a look at -
Note 109730.1 How to setup generic connectivity (HSODBC) for Windows NT
But remember this is not a supported version or configuration and you should be using Dg4ODBC.
Regards,
Mike

OWB 11.0.0.7 and SQL SERver 2005

We did search quite a bit but couldnt get this working...
We are using OWB 11.1.0.7 64bit on Windows 2003 Server 64bit R2
We have to pull data from a SQl Server database – SQL SERVER 2005 64 bit on Windows 2008 R2 64 bit
WE followed the procedures given in Oracle documentation –
1. creating a ODBC DSN connection
2. creating a init ora file for that connection
3. creating a listener
We tried with both HSODBC and DG4ODBC... We can connect to SQL server through OWB...the connection is successful but I cannot import the tables into OWB. It simply hangs forever. (in the init ora file we have put the HS_FDS_SUPPORT_STATISTICS=FALSE) We have to pull data from SQL server on an ongoing basis. However we found a workaround – we can create a remote link to the SQL server database by creating an entry in the tnsnames. However this connection is very slow – we have to pull thousands of records on daily basis. IT takes quite some time to do this. We have tried different combinations after Goodling.
Could you shed some light on this? Is it a bug in OWB 11.1 that we cannot connect to SQL Serer or are we missing something? Will it be ok if we go for 11.2?

Be wary about the differences between initialization settings for generic ODBC vs specific SQLServer gateway, they are different.
http://download.oracle.com/docs/cd/B28359_01/gateways.111/b31049/apd.htm#BABHEBCE
The installation guide has details in the SQLServer section for when the SQLServer gateway is used that you should follow (specifically under configuring SQL Server Views for Data Dictionary support - needed for importing tables definitions into OWB when you use SQLServer gateway);
http://download.oracle.com/docs/cd/B28359_01/gateways.111/b31042/toc.htm
If you have an existing database link this can be used in OWB. When importing the tables you need to be aware that if it is a SQLServer gateway you will need to configure the SQLServer instance as in the gateway doc above). Just because you can query table data does not mean the gateway is configured properly.
Cheers
David

Freetds and sql server 2005

Hi guys
I'm trying to create dblink from 10.2.0.4 database to sql server 2005 using freeTDS. Oracle database is on OEL5, ODBC is installed on another OEL5 machine with database gateway installed and listener started.
So far everything woks fine. However it seems that something is wrong with character set conversion. I'm getting twice as much characters (character followed by a box character). I'm guessing this is 2 byte character set that has not been converted to 1 byte. Oracle DB has nls_characterset set to 'EE8ISO8859P2'.
What setting should be set in init<>.ora for the DG4ODBC and freetds.conf?
I also tried trial easysoft odbc driver and it works fine with these parameters in odbc.ini:
# Convert UCS-2 encoded Unicode data to UTF-8
ConvToUtf = Yes
# Also do this conversion for data passed to Unicode ODBC function (SQLxxxW) calls
ConvWToUtf = Yes

I saw a similar behaviour using an Oracle unicode database. In this case try a unicode compliant tool like SQL Developer, connect to the Oracle db with the db link and select from the linked table.
What is the source column data type and did you specify HS_LANGUAGE in the hsodbc init file?
Edited by: kgronau on Nov 27, 2009 11:45 AM

Crystal Reports 9 and SQL Server 2005 default parameter values

We're using Crystal Reports 9 and upgraded from SQL Server 2000 to SQL Server 2005.
I'm noticing a very weird problem which I wonder if anyone else has experienced (and hopefully found a resolution for). It appears that in using Crystal with SQL Server 2005 stored procedures, if we have default parameter values in the stored procedures, the default parameter values get completely ignored if you pass in a NULL value from Crystal!
For example, if you have a stored procedure that begins like this:
ALTER Procedure [dbo].[StoredProcedure]
@Param1 VarChar(200) = '',
@Param2 VarChar(200) = ''
AS ...
both @Param1 and @Param2 have a default value of an empty string, and therefore should become empty strings if nothing (NULL values) gets passed in for them.
But, like I said, what I'm finding is that with Crystal calling the stored procedure with NULL @Param1 and @Param2 values, they never become empty strings, but rather remain as NULLs.
This was never a problem with SQL 2000.
Very perplexing. Anyone else every experience this?
Thank you.

Please ignore my earlier post -- answered my own question.
NULL parameter values do not get replaced by default values in SQL -- that is normal behavior in both SQL 2000 and SQL 2005. Just goes to show, that no many how many years programming experience you have, you can still get tripped up sometimes : (

BO XI R2 and SQL server 2005 Analysis services

Post Author: fasttrack
CA Forum: Olap
Hello,
I am new in BO, I am using XI R2 and I would like to know this:
I have to build some reports on Data Warehouse using SQL server 2005 Analysis Services.
My question is:
1) How I have to build this reports: directly to data warehouse or building an OLAP (CUBE) in analysis services 2005?
2) BO XI R2 supports SQL server 2005 and especially in this case Analysis services 2005 and provider (I have seen only provider for SQL Server 2000)?
Do you some good resources where to learn how to make reports on DW SQL server 2005?
Thank

Post Author: ShaunOberem
CA Forum: Olap
Hello,
I am new in BO, I am using XI R2 and I would like to know this:
I have to build some reports on Data Warehouse using SQL server 2005 Analysis Services.
My question is:
1) How I have to build this reports: directly to data warehouse or building an OLAP (CUBE) in analysis services 2005?
2) BO XI R2 supports SQL server 2005 and especially in this case Analysis services 2005 and provider (I have seen only provider for SQL Server 2000)?
Do you some good resources where to learn how to make reports on DW SQL server 2005?
Thank
Hi,
If you are trying to create a new OLAP Intelligence Report using SQL 05 I am afraid you are out of luck.
You will need to get a copy of the Productivity Pack (Available for Download in Subscribenet) .
Also, in your SQL Server Sufrace Configuraiton manager try setting Analysis Services to Allow Ananomous connections. This will make sure you get a little further initially. (Dont leave Anonymous on)

Replication Configuration issue after migrating from SQL Server 2005 to SQL Server 2008 R2

Hi All,
This weekend we have migrated one of our Core system from SQL Server 2005 SP3 to SQL Server 2008 R2 SP2. Migration went successful. However when we are trying to Configure transaction replication we are getting below Error:
Msg 21854, Level 16, State 1, Procedure sp_MSrepl_addarticle, Line 573
Could not add new article to publication 'abc' because of active schema change activities or a snapshot is being generated.
Background:
Database compability Changed from 90 to 100.
A quick Help would be appreciated.
Best Regards - Viral
Thanks - Viral

Is a snapshot being generated? the message seems to indicate one is.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Installing Dialog Instances with ECC 6.0 and SQL Server 2005

Hi, I have my ECC 6.0 SAP Server, it is Central Instance, Database instance, all in one. My users are working fine, however we will be adding some new users (15) and we want add a Dialog Instance. Can I add one Dialog instance to my landscape without any changes to my SAP Server ??? ..... My dialog instance will be in a new host.
My hardware SAP Server is: 16 GB RAM, 500 GB RAID 5 for my database, four processors.
What could be my Dialogue Instance hardware?
I have read than I must install with sapinst and select Dialogue Instance and follow instructions. Are there any others considerations?? .....
Do I must install SQL Server in the host Dialog instance ??.
Please if you have some suggestions.
Regards.

Hello Jose,
You can install your dialog instance without doing any change to the existing setup as you have mentioned its on a seprate new host.
Two CPU's and 8GB memory would be fine for your dialog instance.It all depends on your requirement.
Yes you need to install the dialog instance using SAPINST, its kool and sapinst would take care of all.
You need not install any SQL server in the dialog instance host only you need to have a SQL client installed but that would be taken care by SAPINST.
Hope this would clarify your query.
Thanks and Regards,
-Bijesh.

Encrypting communication between an app that uses an ODBC/DSN (with ADODB) and SQL Server 2008 R2

I've been doing a lot of reading the last couple of days on how we can encrypt db communication between our product app and a customer's SQL Server db, but cannot make it work as expected. The app uses a ODBC/DSN to connect to the SQL Server db. I use this
ODBC app to setup the DSN (on a Windows 7 PC):
C:\Windows\SysWOW64\odbcad32.exe
The DSNconnection uses the SQL Server driver 6.01.7601.17514 and has these properties:
- WinNT authentication.
- Client Config button: TCP/IP to <server-name>\<instance.-name>
- Change to default db: <name-of-app-db>
- Everything else is default setting.
SQL Server is on the same Windowns 7 PC and has a self-signed cert installed (used IIS to generate it) and has the Force Enryption set to "yes".
I have a test C# program that uses the ADODB 2.7.0.0 COM-wrapper, made by Visual Studio after adding a reference to the ADO 2.7 library version 6.1.7601.17857. The program creates an ADODB.Connection object that has a simple connection string: "DSN=<san-name>;UID=<user>;PWD=<password>". The
program then creates an ADODB.Recordset object and reads and displays a field from a table.
Works fine.
If I go into SQL Server and set Force Encryption to "no," clear the cert, restart the SQL service, and then re-run the program, it works fine.
Here's the kick. If I go into the DSN and select "Use strong encryption for data" the Test button on the DSN works—why does it work? The SQL Server is no longer encrypting the connection so an error should occur. If I run the test program, it works
as well—why? I can look at the connection properties in the test program and see that ADODB has added the ";Encrypt-yes" stuff to the end of the connection string. Yet that option seems to have no effect.
If I set the SQL instance back to Force Encryption:yes, enable the cert, restart the SQL service, and clear the DSN's "Use strong encryption for data" option, I can still connect to the db with the
test program—why?
What am I doing wrong? I need to be able to ensure that the communication between our app product and the SQL instance is encrypted, and that we get an error if the SQL instance does not support encrypted communications. We really don't want the customer
to have to enable Force Encryption because they have other db's on their SQL Server that do not use encrypted communication, but they want to know that our product's communication channel with the db is encrypted.
No, I can't change the app product's code at this point in time. I'm stuck with working with what a DSN called from ADODB has to offer.
Also, how can I be sure that communications are encrypted? I mean, I've tried things like "SELECT * FROM sys.dm_exec_connections" but that doesn't help because I have no idea how to tie the list of sessions shown back to my test program, although
I guess it's a good thing that some of the sessions listed show encrypt_option as TRUE.
-glenn-

Ah yes, very good point. It's easy to miss because you have to delete then recreate the DSN in order to change drivers. So I switched the DSN over to the SQL Native 11 driver.
Now when I try to connect to the SQL instance as <computer-name>\<instance-name>, and without a cert on the server, I get "the target principal name is incorrect". Perfect; now we're getting somewhere!
Change my DSN to use <fqdn>\<instance-name> and it works. This tells me that SQL Server has auto-generated a cert and named it <fqdn>. I would have expected the "cert fail" error, not a cert
name mismatch, because I'm not using Trust Server Cert.
So I load up my self-signed cert, and that works too.
I am still confused as to why I'm not seeing the "cert fail" error when I have no cert loaded on the SQL Server. I am not using Force Encryption on the server at all, so wouldn't expect SQL Server to auto-create a cert when an Encrypt=yes request comes in,
but apparently it does?
I also ran into a problem with this:
select c.session_id, c.encrypt_option, s.client_interface_name
from sys.dm_exec_connections c
join sys.sysprocesses s
on c.session_id = s.session_id
where s.dbid = db_id('MyDatabase')
There is no s.client_interface_name, probably should be s.hostname. There's also no s.session_id. I thought maybe this should be s.sid, but then no rows ever come back. The c.session_id looks like 51 and 52, but the s.sid looks like a very long binary number,
so these two fields cannot be joined. I don't know how to convert the sid's properly so that the join would work. Ah wait, I just found the s.spid column; the join works when that column is used (I assume that's correct anyhow).
If I add a Thread.Sleep(30 seconds) to my C# program just before the connection is closed, this query shows me the session for the correct hostname has encrypt_option=TRUE.
And I have to keep my fingers crossed that all the app I/O will still work properly after
changing the driver. Probably a safe bet though.
Think I'm ready to throw in the towel on getting the "cert fail/no SSL" error to appear.
It does look like I am able to sufficiently show that the connection is encrypted when Encrypt=yes is used with the newer driver.
Thank for all the help!
-glenn-

Data type conversion issues between Oracle and SQL Server

Hi there, I am using Heterogeneous Services to insert into a SQL Server database. I am running into an issue between data types regarding Oracle's VARCHAR2 and trying to insert that into a SQL Server MONEY data type. I tried using the TO_NUMBER() function to convert my VARCHAR2 to a number, but that didn't seem to help.
Does anyone have any advice on how to work around this??
Thanks for any help,
ivalum21

ORA-02047: cannot join the distributed transaction in progress
ORA-06512: at "MY_PACKAGE_NAME", line 263
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Generic Connectivity Using ODBC]DRV_Execute: DB_ODBC_ENGINE (1645): ;
[Microsoft][ODBC SQL Server Driver][SQL Server]Disallowed implicit conversion
from data type varchar to data type money, table 'tableA',
column 'total_amount'. Use the CONVERT function to run this query. (SQL
State: 37000; SQL Code: 260)
ORA-02063: preceding 2 lines from SQLSERVER_LINK
ORA-06512: at "RCDTPUMP.CAMPUSCALL_DATAPUMP_UNI", line 875
ORA-06512: at "RCDTPUMP.CAMPUSCALL_DATAPUMP_UNI", line 791
ORA-06512: at "RCDTPUMP.CAMPUSCALL_DATAPUMP_UNI", line 1156
ORA-06512: at line 1
That is what I get when I take out the TO_NUMBER()
Message was edited by:
ivalum21

Ethernet connectivity issue with Microsoft Small Business Server (SBS)

Just recently updated my OS to Yosemite, and am now having ongoing problems connecting to my company's Microsoft Small Business Server (SBS).
I'm having no other issues connecting to outside server's via wifi or ethernet, but once I connect to our local business server I lose internet connection and also my email account goes offline (Microsoft Outlook 2011). Sometimes the connection will intermittently return, but will be very slow and won't load images. I had no connection issue's before the update.
Anyone experienced a similar problem?

"That depends on what what resources you use the server for."
- I will be using the printer for print sharing and file sharing. There is an estimating application I will load on a Mac Mini and will want to share that to other desktops.

Connectivity Issue with Vista and SQL Server 2005

Similar Messages

Maybe you are looking for