Renaming namespace

Hi,
I have created a namespace then renamed it, and build objects within. However, at runtime, when Business Process is calling Java Proxy service which resides on WebAS, we got error of "Error when receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)". And log from Monitoring shows that in some places it is still referencing the old namespace. Have you seen such behavior before? P.S. this is the first time we are trying to make java proxy calls.
Any input is appreciated!
Lina

Hi ,
Yes Possible ,
You have to delete the DEFAULT DATA TYPES .. ie , Exchange fault data and Exchange log data
now delete it from the name space list , save and activate it
Regards,
Jude

Similar Messages

Rename namespaces in Aqualogic service bus

When I try to rename namespaces in ALSB the new namespaces is created and validated against the schema, but the old one is still exist. How I can delete the old namespace.
Example
<cus:soapHeader xmlns:cus="http://www.crm.bell/es/CustomerProfileService"xmlns:com="http://www.bell/enterprise/CommonRequest">
     <com:version>1</com:version>
     <com:callingAppID>MaxP</com:callingAppID>
</cus:soapHeader>
After rename
<cus1:soapHeader xmlns:cus="http://www.crm.bell/es/CustomerProfileService"xmlns:com="http://www.bell/enterprise/CommonRequest"
xmlns:cus1="http://www.crm.bellalaint/es/CustomerProfileService"
xmlns:com1="http://www.bellalaint /enterprise/CommonRequest" >
<com1:version>1</com:version>          <com1:callingAppID>MaxP</com:callingAppID>
</cus:soapHeader>
I want to remove xmlns:cus="http://www.crm.bell/es/CustomerProfileService"xmlns:com="http://www.bell/enterprise/CommonRequest" from response

Could you send me the WSDLS?
My email address [email protected]

Replacing default namespace in OSB message flow

I'm in the process of setting up a simple OSB proxy and could use some help figuring out how to change a default namespace in the response from the business service.
The proxy and business service use different namespaces which we'll call "http://foo.com/namespace/proxy" and "http://foo.com/namespace/business". In my routing request message flow, the contents of $body look like this and I'm able to use a Rename action with XQuery expression "./sof:*" to change "http://foo.com/namespace/proxy" to "http://foo.com/namespace/business":
<sof:Execute xmlns:sof="http://foo.com/namespace/proxy">
<sof:adminName>MyAdaptor</sof:adminName>
<sof:request>
[escaped payload omitted]
</sof:request>
</sof:Execute>
This works fine, but in the response message flow, I need to revert the namespace and am having difficulty because the response uses a default namespace instead of using a prefix:
<ExecuteResponse xmlns="http://foo.com/namespace/business">
<ExecuteResult>
[escaped payload omitted]
</ExecuteResult>
</ExecuteResponse>
If I define a prefix P2L in the expression editor to correspond to "http://foo.com/namespace/business", I'm able to reference the ExecuteResponse element as "./P2L:ExecuteResponse", but then I get stuck.
If I try use a Rename action to change the namespace for "./P2L:*", only the ExecuteResponse element is renamed to <sof:ExecutResponse xmlns:sof="http://foo.com/namespace/proxy">. Upstream in the calling application, there's an XML stream reader exception because (I assume) ExecuteResult is not found and parsed.
I also tried using a Replace action against "./P2L:ExecuteResponse/@xmlns" to replace its contents with "http://foo.com/namespace/proxy". I also tried "./P2L:ExecuteResponse/@P2L:xmlns". Neither worked.
Can anyone tell me what I'm doing wrong, or suggest a different approach? Assume that changing the calling application or business service is not an option.
Thanks!

>
If I define a prefix P2L in the expression editor to correspond to "http://foo.com/namespace/business", I'm able to reference the ExecuteResponse element as "./P2L:ExecuteResponse", but then I get stuck.
If I try use a Rename action to change the namespace for "./P2L:*", only the ExecuteResponse element is renamed to <sof:ExecutResponse xmlns:sof="http://foo.com/namespace/proxy">. Upstream in the calling application, there's an XML stream reader exception because (I assume) ExecuteResult is not found and parsed.
>
You pattern "./P2L:\*" matches just one element so it's ok that the payload's namespace wasn't touched. If you want to rename namespace for all elements try "//P2L:*". However, I'm not sure whether this is what you want. Try do describe what you do, what you want and what you get instead.
>
I also tried using a Replace action against "./P2L:ExecuteResponse/@xmlns" to replace its contents with "http://foo.com/namespace/proxy". I also tried "./P2L:ExecuteResponse/@P2L:xmlns". Neither worked.
>
I think it's not a good approach to replace content of xmlns as this attribute is not a common xml attribute.

Change the default namespace in soap message generated by webservice proxy

I have a requirement where the default namespace generated by the webservice proxy has to be changed. For example, below is a soap request message generated by the proxy:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns0="http://siebel.com/asi/"
xmlns:ns1="http://www.siebel.com/xml/getAllSecurityValuesResponse/PS"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<env:Header>
<wsse:Security
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
env:mustUnderstand="1"
xmlns:xmlns="http://schemas.xmlsoap.org/soap/envelope/">
<wsse:UsernameToken
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:Username>kaoliver</wsse:Username>
<wsse:Password
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">db2</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</env:Header>
<env:Body>
<ns0:SearchSecurityServicegetAllSecurityValues_1>
<Login>kaoliver</Login>
</ns0:SearchSecurityServicegetAllSecurityValues_1>
</env:Body>
</env:Envelope>
In the above message, I want to change the oasis namespace to a different namespace. Where are the default namespaces defined in the proxy classes generated by Jdev so that I can change them?
Thanks in advance,
Warm Regards,
Shashi Anand B

>
If I define a prefix P2L in the expression editor to correspond to "http://foo.com/namespace/business", I'm able to reference the ExecuteResponse element as "./P2L:ExecuteResponse", but then I get stuck.
If I try use a Rename action to change the namespace for "./P2L:*", only the ExecuteResponse element is renamed to <sof:ExecutResponse xmlns:sof="http://foo.com/namespace/proxy">. Upstream in the calling application, there's an XML stream reader exception because (I assume) ExecuteResult is not found and parsed.
>
You pattern "./P2L:\*" matches just one element so it's ok that the payload's namespace wasn't touched. If you want to rename namespace for all elements try "//P2L:*". However, I'm not sure whether this is what you want. Try do describe what you do, what you want and what you get instead.
>
I also tried using a Replace action against "./P2L:ExecuteResponse/@xmlns" to replace its contents with "http://foo.com/namespace/proxy". I also tried "./P2L:ExecuteResponse/@P2L:xmlns". Neither worked.
>
I think it's not a good approach to replace content of xmlns as this attribute is not a common xml attribute.

Serialization and Backward Compatibility

Hi,
We have an application in which we persist data to a flat file. For persisting we are using .net serialization with SOAP Formatter. Now the problem what we are facing is as follows.
Problem Statement:
Recently we have re-factored our source code i.e modifying project structure, renaming namespaces, renaming class names, adding or deleting properties. Can any one suggest a solution to handle the de-serialization issue while using the files which are persisted
by old version of the application.
Thanks,
Manohar

You could create/keep a project with the entity classes that you used to persist the data to your flat files. These would not contain any behavior and would only be used for deserializing and serializing from/to your flat files. You could put a facade in
front of this and treat it like a service. Your new project/code would call the facade to retrieve and write to the old structures. Then you could continue to grow/refactor your new code base without having to worry about the dependency on the persisted file
scheme.
On a side note the default SOAP formatter takes up a lot of wasted space in files and data contracts alike and can be too tightly coupled to your code in my opinion. If you do ever consider switching you could go to something like:
the XmlSerializer which gives your more control over how and what is persisted by way of attributes
a JSon serializer which is even more light weight and flexible
-Igor

Namespace problem with bpelx:rename typeCastTo

Hi!
I have j2ee web service which accepts types derived from one base type. Therefore i need to pass argument like request xsi:type="derivedType", where request is super type.
After long searching i found out this can be done via bpelx:rename typeCastTo ... my problem is that if i use this action:
<bpelx:rename typeCastTo="ns3:UserOutgoingCallingPlanOriginatingModifyRequest">
<bpelx:target variable="Invoke_1_transaction_InputVariable" part="parameters" query="/ns2:transactionElement/ns2:_req"/>
</bpelx:rename>
in audit console after running he process i see
<_req xmlns="http://bwproxy.unient.com/types/" xsi:type="ns3:UserOutgoingCallingPlanOriginatingModifyRequest" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
but namespace prefix ns3 is nowhere defined in the message. It is defined only in source ov bpel process, but it is not propagated to the soap message, therefore web service throws a exception:
Caught exception while handling request: unexpected element type: expected=, actual=UserOutgoingCallingPlanOriginatingModifyRequest
Is this bug, or am i doing something wrong?
thanks
Tomas

Hi,
You could try to use HttpClient to consume wcf in windows phone 8.
Here is an exsample you could refer:
http://stackoverflow.com/questions/21536825/windows-phone-8-call-wcf-web-service
Besides, you could refer to :
http://www.codeproject.com/Questions/691619/Consuming-WCF-Service-from-Windows-Phone
Since this issue is more related to Windows Phone, If my reply no help, please move to Windows Phone forum for a better support, It is appropriate and more experts will assist you.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Renaming a NameSpace in BPEL

Hi All,
Can anyone help me on how to rename a namespace in a Payload using BPEL.
i have a payload like this
<urn1:Test xmlns:urn1="xxxxxxxxxxx">
<x>hi</x>
</urn1:Test>
i want to rename the namespace like this xmnls:urn1="yyyyyyy"
<urn1:Test xmlns:urn1="yyyyyyyy">
<x>hi</x>
</urn1:Test>
Any help is highly appreciated.
TIA,
Karthik
Edited by: karthik !! on Apr 13, 2012 12:00 PM

Hi suneel,
Basically the scenario here is im doing an XML transformation and in the transformation i have a elemnent type of xs:any type and so inorder to transform the xs:any element i used <xsl:copy-of select="ns0:test"> in my xslt transformation
so here in the target payload the namespace of source schema is propgated instead of target sschema namespace and finally my BPEL code throws a validation error.
Any pointers on solving this issue will be helpful to me.
Thanks,
karthik
Edited by: karthik !! on Apr 13, 2012 1:13 PM

Namespace replace/rename issue in ALSB

Hi,
As part of our project we have been using ALSB3.0. In one of our outbound Proxy flows we have configured transform stage which intern executing XQuery transormation. Post transformation it publish message on BEA JMSTopic in following format.
*<?xml version="1.0" encoding="UTF-8" ?>
<ref:ABCMessage xmlns:ref="http://www.indteur.org/abc/2.1/reference">
<ref:FromEANNumber>NA</ref:FromEANNumber>
<ref:SenderIdentifier>
<ref:SenderIDType></ref:SenderIDType>
<ref:IDValue></ref:IDValue>
</ref:SenderIdentifier>
<ref:SentDate>2009-10-10T18:41:27.870-04:00</ref:SentDate>
<ref:Product>
<ref:RecordReference></ref:RecordReference>
<ref:NotificationType>04</ref:NotificationType>
<ref:RecordSourceName></ref:RecordSourceName>
</ref:Product>
</ref:ABCMessage>*
Please help us in rename/replace namespace prefix from 'ref:' to 'ns1:' at post transformation and before publishing the saem to JMS Topic.
Thanks in advance........

Personally I would mandate that what ever is the consumer of the JMSQ should be compatible with XML name space constructs. If it is not under our control then one solution would be
1) Convert the xml to string
let $strContent := fn-bea:serialize($body)
2) Replace the ref: with ns1:
return fn-bea:inlinedXML(fn:replace( $strContent, "ref:", "ns1:") )
This is a very bad solution but should solve your issue if XML is not huge (huge XML will consume lot of cpu for this transformation ) .Ideally I would recommend changing the behavior of the message consumer.
Also you can try defining name space for http://www.indteur.org/abc/2.1/reference as ns1 in sbconsole proxy name space definitions. I believe even this will work but never tried.Let me know if this works for you.
My two cents
Manoj
Edited by: mneelapu on Oct 13, 2009 9:18 AM

Renamed: Why did my namespace change? soap-env (vs) soapenv

Hello forum. I normally post in the main forum. I hope this is the right place for a SOAP question. I'm sure you'll let me know if it's not.
We have an application which was running fine until last week. The app lives on a machine which is not completely ours (we don't control the environment). This app receives and sends socket messages. Based on the incoming message our outgoing message may be in SOAP or a legacy proprietary format. At the time of transmission we do not know the format of the message.
Our outgoing messages stopped being transmitted. What we found was that there was a bit of logic in our transmitting component which read the first X characters of the message to see if it is a SOAP or legacy message. What we did to determine this was to look for, what we thought was standard "<SOAP-ENV....." It worked for years. (I know there are better ways of doing this and we're working on that now). The problem was that the messages that were failing contained "<SOAPENV...."
Here's the question. The objects which build these messages are called from our messaging app. They should be in the same JVM as the messaging app. The messaging app's SOAP jars have not changed. The JRE was upgraded to 1.3.1_19 from _07. In the messaging app as a test I can build a SOAP message and it still says "<SOAP-ENV...." Where is this other namespace coming from? I decompiled the saaj components and it looks like the MessageFactory makes some calls to the environment to determine the message implementation. Could the problem be here? Has anyone heard of this type of thing happening before or am I just losing my mind.
Thanks as always.
ST
Message was edited by:
souLTower

Possibly I don't understand the SOAP implementation. I'm using the same set of SOAP jars (saaj, commons, logging, etc) as I always did. If these jars did not change could / should the message format change? Is the implementation looking outside of my JVM for this implementation?
As to "why" it matters is that I need to know why something in my code has changed. Imagine, for example, that the implementation of String changed. It may still adhere to the normal implementation of String but if my code expects it to look a certain way and it stops looking that way then my code breaks.
As I said in the original post I have handled the issue that it changed but I can't feel comfortable with the application if I fear that it can change again and break my code.
The question is, if the jars related to SOAP (the normal ones you get from sun, I'll provide the list if needed) have not changed then how can the format of the message change?
Thanks again.
ST

ORA-28267: Invalid NameSpace Value after upgrade to 11.1.1.5

Hi Guys,
So after we upgraded to 11.1.1.5 to fix an issue which effected 6 out of our 350 source tables in interfaces, we've hit a problem now which is effecting all 350 interfaces.
We are using a dblink from our 11.2.0.2 DWH to a 10.2.0.2 source database. When ODI goes to load the target table (reading from a C$_ collection view with the db link in it) Im hitting ORA-28267: Invalid NameSpace.
A little digging suggests it might be down to the jdbc driver.
In my 11.1.1.3 install I see this :
/oracledi/agent/drivers/ojdbc6.jar
in my 11.1.1.5 install I see this :
oracledi/agent/drivers/ojdbc6dms.jar
I've tried the obvious of renaming the ojdbc6dms.jar to a backup and copying in the 11.1.1.3 driver ojdbc6.jar in in its place but I see no change (restarted agent)
Can anyone suggest anything ? Do I need to start messing with classpaths in odiparams.sh ?
I have logged an SR already, waiting to jump through the usual hoops before I start getting suggestions.
Thanks in advance,
Alastair

OK I swapped out 4 occurances of the driver :
11gODI/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar
11gODI/odi_misc/ojdbc6dms.jar
11gODI/oracledi/agent/drivers/ojdbc6dms.jar
11gODI/oracledi/client/jdev/extensions/oracle.odi.navigator/lib/ojdbc6dms.jar
with the ojdbc6.jar from the 11.1.1.3 install ( I got mine here : /oracledi/agent/drivers/ojdbc6.jar )
And it seems to be working fine now.

Script to connect and rename a drive works on Windows 8.1 but not Windows 7

I have a script to map a drive to a WebDAV share and the staff wanted it so the Drive shows up as Onedrive and not \\http......etc So I added entries to the script
to rename the drive to that. It seems to run and work perfectly on Windows 8.1 but on Win 7 it maps the drive but the rename part doesn't work. Even running the rename section manually in a separate script on Windows 7 does nothing. Is there a different rename
command for VB for a Win 7 OS?
Jason

Sure thing, Also Ive found the problem is on the ones that aren;t working if I open an app notepad for example and do a save as that drive shows as the name I want it but it doesn't when I just go to My comuter view
Set WshShell = WScript.CreateObject("WScript.Shell")
Return = WshShell.Run("https://login.microsoftonline.com/login.srf?wa=wsignin1.0&whr=adfs.cr.k12.ia.us&wreply=https://crdistrict-my.sharepoint.com&LoginOptions=1", 1)
WScript.Sleep 8000
Dim objNetwork
dim objFSO, objShell, objUNC
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objNetwork = WScript.CreateObject("WScript.Network")
Dim strDriveLetter1, strRemotePath1, strNewName
'end of varible declarations
strDriveLetter1 = "W:"
strRemotePath1 = "\\XXXXXXXX-my.sharepoint.com@SSL\DavWWWRoot\Personal\" & objNetwork.UserName & "XXXXXXXXX/documents"
strNewName = "OneDrive"
'end of varible setup
objNetwork.MapNetworkDrive strDriveLetter1, strRemotePath1
'end of map creation code
' Section which actually (re)names the Mapped Drive
Set objShell = CreateObject("Shell.Application")
objShell.NameSpace(strDriveLetter1).Self.Name = strNewName
WScript.Quit
'end of script
Jason

[svn:fx-trunk] 5558: Add hack to Grammar. jj to allow special component tags in spark and halo namespaces to resolve to special node in the parser .

Revision: 5558
Author: [email protected]
Date: 2009-03-25 14:50:18 -0700 (Wed, 25 Mar 2009)
Log Message:
Add hack to Grammar.jj to allow special component tags in spark and halo namespaces to resolve to special node in the parser. This will be re-addressed once we stabilize on the renames and can better enforce the contents of MXML 2006, MXML 2009, FXG, Spark and Halo.
Add a work around for the step building the AIR Updater UI to set -compatibility-version=3.0.0. This involved checking in a local copy to override the sample-frameworks-build.xml checked into the AIR Integration Kit.zip.
Adding missing base halo and spark classes that appear as qualified type selectors in our defaults.css files but have historically not been in our manifests for MXML tag mappings.
QE: This should help pass more tests.
Dev: Not yet
Doc: Not yet
Modified Paths:
flex/sdk/trunk/frameworks/build.xml
flex/sdk/trunk/frameworks/halo-manifest.xml
flex/sdk/trunk/frameworks/spark-manifest.xml
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/Grammar.jj
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/MXMLNamespaces.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/dom/MxmlScanner.java
Added Paths:
flex/sdk/trunk/in/air/sample-frameworks-build.xml

Import already existing directory structure into DFS namespace?

Hi all,
I'm planning to migrate three file servers to a single DFS namespace and after reading the official docs and numerous blog posts I'm still unsure about the right way to do it.
The "main" server already has a share with a complex directory structure, called \\server1\team, and that share shall become the root of the new DFS namespace, lets call it \\domain.local\team.
Part of that already existing directory structure is this folder: \\server1\team\admin\communication\archive. The folder "archive" contains thousands of files in numerous folders and shall become a dfs link to another share \\server2\archive. But
before I can create the folder "archive" as a dfs link I have to create the folder "admin" in the dfs hierarchy of course, then below that the folder "communication"
Question: When I try to create a folder "admin" in the dfs namespace, I get the error message "the folder cannot be created in the namespace. The file exists."
Ok, the folder "admin" indeed exists, but how can I "import" this branch of the existing directory hierarchy into the dfs namespace?
Do I have to rename the existing folder "admin" to e.g. "admin2", then create the dfs folder "admin" and move the complete directory structure below "admin2" to "admin"? Or can I simply make the existing folder
"admin" a dfs folder?
Thanks in advance!
Regards
Christoph

Mandy, thanks for your feedback!
I have to describe my problem more precisely: creating the root of the new DFS namespace is *not* the problem. This worked for me exactly as you expained it. The problem appears when I try to create a folder below that root in the DFS namespace. If that
folder already exists in the share you cannot choose how to handle security settings but you get an error message, and that's it.
This may be helpfull to explain what I want to achieve:
Old structure:
\\server1\team - folder admin - subfolder "archive" - lots of subfolders and files
Now I want to move all files and folders from "archive" to \\server2\archive and link this share into the new DFS namespace, so that our users don't notice any change when they access that archive folder.
new structure:
1. Create DFS namespace root: \\domain.local\team -> \\server1\team   (works!)
            |
2. Create folder admin (problem!)
            |
3. Create subfolder "archive" -> \\server2\archive (not possible becaues "admin" couldn't be created)
I could perhaps create a DFS namespace with the root \\server1\team\admin\archive and link that to \\server2\archive, but I would like to avoid creating a new namespace for each share which from \\server2 which I mount into some subfolder of \\server1\team...
Thanks for reading.
Regards
Christoph

Unable To Create and/or Rename Folders on DFS Shares

Hi
We have a Windows 2008 Storage Server that we use as a data server. About 100 folders are shared on our network and we use DFS to collect these shares into manageable shared units.
The network comprises 35 Windows 7 clients and one Vista client and a couple of XP machines. These are on a Windows Active Directory that presently comprises three domain controllers: 2003, 2008 and 2012 R2. The network comprises just one site and one subnet.
This setup has worked fine for many years (we've had an Active Directory domain since 2001).
As soon as I replaced our Windows XP clients with the Windows 7 clients I have been seeing some strange network issues.
The most bizarre, and the most unwelcome is that when staff try to create new folders or rename existing ones they will sometimes not be allowed to. The problem is intermittent and I have no idea what may be causing it.
The folder rename issue was encountered when we still used XP but I fixed that by disabling the caching of thumbnails. The error message that appears states the folder is in use. I have used Computer Management on the storage server and looked at Shared
Folders > Open Files and have determined that no files were open when this issue occurred.
When staff are unable to create a new folder they see the following message:
I have tried various things to troubleshoot this with the help of a TechNet Community Support person in the Windows 7 forums
here.
To summarise we have tried using Process Monitor to capture the events and I am quite happy to upload this if anyone would like to see it.
We tried the registry edits detailed in
this MS article.
I have created a dedicated firewall rule that allows all traffic on TCP ports 137, 138, 139 and 445.
Another respondent suggested checking out Slow-Link mode but this has not been triggered.
Does anyone have any ideas what may be causing this, please? The network worked like a dream before the Windows 7 clients were introduced, when XP was used.
Thanks!

Hi,
As you just upgarded to Windows 7, please make sure SP1 is also installed on all systems and install the following hotfix rollup for Windows 7 SP1:
An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1
http://support.microsoft.com/kb/2775511/en-us
There was a known issue on Windows 7 which affected shared folders, that newly created or deleted files are not reflect in network folder immediately, which seems similar to your error. If issue still exists after SP1 and hotfix rollup please help confirm:
1. If this issue occurs only on DFS folder in accessing with \\domain.com\namespace. Could you reproduce the same issue in accessing \\server\sharefolder?
2. Will the same issue occurs after disabling Offline Files if it is enabled.
If you have any feedback on our support, please send to [email protected]

Weird file renaming permission issues

Hi!
We have a file rename permission issue. Here is the background:
We created a 2008 R2 DFS namespace called UserData with Read/write share permissions for Administrators, Everyone and System. UserData has been granted NTFS permissions as follows:
Everyone (This folder only): Traverse folder / Execute files, List folder / Read data, Read attributes, Create folders / Append data
CREATOR OWNER (Subfolders and files only): Full control
SYSTEM (This folder, subfolders and files): Full control
Domain Admins (This folder, subfolders and files)
We then enabled folder redirection for users My documents folder through GPO, setting the following:
Setting: Basic - Redirect everyones folder to the same location
Target folder: Create a folder for each user under the root path
\\domain\UserData
We also unchecked Grant the user exlusive rights to documents.
So, now to the really weird behaviour. We logged on to a Windows 7 (x64) client computer with a user who gets this GPO settings and that is not local administrator on the client. The folder is redirected as expected and we can create, delete and write to
files in anyway we want. We can also rename files if we choose an entirely different name and if we choose a longer or a shorter file name,
but we cannot rename the file to something with the same letters but different casing.
Examples of what will work:
"test" to "testing"
"test" to "cool"
"test" to "COOL"
Examples of what will NOT work:
"test" to "Test"
"test" to "tesT"
"test" to "TEST"
We the get this error: "File Access Denied. You need permission to perform this action. You require permission from S-1-5-21-220..... to make changes to this file."
Eventhough I'm pretty sure the share and NTFS permissions of the share are correctly set we have of course checked all the permissions when logged in and the user has Full NTFS control and Read/Write Share permissions.
We have encountered the same problem on a customer company as well, with a different domain with no links to our domain what so ever. I have also seen similar problems from other people when trying to find the answer on internet. Here is an example:
http://social.technet.microsoft.com/Forums/en/w7itprosecurity/thread/35ced5bb-ab13-4e28-8c48-7c68ce0b775c
Anyone have any thoughts?
/Leyan

Resent discoveries:
If I log onto a Windows 7 (x86) Enterprise I face the same Issues.
If the same user logs on to one of the DFS servers holding the namespace and accesses his folder we experience
no problems renaming files.
Customer company states that all is working fine when user logs on to a Windows XP with SP3.
/Leyan

Renaming namespace

Similar Messages

Maybe you are looking for